Bitcoin Forum

after recovered damaged WIF key about a yr ago got abit passive and failed to download all wallet.aes.json in time for the walletID that are known (email) but password and seeds were unknown because fireproof bag was hidden and forgotten.

Long story short really old skewl stacks of 2013-'15 era blockchain.info printed paper wallets were recently found in fireproof bag, with wallet ID entered in the following format:
????????-????-????-????-????????????
and password
and of 19 word non standard blockchain.info recovery seeds.

few walletID paper even had what I believed was backup: several QR code - no its not contain QR code to WIF (in earlier days you could print sheet with all P2PKH + WIF keys but this is not it), but after scanning each one consecutively and concatenate together it appears to be encrypted json backup of sort. pbkdf2_iterations version 2 payload "blahblahblahveryverylongstringcompleteblahblah" is shown.  This was dumped from javascript console from var/obj that believed to hold the encrypted wallet back in 2016 or so (before download-blockchain-wallet.py) was available, and extra attempts were made to try to backup from client side .js memory - as I believe (at the time) that blockchain.info is doing java script kung-fu in memory and session data had all the information needed relating to each wallet-guid instance.

knowing one day I would eventually encounter lost hand hodl (now diamond hand hodl) bag (just as predicted, by accident), back in 2022 I even made attempt to download wallet.aes.json for one that I remembered to have most balance (after scrolling thru email), and waited.

btw contrary to belief blockchain email don't actually contain backup of wallet.aes.json.  was using recovery download-blockchain-wallet.py 3 years ago to download encrypted wallet.aes.json but still unable to open it because did not have time to btcrecover with different wallet guid / possible password pairs.  Now password and non BIP39 mnemonic in the fireproof bag was found it should be super easy to recover if wallet.aes.json for each guid can be retrieved.

as BTC is approaching 99999 finally I started to think that blockchain.com won't easily make it diamond hand hodl friendly.  So I begin to unseal / access the fake make belief self-custody wallet.  Sure enough:

When hitting Blue Continue button, following messages (in the order which) appears briefly

obtain account info
Decrypt wallet data
obtaining encrypted data
Migrating Data

Then red "Invalid Token" is than shown below Email or Wallet ID Field!

the password is correct, because if incorrect password entered field  "Password" would throw different error - "Password doesn't match.  Try again." would appear

and when using login.blockchain.com/beta/auth/recovery "Input your Recovery Phrase" error - "Invalid Recovery Phrase" error was thrown.

I tried https://login.blockchain.com/beta/legacy-pages/forgot-password.html?guid=????????-????-????-????-????????????

but it throws Unknown word rejecting
Unknown word midas or tickers
Unknown word incessant
...
...
and so on.

Then I tried to recover with wallet.aes.json from most valuable wallet I believe that was downloaded in 2022 with download-blockchain-wallet.py assist actually turned out to be super easy to recover, since no cracking was needed (passwords were correct as they were written down on wallet paper backup)

I did python3.11 btcrecover.py --wallet wallet.aes.json --dump-wallet wallet2.txt --correct-wallet-password mypasswordfoundinfireprofbagpaperwallets2024 and waalaa! all the WIF and Pubkey was found when cat wallet2.txt.

bcore28 importdescriptors (getdescriptorinfo "wpkh(WIF) found hasprivatekeys:true and has #???????? checksum  ) works and recovery was successful

Now I wish there are ways to make https://login.blockchain.com/beta/legacy-pages/forgot-password.html?guid=????????-????-????-????-???????????? available again, or make download-blockchain-wallet.py work again (which it throws errors)
Traceback (most recent call last):
  File "download-blockchain-wallet.py", line 76, in <module>
    auth_token = do_request_json("sessions", "")["token"]  # a POST request
  File "download-blockchain-wallet.py", line 72, in do_request_json
    return json.load(do_request(query, body))
  File "download-blockchain-wallet.py", line 66, in do_request
    return urllib2.urlopen(req, cadefault=True)  # calls ssl.create_default_context() (despite what the docs say)
  File "/usr/local/lib/python2.7/urllib2.py", line 154, in urlopen
    return opener.open(url, data, timeout)
  File "/usr/local/lib/python2.7/urllib2.py", line 429, in open
    response = self._open(req, data)
  File "/usr/local/lib/python2.7/urllib2.py", line 447, in _open
    '_open', req)
  File "/usr/local/lib/python2.7/urllib2.py", line 407, in _call_chain
    result = func(*args)
  File "/usr/local/lib/python2.7/urllib2.py", line 1241, in https_open
    context=self._context)
  File "/usr/local/lib/python2.7/urllib2.py", line 1198, in do_open
    raise URLError(err)
