Hi all
I have a wallet on blockchain.info for which I've forgotten the password. I believe I know almost all of it, so figured I'd use btcrecover to try and recover.
However, in order to use btcrecover, I need the encrypted payload from the wallet.aes.json file and I'm having zero luck in obtaining it.
There are two methods which I've heard work for other people and neither works for me. I'm wondering if something has changed on blockchain.info to block access or whether there is something unique about my environment that is causing the problem.
Approach 1: Go to
https://blockchain.info/wallet/<insert wallet ID here>?format=json
The resulting webpage should contain a payload section containing the information I need. Indeed, this does happen when I'm accessing a wallet which I've previously logged into successfully from my computer (I presume due to a cookie?). However, the wallet I need to access is older and I don't have access to any machine where I might have previously logged in. When I try to access the wallet using the URL above, I'm greeted with the "Authorization required. Please check your email." message. I still have access to the original verified email address, so I receive the email and I click to authorize. It shows a Success message and then says to return to the original web page. I do so and attempt to reload, but the result is unchanged... I'm still met with the ""Authorization required. Please check your email." message.".
This approach seems to be a dead end.
Approach 2:Use the "download-blockchain-wallet.py" script from the btcrecover package to pull the necessary information. The situation is the same as Approach 1... the script works fine as long as I've already logged into the wallet on the computer, but returns the "Authorization required. Please check your email." message and then goes into a 5 second "retry" loop that never completes if I'm trying to access a wallet for the first time on that machine. I receive the auth email, but since the script isn't a browser, it's returning as "Unknown browser". When I access the auth URL provided, the page that returns notes that I'm accessing the Auth URL from a browser different from the one that initiated the contact request and asks me whether I want to authorize. I click to authorize and see "Success", but the script never succeeds due to authorization still being required.
I thought I would be clever and use curl to access the auth URL from a command line to circumvent the apparent browser ID issue, but this just fails miserably with a "javascript required" message returned.
In short, another apparent dead end.
So, esteemed experts... can any of you shed light on whether you are still able to access the wallet.aes.json information using the above techniques? NOTE: To accurately test, you must try and access a wallet from a computer that has never accessed that specific wallet...if you've previously successfully logged into that wallet from the computer you're using to test, the techniques above work fine, so no point in testing that. If others are able to do this, I'll at least be able to isolate the issue to something about my environment and hopefully get it sorted. Any help on this is greatly appreciated.
Secondarily, if neither of the above techniques still work, does anyone have a suggestion on how to access the wallet.aes.json information?
Before anyone suggests opening a ticket with support, I've already asked blockchain.info support and they flatly refuse to help, despite the fact that I'm using the original verified email address and am willing to provide any required supporting documentation to establish my identity and that this is a legitimate request. It's very frustrating. The funny part is, there's barely any value in the wallet (<US$10 worth)... at this point, it's more a matter of principle!
Thanks in advance to anyone who is willing to help.
