0 sats \ 4 replies \ @jimmysong 30 Aug 2023 \ parent \ on: Need help recovering wallet from 2010 bitcoin
The really odd thing here is the 5-letter hex found in the second column of the first 4 lines. Hex almost always come in pairs as each byte is 8 bits and each hex letter is 4 bits.
So doing some math 15 bytes in first chunk, 9 bytes, second chunk. 16 bytes third chunk, 4 bytes fourth chunk. 40 bytes is too much for a private key (they're 32 bytes) and 24 could be it, I guess. I can write you a script that you can run to check if the 24 bytes come out to the address you were looking at. I'm guessing it's uncompressed SEC since it's so early, and that's a detail you're going to need to know about for address generation. DM me on Twitter if you want to try it.
Sorry, that was an accident when writing the example. Every block is only four characters. How does that change things?
The only other thing I can think about if nothing else works, is I took the Bitcoin Core backup it gave me and converted it into to HEX, so if someone found it they wouldn't know what is was.
We hear all about these examples now, but I wasn't aware of those risks back then.
reply
12 bytes/8 bytes/16 bytes/4 bytes
There's no obvious way to get 32 bytes, which is the typical length of a private key. I guess it could be that the last 4 bytes are not anything and the first 3 chunks are 32 bytes + 4 byte checksum. If it were and you had those question marks in those places, that's 10 question marks or 40 bits that you have to roll through or 2^40 of attempts. That's about a trillion different possibilities, which is doable, especially with some GPUs. I did 2^44 in about 2 days a while back and that cost about $800 to rent the requisite GPUs if I remember correctly. So, 2^40 should be 1/16th of that, or 3 hours and $50? But there's some custom code that needs to be written to calculate the address and there's no guarantee that that's what these letters mean.
reply
Thanks, I'll reach out by DM on Twitter.
reply
deleted by author
reply