Skip to content
This repository has been archived by the owner on Jan 19, 2022. It is now read-only.

Data corruption, no backup #2

Open
unixpi opened this issue Jul 23, 2020 · 0 comments
Open

Data corruption, no backup #2

unixpi opened this issue Jul 23, 2020 · 0 comments

Comments

@unixpi
Copy link
Contributor

unixpi commented Jul 23, 2020

Problem

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.

References

Original tweet

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant