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
{{ message }}
This repository has been archived by the owner on Jan 19, 2022. It is now read-only.
Andrew: I ran into one instance where my docker crashed and the image and data dir were corrupted somehow, and I had no backup of to restore. Ended up losing that validator. And as much as I like Docker/Bezel images vs local binaries, neither are particularly well known for error proof stability.
Possible solution(s)
Duplicate folder on validator creation (with just the keys)?
If you generate your keys according to EIPs 2333 and 2334 -- a set of standards that describe how withdrawal and signing keys are related, and how they can be derived from a single mnemonic -- then all you need to do is keep your mnemonic in a safe place. Deposit Launchpad helps enforce this.
Problem
Possible solution(s)
Duplicate folder on validator creation (with just the keys)?
If you generate your keys according to EIPs 2333 and 2334 -- a set of standards that describe how withdrawal and signing keys are related, and how they can be derived from a single mnemonic -- then all you need to do is keep your mnemonic in a safe place. Deposit Launchpad helps enforce this.
References
Original tweet
The text was updated successfully, but these errors were encountered: