Re: Recovering 33 character private key from legacy blockchain.info wallet
Yes, i have tried doing using blockchain import tool.
Doesn't recognise the file.
Although the last transaction i remember on the wallet is from 2013, it could have been created even earlier. (2011-2013)
Doesn't recognise the file.
Although the last transaction i remember on the wallet is from 2013, it could have been created even earlier. (2011-2013)
What file name did you use when dropping the file? I know blockchain can behave weird if you dont name the textfile exactly wallet.aes.json
/KX
I made multiple tries. wallet.aes.json and so on.
I also managed to access mine blockchain.info wallet just now and download it + decrypt it. The private keys matches. So the key that is problematic was somehow imported into blockchain.info and it was considered it valid at some point. Same private key is present in JSON unencrypted blob in 2020. Some sort of hint is, that the wallet was used around 2013.
It's been a long time since I've looked at a wallet.aes.json file, but 33 characters doesn't seem long enough to me. Hopefully, I'm wrong. Have you tried this yet?
https://github.com/blockchain/my-wallet-backup-decryption-tool
https://github.com/blockchain/my-wallet-backup-decryption-tool
Yes i have tried it after downloading encrypted wallet from blockchain.info and using this tool, to see what blockchain.info stores in it's JSON blob.
Such test, completely overrules scenario where backup file was somehow modified/had its integrity violated. The exact same private is being returned by blockchain now in JSON, after downloading wallet using btcrecovery python tools in 2020. This results in exactly same weird 33 characters private key.
When interacting with BC.info user interface - the key shows up in "Imported Addresses" and while clicking on "Show private key" on blockchain.info it displays "Unsupported Private Key".
So TLDR: I managed to access blockchain wallet using web interface and their "GUID" login, but i cannot make any transactions or export private key - as it shows up as invalid/unsupported one. The 33 character private key from 2013 backup is the same as from 2020 backup. Scenario where backup is corrupted is excluded i think. Therefore the key at some point was considered valid by blockchain if it end up being in wallet backup.
If someone manages to provide a good hint, i'll make sure you get paid.
