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
I know it the process might look a bit opaque and probably needs to be a bit better documented, but not sure I'm wholly in agreement here.
If the user backs up the entire wallet, it's a copy of the wallet.seed + the wallet_data directory. However, unless the wallet is backed up after each and every transaction, there will always be a need to run wallet restore with the seed file to recover any outputs that may have been created after the backup. Therefore, unless the wallet is backed up on each and every transaction, it's pointless to back up the wallet_data directory.
So all a grin wallet backup command would do at the moment is copy the wallet.seed file somewhere else and rename it. Surely at the moment it's possible to just output something to the effect of put a copy of this file somewhere safe when running grin wallet init?
Of course we'll ultimately want a BIP39 mneumonic as well, and the key derivation will change somewhat, but I wouldn't expect the backup process (keep a file somewhere safe) to change much.
Backup of a grin wallet is currently a manual process that is opaque and error prone.
Introduce a
grin wallet backup
subcommand that automatically backs up a user's wallet in a format compatible for futuregrin wallet restore
commands.Specification:
Relevant chat thread.
The text was updated successfully, but these errors were encountered: