[DO NOT DM] Requesting help regarding my old account

[nc50lc]

-snip-

How can I find my wallet ID?

I do not have any emails from Blockchain.info from back then.

It's the seemingly random numbers with dashes that you use to login.
But If you're using your email address instead; login your account first, then you can find it in your wallet's settings under 'General' settings tab.
(read the red warning note below it for your privacy)

[lightsun47]

-snip-

How can I find my wallet ID?

I do not have any emails from Blockchain.info from back then.

It's the seemingly random numbers with dashes that you use to login.
But If you're using your email address instead; login your account first, then you can find it in your wallet's settings under 'General' settings tab.
(read the red warning note below it for your privacy)

Ok. I was able to extract the correct payload file (I believe).

Now, I have two problems when I use two different commands:

1.

Code:

python btcrecover.py --wallet ./btcrecover/test/test-wallets/blockchain-github-v1-1 --dump-privkeys blockchain-github-v1-1_main_privkeys.txt --correct-wallet-password mypassword

Starting btcrecover 1.13.0-Cryptoguide on Python 3.13.5 64-bit, 21-bit unicodes, 64-bit ints

Dumping Wallet File or Keys...

Wallet successfully dumped...


I cannot find any file in this case.



2.

Code:

python btcrecover.py --wallet wallet.aes.json --dump-wallet wallet_decrypted.txt --correct-wallet-password MYCORRECTPASSWORDHERE

Starting btcrecover 1.13.0-Cryptoguide on Python 3.13.5 64-bit, 21-bit unicodes, 64-bit ints

Dumping Wallet File or Keys...

Unable to decrypt wallet, likely due to incorrect password..


I am using the correct password but I am getting this error.




I tried to extract the password using:

Code:

python seedrecover.py --wallet-type blockchainpasswordv3 --mnemonic "phrases here" --mnemonic-length 17

command but I am getting a weird coded password as a recovered password - half correct and half some coded words with it.

When I try to use that recovered password to dump the keys, it says password is invalid.




It feels like I am back to square one despite being so close to the end now!

Please help.

Thanks again.

[nc50lc]

1.

Code:

python btcrecover.py --wallet ./btcrecover/test/test-wallets/blockchain-github-v1-1 --dump-privkeys blockchain-github-v1-1_main_privkeys.txt --correct-wallet-password mypassword

Wallet successfully dumped...

I cannot find any file in this case.

Since the indicated value of --dump-privkeys arg isn't an absolute nor relative path,
If not in your BTCRecover nor python install directory, it should be in your working directory named "blockchain-github-v1-1_main_privkeys.txt".
About "working directory", it's the directory displayed in your command line before the ">" sign.

Or alternatively, specify the absolute path of where you want to save the dump file.
e.g.: --dump-privkeys D:/blockchain-github-v1-1_main_privkeys.txt to save it in D: drive's root.

Unable to decrypt wallet, likely due to incorrect password..

I am using the correct password but I am getting this error.

If it's not the password, it may be the payload that you saved as wallet.aes.json file.
The format should look like the test "blockchain-github" wallets in ".\btcrecover\test\test-wallets" (open as text), older versions are different than the latest so check them all if your payload isn't formatted correctly.

It feels like I am back to square one despite being so close to the end now!

Fingers Crossed.
But like I mentioned, his suggestion to dump the wallet's private keys isn't the direct solution to this but an option in case it's the client's issue.

[lightsun47]

1.

Code:

python btcrecover.py --wallet ./btcrecover/test/test-wallets/blockchain-github-v1-1 --dump-privkeys blockchain-github-v1-1_main_privkeys.txt --correct-wallet-password mypassword

Wallet successfully dumped...

I cannot find any file in this case.

Since the indicated value of --dump-privkeys arg isn't an absolute nor relative path,
If not in your BTCRecover nor python install directory, it should be in your working directory named "blockchain-github-v1-1_main_privkeys.txt".
About "working directory", it's the directory displayed in your command line before the ">" sign.

Or alternatively, specify the absolute path of where you want to save the dump file.
e.g.: --dump-privkeys D:/blockchain-github-v1-1_main_privkeys.txt to save it in D: drive's root.

