You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a 2 nodes POS private chain configured as here but adjusted to run on k8s. When I try to create a validator wallet on my second node, I have no way to get the deposit data and the withdrawal public key. Here is what the docs from here sais:
And having the consensus layer (prysm beacon-chain) and the execution layer (geth) running in the same k8s pod (meaning it's on the same localhost network).
After talking to the team the deposit information should align with the original creation of the keys ( we will not support displaying it), information about the withdrawal address can be reviewed https://docs.prylabs.network/docs/wallet/withdraw-validator. you can get the data via beacon API or using a tool like https://github.com/wealdtech/ethdo. sorry it may not be the answer you were hoping for. I have opened a separate issue for documents and will be closing this one.
Describe the bug
I have a 2 nodes POS private chain configured as here but adjusted to run on k8s. When I try to create a validator wallet on my second node, I have no way to get the deposit data and the withdrawal public key. Here is what the docs from here sais:
And here is what I get in reality:
Has this worked before in a previous version?
🔬 Minimal Reproduction
Taking this config file:
And having the consensus layer (prysm beacon-chain) and the execution layer (geth) running in the same k8s pod (meaning it's on the same localhost network).
prysm validator --datadir ./ --chain-config-file ./consensus.config.yml wallet create --wallet-dir .
prysm validator --datadir . --chain-config-file ./consensus.config.yml accounts list --wallet-dir . --show-deposit-data
Error
Platform(s)
Linux (x86)
What version of Prysm are you running? (Which release)
v4.1.1
Anything else relevant (validator index / public key)?
Have tried with main net, got the same behaviour.
Can provide the genesis.json file as well if it's really needed.
The text was updated successfully, but these errors were encountered: