Automatic support of upgrade best practices #395
Description
Describe the issue
The community is receiving recommendations that place less knowledgeable users in danger. If these posted recommendations are the best operating procedure, then they should be automated and require no human interaction.
Importing and exporting private keys leads to user and security risks that can be easily avoided.
Expected behavior (tell us what should happen)
On a major upgrade, format change, etc., the wallet should automatically perform the prescribed upgrade's best practices.
- Detect saved wallet version.
- If wallet version is good, return success
- If wallet version is old, backup, port keys to new wallet, delete files to perform fresh sync, etc.
- If everything works return success
- If not return failure and recommended recovery solutions or a link to help.
Over generalization and simplification, but to ensure widespread adoption happens we need to make sure that the upgrade process is seamless and requires no user intervention. If we upgrade from one database version to another, we need to have a helper utility that can read and export older versions. We also need to ensure that the upgrades best practice does not put undue stress on the user or the network. If I'm a business user I don't want an upgrade to take 8 hours to resync on my slow machine just to use utility that should have taken me 10 seconds. For example, my doctor's office just upgraded their system and they can't access my records because it's syncing.
What platform are you using (Linux, Windows, Mac)
All