Unable to decrypt wallet, likely due to incorrect password..

I am using the correct password but I am getting this error.

If it's not the password, it may be the payload that you saved as wallet.aes.json file.
The format should look like the test "blockchain-github" wallets in ".\btcrecover\test\test-wallets" (open as text), older versions are different than the latest so check them all if your payload isn't formatted correctly.

It feels like I am back to square one despite being so close to the end now!

Fingers Crossed.
But like I mentioned, his suggestion to dump the wallet's private keys isn't the direct solution to this but an option in case it's the client's issue.

Thanks.

I was actually able to located the dump and private keys file.

Now, upon importing in Electrum, I see there were two transactions made back in 2022.

One was 0.04 BTC in and out quickly and another one for 1.1 BTC in and out quickly.

I don't understand why someone would do this because my account was dormant ever since 2014.

Anyways, I have a suspicion that the private keys file actually don't belong to me and it was installed when I installed Btcrecover, so I am seeing someone else's transactions?

I still believe my .json file is password encrypted which I have yet to decipher.

Your thoughts on what should I do to decipher and try again?

Thanks again.

[nc50lc]

-snip-

Anyways, I have a suspicion that the private keys file actually don't belong to me and it was installed when I installed Btcrecover, so I am seeing someone else's transactions?

Do you mean the private keys in the dump file in your first command?

You should've expected it since you had pointed a test wallet file in that command's --wallet arg's value, the ones pre-included in BTCRecover. (./btcrecover/test/test-wallets/blockchain-github-v1-1)
I though you were testing its --dump-privkeys functionality when you used that specific command.

[lightsun47]

-snip-

Anyways, I have a suspicion that the private keys file actually don't belong to me and it was installed when I installed Btcrecover, so I am seeing someone else's transactions?

Do you mean the private keys in the dump file in your first command?

You should've expected it since you had pointed a test wallet file in that command's --wallet arg's value, the ones pre-included in BTCRecover. (./btcrecover/test/test-wallets/blockchain-github-v1-1)
I though you were testing its --dump-privkeys functionality when you used that specific command.

You are correct.

I was actually dumping the test wallet private keys! They aren't mine like I had raised suspicions.

Ok.

Now that it's clear, how can I dump my private keys?

I use the --dump-privkeys command, but I cannot specify where the file is located?

Please help with the actual command as to what to type.

And someone should make a program in which you just have to drag and drop files and get dump results instantly instead of typing in DOS like it's still the 80's! It's really annoying.

Thanks again.

[nc50lc]

Ok.

Now that it's clear, how can I dump my private keys?

Just keep it simple by using a dedicated directory for wallets and dump files.

