|
Title: Legacy wallet, SecurePrint Code length does not match? Post by: FiveCirclesTheorem on March 05, 2021, 03:14:09 AM I created a wallet some years ago, and made a paper backup with Secure Code, which is also written on the paper.
And recently I tried to import it back but find the Secure Print code wrong. So I created another wallet for test, and found that the Secure Print code of the new wallet contains 11 letters, but my old wallet 13. Is it because the version of Armory or something? I cannot remember much. Any advice is welcomed. Title: Re: Legacy wallet, SecurePrint Code length does not match? Post by: goatpig on March 07, 2021, 11:33:54 AM The SecurePrint password is the base58 of the first 7 bytes of the hash of your root key. Depending on the "integer" value of these 7 bytes, the length of the SP password may vary.
Title: Re: Legacy wallet, SecurePrint Code length does not match? Post by: FiveCirclesTheorem on March 09, 2021, 06:54:06 AM The SecurePrint password is the base58 of the first 7 bytes of the hash of your root key. Depending on the "integer" value of these 7 bytes, the length of the SP password may vary. Thank you for your explanation. So what should I do when I’m not able to restore it...Title: Re: Legacy wallet, SecurePrint Code length does not match? Post by: FiveCirclesTheorem on March 09, 2021, 07:00:21 AM The SecurePrint password is the base58 of the first 7 bytes of the hash of your root key. Depending on the "integer" value of these 7 bytes, the length of the SP password may vary. If I send my root keys to you, is it possible to restore the wallet?My wallet contains no bitcoins, but I need some addresses where it used to send... Title: Re: Legacy wallet, SecurePrint Code length does not match? Post by: goatpig on March 09, 2021, 02:40:47 PM I don't touch users' root keys. You'd have to elaborate on the error you're experiencing and give me log files.
Title: Re: Legacy wallet, SecurePrint Code length does not match? Post by: FiveCirclesTheorem on March 10, 2021, 02:29:08 AM I don't touch users' root keys. You'd have to elaborate on the error you're experiencing and give me log files. 1. I have the paper backups with root keys and Secure print code.2. Maybe I have encrypted the secure code but it was a long time and there was no notes, so I could not remember. 3. I tried several times and checked if I wrote the root keys and the secure code right... 4. I can give you the log files but if I did encrypt the secure code then it would be just my own fault and there would be no bugs... Title: Re: Legacy wallet, SecurePrint Code length does not match? Post by: goatpig on March 14, 2021, 07:55:13 PM 1. I have the paper backups with root keys and Secure print code. 2. Maybe I have encrypted the secure code but it was a long time and there was no notes, so I could not remember. 3. I tried several times and checked if I wrote the root keys and the secure code right... 4. I can give you the log files but if I did encrypt the secure code then it would be just my own fault and there would be no bugs... 2. There is no such feature in Armory. Unless you went out of your way to do it manually, I don't expect that to be the case. 3. You need to elaborate on how it fails. Are you getting an unexpected wallet id? Is nothing happening instead? 4. Logs would give me a clue as to what the failure is. Again, idk how you'd end up with encrypted SP pass unless you did that manually using some 3rd party software. |