Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add minimal list validators #5334

Closed

Conversation

winksaville
Copy link
Contributor

Issue Addressed

There is no issue, I thought it was a nice to have.

Proposed Changes

Added list_validator.rs based on import_validators.rs, this command
lists all of the validators present on the target node.

Additional Info

Currently there are no tests,

I wanted to be sure that my vc's were setup to properly for use
with validator-manager using a "read-only" command, `list` seemed like
an obvious choice.
@dapplion dapplion changed the base branch from stable to unstable March 4, 2024 01:31
@chong-he chong-he added the val-client Relates to the validator client binary label Mar 4, 2024
@pahor167
Copy link
Contributor

pahor167 commented Mar 4, 2024

I also added this command (among others) in the following PR #5347 - please let me know if I should remove it from there

Updated SUMMARY.md, help_vm.md and scripts/cli.sh then ran `make cli-local`
which created help_vm_list.md in the root. I then moved it to `book/src/`
@winksaville
Copy link
Contributor Author

I also added this command (among others) in the following PR #5347 - please let me know if I should remove it from there

Whatever the powerful say is fine with me, this a decision that is above my pay grade, LoL!

@chong-he chong-he added the ready-for-review The code is ready for review label Mar 5, 2024
Run `cargo fmt` to fix list_validators.rs format.
@dapplion
Copy link
Collaborator

dapplion commented Mar 11, 2024

Thank you @winksaville for the contribution! This PR uses get_lighthouse_validators which is a lighthouse specific route. The VC_URL_FLAG description states A HTTP(S) address of a validator client using the keymanager-API. which contradicts the above.

Given the existence of the keymanager API (see https://github.com/ethereum/keymanager-APIs) it is best to use its list endpoint. Speced here https://github.com/ethereum/keymanager-APIs/blob/a71e126e369a4ca762906f1d0884edcad70ee0ed/apis/local_keystores.yaml#L2)

EDIT: @pahor167 's PR uses the keymanager API to list keystores, see https://github.com/sigp/lighthouse/pull/5347/files#diff-748ad38a4d2e54eeef556475f65a7d67a53fb644e416d87d7f0c68202fba1468R77 maybe we can focus on that one as it's closer to the end goal :)

@winksaville
Copy link
Contributor Author

winksaville commented Mar 11, 2024

EDIT: @pahor167 's PR uses the keymanager API to list keystores, see https://github.com/sigp/lighthouse/pull/5347/files#diff-748ad38a4d2e54eeef556475f65a7d67a53fb644e416d87d7f0c68202fba1468R77 maybe we can focus on that one as it's closer to the end goal :)

SGTM, if @Pahor is closer definitely use it.

@winksaville
Copy link
Contributor Author

Closing in preference to #5347

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-for-review The code is ready for review val-client Relates to the validator client binary
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants