Provisional in-wallet help
There are two situations where a wallet needs to be migrated. Older JSON wallets are migrated to the latest database format. And more recent database wallets are also migrated to the latest format when necessary.
If your wallet migrated successfully, just click the finish button and this wizard will close and your wallet will open.
All wallet migrations back up the wallet within the same directory the original wallet file is located. The process can be illustrated as follows:
mywallet
.mywallet
to
mywallet.backup.1
. If that file name is already in use, then it will
increase the number at the end. It will try and use mywallet.backup.2
,
and if that fails it will try mywallet.backup.3
and so on.mywallet.sqlite
For the most part, there will not be any problems encountered when migrating your wallet. But some wallets will fail to migrate, and if that happens to you, you should be able to use the information below to aid you in discovering why or what to do in this situation.
There is only one identified situation where wallet migration fails. This is where the wallet data is incomplete, and the migration process cannot link it together and finds that data it needs is missing.
Open the wallet using ElectrumSV 1.2.5 and wait for it to synchronize. Make sure it connected to the network to do so, and that it is fully up-to-date. In order to maintain sane wallet file names you may want to:
.sqlite
migrated wallet..backup.1
file to it's original name.Otherwise, please follow these steps:
-v=debug
. For
example:/Applications/ElectrumSV.app/Contents/MacOS/1.3.13 -v=debug
ElectrumSV-1.3.13.exe -v=debug