Slashing protection for migration not working
Opened this issue · 1 comments
0xminimus commented
I’m trying to migrate a validator to another machine, following instructions here:
https://docs.prylabs.network/docs/advanced/migrating-keys
But when I try to export slashing protection I get this error:
root@gbc-prysm:~/prysm/gbc# docker run -it -v /root/prysm:/output -v /root/prysm/gbc/wallet:/wallet ghcr.io/gnosischain/gbc-prysm-validator:v2.0.4-gbc -- slashing-protection-history export --datadir=/wallet --slashing-protection-export-dir=/output
[2022-05-20 22:32:53] WARN flags: Running on Ethereum Consensus Mainnet
[2022-05-20 22:32:53] INFO historycmd: This command exports your validator's attestation and proposal history into a file that can then be imported into any other Prysm setup across computers
[2022-05-20 22:32:53] FATAL Could not export slashing protection file: could not export slashing protection history: genesis validators root is empty, perhaps you are not connected to your beacon node
k1rill-fedoseev commented
I think you should try to use --datadir=/wallet/direct
instead. That's what we are using in our docker-compose configs for slashing protection export. Alternatively, you may try using validator-export-slashing-protection
service from our docker-compose config files, it should work fine even for a different database version.