For example (your previous replies suggest you're using Windows):
Create a "recovery" folder in your "D:" Drive, that'll make its absolute path; "D:/recovery/".
Place your wallet.aes.json file there.

Then, considering Python and BTCRecover are properly set-up, use your previous commands but point the args' values to the absolute path of the directory above.
E.g. (based from your command above):

Code:

python btcrecover.py --wallet "D:/recovery/wallet.aes.json" --dump-wallet "D:/recovery/wallet_decrypted.txt" --correct-wallet-password "MYCORRECTPASSWORDHERE"

Include the quotation marks in the example if any of the values have whitespace or special characters.

The problem is the result of your previous attempt in #2.
The command seem to have worked but something cased that "possibly wrong password" error.

And someone should make a program in which you just have to drag and drop files and get dump results instantly instead of typing in DOS like it's still the 80's! It's really annoying.

They (Blockchain(dot)com) have their own wallet decryption tool with GUI that can dump wallet.aes.json files but the private keys are dumped as bare base58, not WIF.
It'll be quite troublesome to convert each to WIF.

Plus you already setup the previously suggested tool by other members, BTCRecover, and it's good enough.

[lightsun47]

Code:

python btcrecover.py --wallet "D:/recovery/wallet.aes.json" --dump-wallet "D:/recovery/wallet_decrypted.txt" --correct-wallet-password "MYCORRECTPASSWORDHERE"

I am getting this error:

FileNotFoundError: [Errno 2] No such file or directory: 'C:/XXX/recovery/wallet.aes.json'

I have made a new directory and pasted the .json file there, but getting this error.

P. S. I am starting to think my .json file is invalid/incorrect because it has a lot of other characters than one shown in this video:

https://www.youtube.com/watch?v=f63FpoTKwSw&list=PL7rfJxwogDzmd1IanPrmlTg3ewAIq-BZJ&index=12

Not sure if it has to be exactly the same as shown in the video (apart from the content inside of course).

[nc50lc]

P. S. I am starting to think my .json file is invalid/incorrect because it has a lot of other characters than one shown in this video:

You would get a different error if it's caused by an invalid wallet.aes.json's payload/format.
We'll see if you've copied the wrong response (payload) after fixing the current issue with the pathing error.

FileNotFoundError: [Errno 2] No such file or directory: 'C:/XXX/recovery/wallet.aes.json'

I have made a new directory and pasted the .json file there, but getting this error.

If you're positive that the path is correct and existing, the only Windows thing that may have caused this is its default hidden "common file extension" option.

If you initially created a text file to make that wallet file, its actual name may be "wallet.aes.json.txt" with hidden ".txt" extension.
So, try to enable the settings in your Windows Explorer in "View->Show->File Name Extensions", then rename the wallet file correctly.

[Cricktor]

OP, does your Windows Explorer hide extensions from files? If yes, I'd recommend to turn if off temporarily or better permanently, it's in my opinion a totally silly Windows crap option which is on by default!

As nc50lc points out, BTCrecover doesn't find your 'C:/XXX/recovery/wallet.aes.json', either because the path to the file doesn't exist or the silly Windows hiding file extensions doesn't show you that your 'wallet.aes.json' might actually be something like 'wallet.aes.json.txt', particularly when you created the file with a Windows text editor app.

[lightsun47]

P. S. I am starting to think my .json file is invalid/incorrect because it has a lot of other characters than one shown in this video:

You would get a different error if it's caused by an invalid wallet.aes.json's payload/format.
We'll see if you've copied the wrong response (payload) after fixing the current issue with the pathing error.

FileNotFoundError: [Errno 2] No such file or directory: 'C:/XXX/recovery/wallet.aes.json'

I have made a new directory and pasted the .json file there, but getting this error.

If you're positive that the path is correct and existing, the only Windows thing that may have caused this is its default hidden "common file extension" option.

If you initially created a text file to make that wallet file, its actual name may be "wallet.aes.json.txt" with hidden ".txt" extension.
So, try to enable the settings in your Windows Explorer in "View->Show->File Name Extensions", then rename the wallet file correctly.

Ok let me tell you what I did.

I used btc_address_dump "INSERT MNEMONIC PHRASES HERE" command.

This dumped private keys (Hex, WIF), public key and legacy address.

Upon checking the address in public explorer, I found there are no transactions at all?!

I mean, if there's no activity at all (and most importantly, NO BALANCE!) then what's the point of recovering this wallet in the first place?

Afaik, there's supposed to be some balance from back "then".

If it's safe, can I share my public address here, so you can have a look yourselves?

Thanks. Let me know.

[nc50lc]

I used btc_address_dump "INSERT MNEMONIC PHRASES HERE" command.

You didn't specified which "btc_address_dump" tool that you've used, was that from 10gic's GitHub repo?

Because you must have an incorrect derived address since that tool doesn't check for the mnemonic phrase's checksum and just assumes that it's valid.
Then, your 17-words backup phrase isn't a BIP39 seed phrase that can be used to derive your private keys and addresses.
That is for the recovery of your account credentials like what you did initially (when you got your password from it).
When you entered it to that tool, it forcefully used BIP39's algorithm to derive the displayed address, but that isn't what Blockchain(dot)com used to derive your keys.

If you used the new 12-words seed phrase in your security settings, that should be BIP39 standard.
However, the tool only derived one address while Blockchain uses more than just one.
And also, the one you're looking for could be from an address derived from the uncompressed public key pair of one of your prvKey.
And lastly and more importantly, the private keys from 2014 version of Blockchain's online wallet might not belong to that HD seed since it's not yet implemented there at that time.
("Blockchain/My-Wallet-V3" a.k.a "My-Wallet-HD" was on Beta during Q4 2014, ref: push hdwallet branch)

On the other hand, dumping the private keys from your wallet.aes.json file will ensure that every private keys in the dump file are the ones contained in your wallet.

[lightsun47]

On the other hand, dumping the private keys from your wallet.aes.json file will ensure that every private keys in the dump file are the ones contained in your wallet.

Ok. I tried to do this, but it says I have incorrect password.

1. When I decrypted the password earlier, it had some non recognizable characters in it. So, I wasn't able to use it by copy pasting it.

2. Let's assume that password is really correct. How can I use it?

Also, can you please paste the command to decrypt the .json file now? (It looks like adding the .txt in the command worked as you had suggested earlier.)

Thanks.

[nc50lc]

On the other hand, dumping the private keys from your wallet.aes.json file will ensure that every private keys in the dump file are the ones contained in your wallet.

Ok. I tried to do this, but it says I have incorrect password.

Question, can you successfully login to their wallet's website or app?

Because if so, just use the same password that you're using to login since it's the same required password to decrypt the encrypted payload that you copied to create a wallet file.

Also, can you please paste the command to decrypt the .json file now? (It looks like adding the .txt in the command worked as you had suggested earlier.)

My suggestion was to remove the ".txt" from the file leaving its actual name "wallet.aes.json" and use the command in the instructions.

[lightsun47]

On the other hand, dumping the private keys from your wallet.aes.json file will ensure that every private keys in the dump file are the ones contained in your wallet.

Ok. I tried to do this, but it says I have incorrect password.

Question, can you successfully login to their wallet's website or app?

Because if so, just use the same password that you're using to login since it's the same required password to decrypt the encrypted payload that you copied to create a wallet file.

Also, can you please paste the command to decrypt the .json file now? (It looks like adding the .txt in the command worked as you had suggested earlier.)

My suggestion was to remove the ".txt" from the file leaving its actual name "wallet.aes.json" and use the command in the instructions.

1. Yes I can successfully login to the wallet's website. However, it shows the password is incorrect.

2. Ok. I have now renamed into .json file (which I had done previously anyways). I will report back.

Sorry for the delay because I am feeling this is going nowhere...

Edit: I am trying to recover using Import Wallet file on Blockchain.com, but it still says incorrect password.

[nc50lc]

Sorry for the delay because I am feeling this is going nowhere...

Yes, I've mentioned in post#4 that the deleted AI-generated reply by a certain member which included that suggestion isn't the solution to the issue.
It just posted unrelated Blockchain(dot)com recovery options based from his unclear prompt.

You're just doing that for confirmation that the wallet.aes.json doesn't actually contain the right private key(s).
If you're having trouble with the instructions, it's best to pause it for now.

[lightsun47]

Sorry for the delay because I am feeling this is going nowhere...

Yes, I've mentioned in post#4 that the deleted AI-generated reply by a certain member which included that suggestion isn't the solution to the issue.
It just posted unrelated Blockchain(dot)com recovery options based from his unclear prompt.

You're just doing that for confirmation that the wallet.aes.json doesn't actually contain the right private key(s).
If you're having trouble with the instructions, it's best to pause it for now.

Thanks. I was already taking a break if you noticed I hadn't posted anything since a few days. But anyways, this needs to be done as well.

EDIT: Can running Bitcoin core show anything relevant, i.e. can it show any transactions, balance, etc. of my wallet? Thanks.

[nc50lc]

-snip-
EDIT: Can running Bitcoin core show anything relevant, i.e. can it show any transactions, balance, etc. of my wallet? Thanks.

Nothing in particular, other clients can already check every output types that Blockchain(dot)com used within its lifetime.

The difference is just you'll be relying on your own copy of the Bitcoin blockchain if you used Bitcoin Core to rescan.
But even with you own copy of the blockchain, you still need the correct public key(s) or at least address(es) to find which is which.

Note: "Blockchain" online wallet and the Bitcoin "blockchain" are different things.
I normally use capital letter on the former to identify that it's the company that offers an online wallet/exchange service.