> I don’t know how to do this in Dappnode yet, but its probably just a matter of using your divine god-like index finger, the Dappnode way.
You can back-up your validator's file and download a .tar that contains the same file structure used by Prysm in the ethdo wallet. Then you can point ethdo and Prysm to consume that directory and validate with that keys. But as you said, be extra careful to not get slashed!
> Something I kinda weird I found on this part is that [in DAppNode] you have to send the Eth to an intermediary address?
Integrating the deposit account lets you skip a few setup steps. This is there to make the whole process of setting up test validators as easy as possible so as many people as possible try it out. Of course, when we get closer to mainnet this will not be an allowed method, and we will encourage people to stick to physical devices or other more secure ways
Any chance you’ve migrated from a downed machine to a new build using the same validator keys successfully? Im aware of copying the validator db to avoid penalties, but with a live mainnet 32 ETH at stake, it’s a bit of a high-dive so would be interested to get your take.
Thanks for the great info, I’m the cryptostewar subscriber email address. Cheers.
> I don’t know how to do this in Dappnode yet, but its probably just a matter of using your divine god-like index finger, the Dappnode way.
You can back-up your validator's file and download a .tar that contains the same file structure used by Prysm in the ethdo wallet. Then you can point ethdo and Prysm to consume that directory and validate with that keys. But as you said, be extra careful to not get slashed!
> Something I kinda weird I found on this part is that [in DAppNode] you have to send the Eth to an intermediary address?
Integrating the deposit account lets you skip a few setup steps. This is there to make the whole process of setting up test validators as easy as possible so as many people as possible try it out. Of course, when we get closer to mainnet this will not be an allowed method, and we will encourage people to stick to physical devices or other more secure ways
Hmm... interesting. Which setup steps are skipped by using an intermediary smart contract?
(btw, thanks so much for answering my Dappnode questions!)
Any chance you’ve migrated from a downed machine to a new build using the same validator keys successfully? Im aware of copying the validator db to avoid penalties, but with a live mainnet 32 ETH at stake, it’s a bit of a high-dive so would be interested to get your take.
Thanks for the great info, I’m the cryptostewar subscriber email address. Cheers.
FYI (as of early 2019) Lighthouse has an Apache 2.0 license :)