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
Right now, we don't help backup node keys and expect our users to manage it themselves.
This is especially problematic when using leave-network, which blasts the sidechain directory.
I propose one of the following:
Bare minimum, leave-network should drop keys into ~/.hydra/backups/{name}, possibly also including other relevant backup stuff (like config.toml or loom.yml)
Alternatively/additionally, maybe it would be appropriate to consider adding something like hydra client save-identities --profile=my_node to backup the keys, and then a corresponding restore-identities option
The text was updated successfully, but these errors were encountered:
Right now, we don't help backup node keys and expect our users to manage it themselves.
This is especially problematic when using
leave-network
, which blasts the sidechain directory.I propose one of the following:
Bare minimum,
leave-network
should drop keys into~/.hydra/backups/{name}
, possibly also including other relevant backup stuff (like config.toml or loom.yml)Alternatively/additionally, maybe it would be appropriate to consider adding something like
hydra client save-identities --profile=my_node
to backup the keys, and then a correspondingrestore-identities
optionThe text was updated successfully, but these errors were encountered: