In your case, the fact that you saved the original Wallet.aes.json (lucky you!) means that you will be able to get to your private key, but only using BTCrecover, and restore access to the wallet using the private key when you extract it from wallet.aes.json in WIF format.
What is WIF?
Wallet Import Format (WIF) is a standardized method for displaying Bitcoin private keys using the Base58Check encoding scheme. WIF format was standardized in order to allow all Bitcoin wallets to import and export private keys.
https://river.com/learn/terms/w/wallet-import-format-wif/You can use WIF to import your private keys into a new wallet. You can also find more information here:
https://en.bitcoin.it/wiki/Wallet_import_formatI believe he is referring to Bluewallet's GUI. Bluewallet supports multiple wallet formats. The Legacy Bitcoin wallet is presented with a green card color in the user interface.
https://bluewallet.io/bitcoin-wallet/Thank you, this is all correct!
About WIF, correct and excellent link.
About BlueWallet,
I’ll add that if in BlueWallet the card icon is:
Legacy (for one private key) (1.....) - green (as in your picture),
P2PKH (HD Legacy) (1...) - red,
P2SH (3 ....) - dark blue,
P2PKH/P2WSH (bc1q...) - blue.
This is exactly what I meant.
I'll be more than happy to do so. The community is helping me, so of course I want to help the community back. Mind if I clarify a few things?
....
What's going on here? Can you share more information?
This is indeed the tool I used to try and decrypt the wallet file:
https://github.com/blockchain/my-wallet-backup-decryption-toolThe link you gave redirects to here. As I said, the tool failed to decrypt the wallet.
I think this:
You now actually have two identical wallets in the Blockchain.com system (w2013 and w2021).
Both have the same email address to confirm login;
Both have the same ID in Blockchain.com's proprietary format:
12345678-90ab-cdef-1234-567890abcdef
w2021 with BIP39 encoding;
w2013 with its own and outdated encoding from Blockchain.info (BIP58?).
As a result, Blockchain.com simply cannot connect these 2 wallets. The w2013 address is not imported into w2021.
Contacting Blockchain.com support, in my opinion, is completely useless. This is a waste of both your time and your nerves. You will not be able to log into w2013 as usual with email confirmation. No matter how hard you try, you can always use this email address and wallet ID to log in only to w2021.
To solve the problem, the only option left is to extract the private key from your wallet.aes.json (2013) using
BTCrecover. This is probably the only real option to get to the 2013 wallet.
If anyone knows another option, please write your suggestions in this topic.
But only proposals tested in practice and specifically with the old wallets Blockchain.com/info.