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

Create-validator cli is broken since alpha.5 #2122

Closed
chuck-bear opened this issue Nov 1, 2024 · 4 comments
Closed

Create-validator cli is broken since alpha.5 #2122

chuck-bear opened this issue Nov 1, 2024 · 4 comments
Assignees

Comments

@chuck-bear
Copy link
Collaborator

The create-validator CLI is broken since alpha.5, last time it worked it was with alpha.4.

How to reproduce it ?

Run that command line with alpha.8 binary:

beacond deposit create-validator $VAL_WITHDRAW_CREDENTIAL $VAL_DEPOSIT_GWEI_AMOUNT $GENESIS_FORK_VERSION $GENESIS_VALIDATORS_ROOT --private-key $YOUR_ETH_WALLET_PRIVATE_KEY  --home $YOUR_BEACON_HOME_DIR

It will return open : no such file or directory

And run it with alpha.4 binary.

Let me know if you need more details.

@chuck-bear chuck-bear changed the title create-validator cli is broken since alpha.5 Create-validator cli is broken since alpha.5 Nov 1, 2024
@abi87 abi87 self-assigned this Nov 1, 2024
@dezzeus
Copy link
Contributor

dezzeus commented Nov 5, 2024

It took a while, but I have found the root cause of the issue: the deposit CLI sub-command was attempting to retrieve the (viper) configuration from the command's context using the ViperContextKey key defined in the github.com/cosmos/cosmos-sdk/client package instead of the one defined in the github.com/berachain/beacon-kit/mod/cli/pkg/context one (that was used for storing the loaded configuration).

As a result, the command attempted to load the priv_validator_key_file and priv_validator_state_file files from empty strings returned by a new, empty, viper configuration.

I'll make a PR to fix it, hoping that there are no more issues down the same road.

@chuck-bear
Copy link
Collaborator Author

Thanks @dezzeus this looks very familiar to #2123

@abi87
Copy link
Collaborator

abi87 commented Nov 5, 2024

@chuck-bear we do have a proposed solution by @dezzeus on #2128. Can you try it out?

@chuck-bear
Copy link
Collaborator Author

@dezzeus @abi87 just tested, it's working. Thanks!

@dezzeus dezzeus closed this as completed Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants