Armory PaperBackup

[A720]

Hi

I have Problems with one of my old Armory PaperBackups

I have the Wallet Unique Id and MainAddress
and the Password

Problem is i dont have the File any longer

and the Paper is kinda damaged on the edge
last 4 digits in every Line not readable

a = known  x = unknown/not readable

RootKey

aaaa aaaa aaaa aaaa aaaa aaaa aaaa aaaa xxxx

aaaa aaaa aaaa aaaa aaaa aaaa aaaa aaaa xxxx


ChainCode

aaaa aaaa aaaa aaaa aaaa aaaa aaaa aaaa xxxx

aaaa aaaa aaaa aaaa aaaa aaaa aaaa aaaa xxxx


help would be really appreciated

[1715478304]

1715478304

[1715478304]

1715478304

[1715478304]

1715478304

[1715478304]

1715478304

[1715478304]

1715478304

[1715478304]

1715478304

[goatpig]

The last 4 characters are checksums. The actual 16 bytes of data per line are encoded in the first 8 "words". You can write gibberish for the last 4 characters if you want. Armory will complain the checksums are invalid and will ask you to explicitly check the proposed wallet id with the one written on your backup. If the two match, you're all good.

[A720]

It took some time to get 4 characters per line that worked
problem is when i change the last 4 it also changes the Wallet uniqe id
and they dont match sadly
how is the checksum per line calculated?

[goatpig]

Last 4 characters shouldn't affect the final ID. Maybe you are getting combinations that have a "repair" candidate. At any rate, you can only use characters from the narrow set.

This is the character set:

https://github.com/goatpig/BitcoinArmory/blob/master/armoryengine/ArmoryUtils.py#L2246

This is the checksum calculation:

https://github.com/goatpig/BitcoinArmory/blob/master/armoryengine/ArmoryUtils.py#L2265
https://github.com/goatpig/BitcoinArmory/blob/master/armoryengine/ArmoryUtils.py#L2404

The hash function is 2 passes of sha256

[HCP]

The last 4 characters are checksums. The actual 16 bytes of data per line are encoded in the first 8 "words". You can write gibberish for the last 4 characters if you want. Armory will complain the checksums are invalid and will ask you to explicitly check the proposed wallet id with the one written on your backup. If the two match, you're all good.

I have tried restoring a dummy wallet using random characters for the last 4... and I get an error:


This happens if I use blanks, or just random like aaaa... or just repeat one of the other 4 letter groups... it seems it'll only work if I get at least the first 2 letters of the checksum correct, then the last 2 can be anything.

[goatpig]

I've reworked this code into the C++ side recently, I may be confusing the old functionality with the new one. He could get his wallet to restore by modifying the Python code to ignore checksum errors.

[A720]

Thanks a lot for the help !


i managed to manually brute force it

16x16 possible letters per line - so 4x256
aaaa - adaa - aeaa ------ > awaa - daaa - ddaa - deaa  and so on ..


if its the correct first 2 letters  the last 2 dont matter  - of the 256 trys per line
i got between 15-20 working combinations but only one was not producing errors when changing
the last 2 from aa to something else

im new here - is it against the rules to send/post btc adresses here on the forum?

[goatpig]

im new here - is it against the rules to send/post btc adresses here on the forum?

I don't think so, some people post theirs in their signature even.

[HCP]

im new here - is it against the rules to send/post btc adresses here on the forum?

No, it's not against the rules to post BTC addresses... but depending on your personal level of "paranoia", it's advisable to consider what you do and don't share from a privacy point of view


Note that "begging" (ie. asking for people to send you money) is against the forum rules... so posting an address and saying "please send me money" would be against the rules.

Refer "Rule 7" in the "Unofficial Forum Rules": https://bitcointalk.org/index.php?topic=703657.0

[A720]

ok -> thanks again !