urllib2.URLError: <urlopen error [Errno 8] Name does not resolve>

FYI, you can get rid of all the ??? by editing your post, clicking on + Additional Options... at the bottom, and selecting Don't use smileys.

Seriously, it's hard understand the full situation with that wall of texts while talking about separate blockchain(dot)info wallets  :-\
It would be better if you identify which one was described in that previous attempt and which one was recovered in that last part. (e.g.: walletA, walletB)

You're not the only one who got that error when pasting their version3 mnemonic (https://web.archive.org/web/20240922032019/https://login.blockchain.com/legacy-pages/js/mnemonic/mnemonic_words_v3.txt) to their legacy import (forget-password) page.

However, even if it proceeds, it'll just show you your password which you already have.
Or is this for another wallet aside from the one your tried to login and the one you've successfully imported to Bitcoin Core?

For the former, you may ask them to support v3 mnemonic (e.g. via Bug Report Issue),
Here's GitHub Organization: https://github.com/blockchain (https://github.com/blockchain), try it in their "blockchain-wallet-v4-frontend" repository since their current v5.0.87 beta wallet isn't available.

For the latter, compatibility was broken.
The owner of the new BTCRecover fork has a tutorial on how to download the wallet file here: /docs/Images/download_blockchain_com_wallet.png (https://github.com/3rdIteration/btcrecover/blob/66121eab54380dc7dd3b27c14d0d32e3a3ccbd14/docs/Images/download_blockchain_com_wallet.png)
But it's the same from: https://blockchain.info/wallet/<YOUR_WALLET_ID>?format=json which doesn't work in the latest version.

I have the same problem. Invalid token error while accessing my wallet in Blockchain. Please help if you found a solution.

I contacted the Blockchain support but they were of no help

That's a bug in their new wallet beta version, something that only they can fix.
Your other options should be similar to what OP did to his other wallet but that requires a copy of your "wallet.aes.json" file that is now hard to fetch from their server.

If you want to continue, include more information like what OP did (but more organized) and post it as a new topic.
E.g.: What data and file you have (but don't actually post or PM those to anyone), which link and tools you've previously tried
Use the small "new topic" button in Web Wallets board, at your right-hand side: https://bitcointalk.org/index.php?board=222.0 (https://bitcointalk.org/index.php?board=222.0)

Hey! Thank you for the reply but i am not tech savy nor i am sure which detailed info to be shared like OP did (don't want my wallet to be hacked).

I hope they fix the bug or someone finds a sure shot solution and guide us on how they fixed it.

I'll be checking this thread regularly and if someone finds a solution please please do mention it. (I am willing to send some coins as token of appreciation to anyone who was able to fix the problem)

I have this same issue (I think?). Does Blockchain.info have some public bug tracker where I could follow when this bug gets fixed?

They have a GitHub Repository page where issues can be posted: https://github.com/blockchain/blockchain-wallet-v4-frontend/issues (https://github.com/blockchain/blockchain-wallet-v4-frontend/issues)
But those are mostly user-reported issues and not the ones found by the developers, this thread's issue isn't reported there.
Additionally, the version used in the online/app wallet is v5.x while the highest available repository version is v4.

They also have a bug bounty program in "Hackerone" but that's for security issues and the solved bugs aren't and will not be disclosed.

Let's report it so they know a lot of users are facing this issue and so they can come up with a fix


https://github.com/blockchain/blockchain-wallet-v4-frontend/issues/6526

The link is invalid, have you finished posting the issue or was it deleted?
AFAIK, it's shouldn't be deleted since there's no duplicate, unless you haven't provided enough information.
The previous issue 6525 is even worse in that regard though.

But as I've said in my previous reply, that repository is for v4 online wallet and not the currently active beta v5 wallet.
It's better to send it via their contacts; email or through cs.

I have the exact same issue with several old wallets at blockchain.com where I have the correct identifier and password, the newest wallet that gives the "invalid token" error was created in 2015. The last time I logged in to it was in 2021. I don't see this issue mentioned before this thread, does this mean that the issue appeared just recently, then hopefully maybe they can fix the issue. I've tried to talk to the support but it has been a struggle so far, but maybe it's because they don't recognise the issue because of its novelty. I sure hope we can solve this  :(

I think OP is the first to report this issue here but IIRC, I've been having login issues since November last year but it's just a "test wallet" so I don't have any reason to post this as an issue topic.

I don't know if this'll apply to your and OP's case but after testing a few options:
I've managed to restore with my test account's 12-word recovery phrase in their Android App then disabled 2FA SMS within the app, after that, I can login to the web version without any errors.
But I don't have the means to confirm if it's the cause of the error or they just fixed the previous error that I'm getting when logging in my test account.

I tried this before in the web version last year, it worked once, but lately, it consistently resulted with an error once it reached the login phase.
Not surprising since they must be changing and fixing things while it's still in "beta" phase. (they shouldn't have used their regular clients as beta testers though)

If that didn't work, it's better if you can reach their "technical support" (reach them via CS) since they know and have access to their v5 wallet's code.

I'm guessing it doesn't apply to me since I don't have any recovery phrase, just the identifier and password. I wish the "invalid token" issue existed in a separate thread, OPs post is almost incomprehensible to many of us novices and the talk of wallet.aes.json and pass phrases muddies the waters regarding the specific issue of not being able to log in to old wallets with the correct identifier and password. The latest wallet I have that is no longer functioning was created in 2015, surely there will be plenty of others that will discover that their old funds are no longer accessible.

Any update for this? My friend and I have same problem..

---

Hv u tried to contact their customer service?
They asked for login access, i didn't want to give them that. They should allow users to keep using the old login page, instead we are forced to use the new beta version.

---

Tried your suggestion. It gave an error warning, the resetting wallet failed on android, then suddenly was able to log in, put pin code, the synchronize page showed, then back to pin code page again, repeating without stopping. This is terrible.

Sorry, aside from the previous test that I did, I have no other means to test their app/web wallet.
I now can't reproduce the issue because the only test account that I have can now log-in without issue since then.

Since you have you recovery phrase anyways, you may be able to restore your DeFi wallet(s) in Electrum if you need access to your bitcoins.
That's if it's their new BIP39 seed which they generate as 12-word recovery phrase.

If so, Download Electrum: https://electrum.org/#download (https://electrum.org/#download)
And Verify it: https://bitcoinelectrum.com/how-to-verify-your-electrum-download/ (https://bitcoinelectrum.com/how-to-verify-your-electrum-download/)

Then restore the seed phrase via BIP39 seed option during new wallet creation window.
I just typed this in another thread, so I'll just quote myself here:

Since the original wallet where it came from is always online, I will not suggest the cold-storage option to restore.
But if you prefer it, here are the steps: https://electrum.readthedocs.io/en/latest/coldstorage.html (https://electrum.readthedocs.io/en/latest/coldstorage.html) (restore it in the offline machine instead of creating a new wallet)

I have but they haven't been much help and they currently stopped answering.

I noticed a pattern that all the old wallets that give me the "invalid token" error are wallets that are not connected to any email address. All my old wallets connected to an email are accessible, all the wallets that are not connected to an email address give the "invalid token" error. Is this true for you guys as-well?

I will try these steps. Thanks!


Did they ask u your email or login?
I don't remember if it's with or without email address, but yes possible. It's an old wallet for sure.

So far they asked for the identifiers and the dates when the wallets where created.

I have good news!

It seems that the lack of an associated email was part of the issue which gave the "Invalid token" error. I gave customer support the identifiers, approximate creation dates for the wallets and new email addresses that are not associated with any other blockchain.com wallet. With this information they managed to fix it and all my wallets are now accessible. So if anyone has an issue with "invalid token" this may be the solution. Hopefully this solution will spread within customer support because I'm sure there will be more people with this problem.

Thanks for the update.

When you say identifier, do you mean wallet id? Or some other information?

Yes, wallet ID.

I can confirm that I had this same issue and indeed the root cause was that there was no e-mail address attached to the account.

The customer service was able to solve the issue but it took a lot of messaging with them back and forth before they did.

Hi
I opened here an account in this site to answer this message!

I also get the same problem, when i try to login to my account it tells me invalid token, i am going crazy! When i opened the account in blockchain i didnt give them no email, nothing

I have juat my wallet i.d and my password, i even lost and forgot the 12 words they told me to remmember

I talked with the support, many times until they stopped to answer me anymore and all they told me is "if you cant tell us your email that is connected to your blockchain account we cant help you


And i messaged them so many times back that i didnt give them any email, nothing, when i opened my account, and they insaist to tell me that without my email they cant help me



What to do ?? I really go crazy, all of my money is in this blockchain account i am so frastrated, i tild them this, i told them that i cry all day long, and they dont help

maybe this helps someone in the future

hit the same issue (wallet without email, invalid token on failed migration after login, useless support)

what seems to work is to use this url to get the wallet info (save it to wallet.json)


(where UUID is your wallet id)

then use btcrecover to decrypt private keys


private keys are in keys.txt, create new wallet in electrum, use option to import private keys

let me know if it worked

Unfortunately it Didn't work, as I started to try to do what you told me and tried to enter this site :

https://blockchain.info/wallet/UUID?format=json

and I pot my wallet i.d instead the letters UUID as you said , and i just got a white window with letters and number and Nothing that can help me , it didnt enter me to the site of blockchain , it shows me this : (also it shows letters and numbers when i try to enter the link you sent me without replacing between UUID with my wallet i.d)

{"initial_error":"For Improved security add an email address to your account.","extra_seed":"c2e28f3f6e1886053f386c1fb024a19eecb0e0144aad2ee32cec56045a3f998655fcdcc0fea7389 055414202ee4855b51f8a5d097b64026954d9991c17a61c10","auth_type":0,"real_auth_type":0,"payload":"{\"payload\":\"Wp3ytnoqgI8sgnSycf50ivMz4jqZQzBN3BJOGWIbJ93vKj8uu\/t\/g5+RVpqt0XetufnIAbDjDn6xCdRsCrXnAYUOjVHoRz0Y8XeYJW9mFRt9ndHIgSlvFzJFXR8dJNlvVUJG5hmVE6Lls2vVlnHi4YG1tDIRGp3vn4fn8orSPQeBRJJ0qarLdyWylUpl6YECXt5VaC2k5cYs7jzpmqk8qNeNPWxt2b1DEHImzcwh81ZDxXkOeRuvvPGccxce28UyigUNBl9eHaZFfrXVRLEfaWk6idJiElQvpexJ2T\/PPr7YAtUYAqVPtyBfOSJjwrVM+e72Vak3GPASTfv1ayPNhH4yORvkXfrVjXbsa3hgbLGZ1lEDEHbyWUSaS7ivDwh8vEex7R+uK10NAisYO6alfkrk4nUDcN8pt2hYR1HOm8pX102lGxn4F7i37\/scapxlAZOOvc6Yw9LbGv97IvzqLiU\/oWUzFRz253H6G8jg3eWQMq66LX00qS6WUN7OCPwEuLXUmp9WZSYwOJu1en8t6j4GDPqvrJeUVKbcfTaTb8R14d9G6l50brvUjJmYyuVKVK9rMnIvNEZ9RkVWB2OeoEdJ8XLN874aCgLFtBmV\/Z3MEP+HVHMyxkm8v4FxsjSEJl9HluQB\/lRA+hVdGUgN3Z2LYpgn5QfjgFke6QYYUamWCeOXlzGxtMCZyTvqpm4t1EfTTXB3VO2DifCucxHHJY0VKPngGXlwvANE7azY31rzYwjB7P9CxLgpvGyY6r0rbu9+ci1uKKZbH4yvWs\/UgznafbV1C3Fwxt56K\/PLyaWj+iymG3+\/axp6O+RdXKW3RwGOPmN05O7oeuZ+bVmExIVvGQTdbhBZz8RguMDv6lrAjVn2v4I1YxnDukDCWZLDwQBrrT9ksMT4mEjWlO3ChiQPOlU\/SzlVd81pFOizcqq8xYp3m0JCnx2iyiYB+kaxFRtKtNsDu84l7r0iQKfOFV3+EKafAeMOYCHl9ikRy\/XLKQcFAOJxTqlhzvTdALZInyokVBnopYWipiaxqsJVLaUoss26z2Aap1Ca5I5AJVpsw6FXlk+jMpWnJXzEWhTbJ6NvvZyyrHBzpVZ6RuvWw8OTgAPfGQTdWV1HmhUHK8wQVcX+CoUs26dGxhPTUb8PCw+sEdEinQU8Q4\/kBNWSnSAkOwhOISOqV0\/2RGFa96DJPfRvJHX4wAUf5eLnk48GuT4pHieWHj8B6noujBwqRv0eaSMuHKjNNa4YjhuGh7C80F+gBqzu5Qk0yX1HouhRMTZSp9pbZMcDHaK6RzGnb7m+rrpp9wahef+qKofGw1usdoNejIwbRdWrAaTuJcS6NJffx424EMKSMLT5TQbb5xpS3UyZ6roz3LVPkgyTD5\/l\/8y93LmYWYm4yECyn96cfc8hmI6fLq120OSAD6w2nemYZgoZrCyLO6jCkTVRG0+XEAyqSh\/WSN0PhEnUdn+B+8PqWx0hcKlKSrtNNkRvraO\/laEBv8i7TOQMjjJTCgtYhHcWKO4Io5MTVoe6Zr57dImW334E83p6WOcbLSrFutwfHPQCw6pArGWWo1MOFePF3vjEmNvtc5bUUVCQPBfwK+ezsrzL8mZn+3yMxOqT6wxq394vwOWwrwSyo59zoBxEHX1+ja7M2jZMVFcD75Q8jLNKEh35+SVrqPVbv\/3WpUUMsygSqTf24vpN1oTfOgcpkfnGlaqSZJJt2V0q8Bz8Pn\/75R8Wnz1jclfqmRv20X274VLD0FOrVxNSvCNNQDoylVgQebqD3p2Z8QY1D6CH5C3PJyCANb66pdK5taZWNJ7VsKI0A2cVun\/IH6A8+eGAaAymlzjWKmTRou1Frx0d1ZM0LmMfOZ\/5AeX8uXIgRtnJ6LlfJteVTIrLCTSif0l8BgZ9lU8IX3tqsGMIXsZx+D6fY5mdlf0S65eeonUk\/c0VI9wOnK14CcLkkLnZDTDMrnzRb9zpPjCXxKgcnHuMRU7gHasSUFEdA0HAL\/ylSfNbwXWqN6Aw0H7zpHq3WZxXAtPrbAiiuFi6+tNV02Cw5yN3F1nFll5xOPBXWqkWsmRMKY\/TzNie+VxLVfY9ETSIjoUQWzDIc8fT5ToxOe6XuDgBM51cwu8CeD7qIeaGuxzpqoO7tov9dHlRaraCVN7ClQZ5l+xjWRmuJUikUXMelle3+C8zZH2hiCU4CN8W2xi5SSuY++LtAWransQgB5TzjFxHHIKlWNYhDa+FF\/8h0dzaeZEu8WQgPUevhiSbxaoYN8eD6y\/CokuEUd51XFA+TAg+Vq+U28ZCciURBgMxQxbXYR\/4\/vSPT30AU2B1wuEzidMV9KgyRr+ihICIWo4tMreRzqvDGjG\/rNXQIcTNOKM93eqgPRcnPUj0PiSZFAAq\/5n+f2j32U7CtOXwVJf5DQPgCiJJwnlkNKrE0i6z6q\/KMFe4IZ5PKLVDmVSrVHOr3Dg7tO9wQez+wvSX4\/xrVxsYYCnITTk7zMdTw3HhmfJxIdTJyZR6r+kqVgmbdg9nVXm95h28Za9oBCYuXwg+CJufKwKOP6g7l657xjmRVHjIj9+D11IwZnrxhtj0GAyMYVKNIFhFxb1I2rEiRPLJ8VFmMdk69cgrM3MUXDE9iKZ7PrM+YMs72uEVQuGsoA==\",\"pbkdf2_iterations\":5000,\"version\":4}","symbol_local":{"symbol":"$","code":"USD","symbolAppearsAfter":false,"name":"U.S. dollar","local":true,"conversion":0},"guid":"ed682dde-4d55-41ed-67ad-bcb8507ee973","payload_checksum":"8e3a536ef4d989e0a737f981112bcb919b4d1d0a301d6ccdb190217dcf3f396e","war_checksum":"705948bd199da68a","language":"en","symbol_btc":{"symbol":"BTC","code":"BTC","symbolAppearsAfter":true,"name":"Bitcoin","local":false,"conversion":100000000.00000000},"sync_pubkeys":false}

I'm surprised that the instructions above still works on wallets without associated email, that method is old BTW.
Anyways, your wallet.aes.json should be the payload part of that result.

Just snip the line starting from: {\"payload\":\"Wp3y...
to: ...GsoA==\",\"pbkdf2_iterations\":5000,\"version\":4}
Then save it as "wallet.aes.json", make sure to display "common file name extensions" since your OS may be keeping that ".txt" extension if you've used a text file to save it.

I can also confirm that my legacy wallet id was giving "invalid token" error due to lack of associated e-mail. Same as above I provided customer support with the wallet ID, approximate creation date and the new e-mail address and my wallet is now accessible. For what it's worth my identity was also "verified"