Bitcoin Forum
April 16, 2024, 08:33:11 AM *
News: Latest Bitcoin Core release: 26.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Legacy wallet, SecurePrint Code length does not match?  (Read 132 times)
FiveCirclesTheorem (OP)
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
March 05, 2021, 03:14:09 AM
Last edit: March 06, 2021, 05:10:07 PM by FiveCirclesTheorem
 #1

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.
1713256391
Hero Member
*
Offline Offline

Posts: 1713256391

View Profile Personal Message (Offline)

Ignore
1713256391
Reply with quote  #2

1713256391
Report to moderator
The trust scores you see are subjective; they will change depending on who you have in your trust list.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1713256391
Hero Member
*
Offline Offline

Posts: 1713256391

View Profile Personal Message (Offline)

Ignore
1713256391
Reply with quote  #2

1713256391
Report to moderator
1713256391
Hero Member
*
Offline Offline

Posts: 1713256391

View Profile Personal Message (Offline)

Ignore
1713256391
Reply with quote  #2

1713256391
Report to moderator
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3654
Merit: 1345

Armory Developer


View Profile
March 07, 2021, 11:33:54 AM
 #2

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.

FiveCirclesTheorem (OP)
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
March 09, 2021, 06:54:06 AM
 #3

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...
FiveCirclesTheorem (OP)
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
March 09, 2021, 07:00:21 AM
Last edit: March 09, 2021, 07:35:11 AM by FiveCirclesTheorem
 #4

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...
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3654
Merit: 1345

Armory Developer


View Profile
March 09, 2021, 02:40:47 PM
 #5

I don't touch users' root keys. You'd have to elaborate on the error you're experiencing and give me log files.

FiveCirclesTheorem (OP)
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
March 10, 2021, 02:29:08 AM
 #6

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...
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3654
Merit: 1345

Armory Developer


View Profile
March 14, 2021, 07:55:13 PM
 #7

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.

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!