Getting a "Invalid token" error on old blockchain.info wallets

So, about a year ago, I managed to fix this messed-up WIF key but then kinda slacked off and didn’t download all the wallet.aes.json files in time for the wallet ID linked to my email. I had no clue about the password or seeds since I totally misplaced the fireproof bag that had everything in it. Fast forward, I recently stumbled upon some really old school paper wallets from blockchain.info from 2013-2015, hidden away in that fireproof bag. The wallet ID was in this format: ??-?-?-?-??? and I also found the password along with a 19-word recovery seed that’s not the usual blockchain.info style. A few of these paper wallets had what I thought was a backup, with a bunch of QR codes but turns out they don’t lead to a WIF. Back in the day, you could print a sheet with all the P2PKH and WIF keys, but this wasn’t that. After scanning the QR codes one after another and stitching them together, it looks like it’s some sort of encrypted JSON backup. I spotted a pbkdf2_iterations version 2 payload, which is a super long string I’ve dumped from the JavaScript console back in 2016 or so, before download-blockchain-wallet.py was even a thing. I was trying to pull backup from the client-side JS memory because I had this hunch that blockchain.info was doing some JavaScript magic with memory, and all the wallet info was somewhere in that session data. I always knew I’d eventually find that lost HODL bag (now it's more like diamond hands), and back in 2022, I even tried to download the wallet.aes.json for the one I thought had the most coins after digging through my emails.

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 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, 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 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

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 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 And Verify it: 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 (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?