etotheipi / BitcoinArmory

Python-Based Bitcoin Software
Other
827 stars 621 forks source link

Test backup doesn't work? #157

Open natefinch opened 10 years ago

natefinch commented 10 years ago

I made a paper backup and wanted to test it, so I used the test backup feature (btw, it probably needs its own menu item, since it's hard to know that you need to go to "import or restore wallet" to test your backup).

I went to test my backup, and entered the two lines of text under "root key", however, I'm not sure what, if anything needs to go under chain code (the paper backup from Armory doesn't seem to have anything labelled chain code). After entering the root key, I hit test backup and.... nothing happened. Is something supposed to happen?

Also, usability note - when I went to enter the root key, I clicked in the center of the top text box, and instead of starting the cursor at the start of the text box, it started in the middle somewhere, so I got halfway through typing the key and ran out of room. It was not very obvious what the problem was.

etotheipi commented 10 years ago

Are you using an intermediate build? Like version 0.89.99.X? Because the problem with the cursor starting in the middle of the line was fixed in 0.90.

Also, wallets created with version older than 0.90 have four lines instead of two. The last two are the chaincode. These four-line backups are called "Version 1.35". The ones that only have two lines are "1.35c" (because the wallet code/format is the same, but the data is derived differently and only requires the backups to change, not the wallets). In version 0.90-beta, there is a drop-down box at the top that has you select the version you are restoring. Most likely, you are using 1.35c. Once you select the proper one, there will only be two lines to fill.

It sounds like we should add a popup that points this out if the person has it set to 1.35 but only enters two lines.

natefinch commented 10 years ago

Yeah, I'm on 89.99.14, sorry, should have mentioned that. Armory says I'm up to date, though. Should it say I need to upgrade?

The version thing was a little confusing... maybe the test should default to the same version it produces?