I am selling my wallet—I’m offering a reward for cracking the password.

[Stalker22]

These links are a scam; they do not have access to my wallet. At best, they only have the address's extended public key.

Yes, those links ARE a scam.  And so is yours.  The only difference between those wallet files and yours is that they are selling for 0.00105000 BTC, while yours is 0.18900000 BTC!  But both are fake.

As for the wallet file access, here is a screenshot of the wallet uploaded nine months ago:



And this is yours:

Interestingly, both wallets share the exact same labels for incoming transactions and addresses.  How do you explain this?

Besides, you forgot what Dave replied to your request:

Dave Bitcoin<walletrecoveryservices@gmail.com>

Sorry, I cannot help you with this for two reasons:

1) I have been sent this same wallet a few years ago, with very different password ideas
2) It is not possible to find a random password of that length with Arabic letters

Regards,
Dave

[Chris_Farli]

No, the password looks like this: a name and an Arabic word. It seems to me that the Arabic ending is being perceived incorrectly. I haven't run any tests yet—I'll need to give that a try; it's a good lead to help get things moving. My Bitcoin client version 28.1.0

This isn't the right place to discuss it, but anyway...

I would test the following, you can do it with Testnet coins or no coins at all:
Take the Bitcoin client version from the time "your" wallet has been created (first funding transaction should be an indicator). Create a wallet with an wallet encryption password similar to what you said. This time write down the encryption password properly so that you can reproduce it.

Now open, migrate if necessary, this test wallet in your Bitcoin Core 28.1.0. Does the encryption password unlock the test wallet properly?

I've no suspicion that this could fail, but if it does for whatever reasons, character encoding mismatch issues from old to newer Bitcoin client version, then your prior attempt were destined to never bring you to a solution.

Do you have copies of your wallet that haven't been touched by newer Bitcoin client versions? In a recovery case I would always make sure to never destroy original data, always work on copies of copies, so that you can always restart from a known and defined state.


It's a shoot into the blue, but those are things that I would verify first.

...

I'm not much of a friend of those "lost wallet sales" because I believe that the majority, if not all of them, of those wallets are faked and rigged. And there's mostly no way to avoid being screwed.

Well, there's always something to learn from a recovery case...

To be honest, I don't remember exactly which version was used to create the wallet, but I still have the original Maxtor hard drive (80 GB, SATA 3.0) and seven copies of the wallet itself. As for version verification, there were no issues with the password (including the version with the Arabic suffix)—everything works perfectly; the only error was related to the `peers.dat` file in certain versions, which prevented them from launching.

I have versions 10 and 11.2 installed in different folders on my drive. Version 28 is the latest; it accepted the verification file and password without errors but returned an "incorrect password" result, so the search must continue. At this point, I am about 70–80% confident in the password; the only sticking point is its ending.

I’m also unclear on the point regarding character encodings when adding a password list— File encoding:
SBCS (ANSI/OEM), OUTF-8, OUTF-16LE (Unicode) Does the system have a specific text encoding? The first thing that comes to mind is converting this list into each of the following formats: SBCS (ANSI/OEM), UTF-8, and UTF-16LE (Unicode).

These links are a scam; they do not have access to my wallet. At best, they only have the address's extended public key.

Yes, those links ARE a scam.  And so is yours.  The only difference between those wallet files and yours is that they are selling for 0.00105000 BTC, while yours is 0.18900000 BTC!  But both are fake.

As for the wallet file access, here is a screenshot of the wallet uploaded nine months ago:

https://i.ibb.co/jvB23GsK/Screenshot-11.png

And this is yours:

https://i.ibb.co/6c3nx6by/Screenshot-3.png

Interestingly, both wallets share the exact same labels for incoming transactions and addresses.  How do you explain this?

Besides, you forgot what Dave replied to your request:

Dave Bitcoin<walletrecoveryservices@gmail.com>

Sorry, I cannot help you with this for two reasons:

1) I have been sent this same wallet a few years ago, with very different password ideas
2) It is not possible to find a random password of that length with Arabic letters

Regards,
Dave

I think these are your links; you’ve been promoting them very actively. I’ll be able to prove it once I find and restore the end of the password and sign the message.

In case you hadn't noticed, we are discussing various options, yet you aren't participating in the discussion at all—you're just spouting nonsense. I have no intention of clicking the links you post; you seem suspicious. You’re the one who messaged me asking for that file, right? https://i.ibb.co/67f2hJ86/Screenshot-14.png

@Stalker22 - Thank you for sharing your opinion—that is your right. I only hope that you won't behave rudely while doing so.

Be that as it may, giving your wallet file to random strangers to "crack a password" is the peak of sheer stupidity.

However, unless OP can somehow prove that he is the original owner, I dont believe him.  Whether he is the actual scammer or just a useful idiot taking his turn to sell a fake story doesnt really matter.  Time wont tell anything we dont already know:

That exact wallet has been used as scam bait for years by multiple people.  These types of scams were popular a decade ago, and frankly, anyone who still falls for these tired, recycled fairy tales today is an absolute fool who deserves to lose their money.
~snip~

I agree - the only logical explanation is that people resort to drastic measures when they have no other choice. The evidence suggests that the OP may not be the original owner, and either way, I don't think anyone will buy that wallet after even Dave wrote that it's impossible to find the password for it.

What do you agree with regarding the time I had an RTX 470 4GB card and a purchased brute-forcing program 2018? https://i.ibb.co/p6pP88JX/Screenshot-39.png You’re the ones who aren’t real; you just make me angry with your insults.

These links are a scam; they do not have access to my wallet. At best, they only have the address's extended public key.

Yes, those links ARE a scam.  And so is yours.  The only difference between those wallet files and yours is that they are selling for 0.00105000 BTC, while yours is 0.18900000 BTC!  But both are fake.

As for the wallet file access, here is a screenshot of the wallet uploaded nine months ago:

https://i.ibb.co/jvB23GsK/Screenshot-11.png

And this is yours:

https://i.ibb.co/6c3nx6by/Screenshot-3.png

Interestingly, both wallets share the exact same labels for incoming transactions and addresses.  How do you explain this?

Besides, you forgot what Dave replied to your request:

Dave Bitcoin<walletrecoveryservices@gmail.com>

Sorry, I cannot help you with this for two reasons:

1) I have been sent this same wallet a few years ago, with very different password ideas
2) It is not possible to find a random password of that length with Arabic letters

Regards,
Dave

I didn't quite understand what you meant regarding tags; at the time, I wanted to figure out how transactions worked and discovered that using real coins wasn't necessary—there were "faucets" that dispensed test coins. Address tags are a personal matter; I am under no obligation to explain to you what significance they held for me... https://i.ibb.co/2YtWmV1j/Screenshot-40.png

I no longer want to prove anything to bullies; now I only interact with reasonable people.

[Cricktor]

OP, don't post consecutive posts within less than 24h time difference, this violates forum rule #32. I highly recommend to read and understand the Unofficial list of (official) Bitcointalk.org rules, guidelines, FAQ.
Post edit: reported posts have been merged by a moderator.

I can't speak for Dave but I'm pretty sure he mainly refused to invest anything into this recovery case because it's a sold wallet made public and brought to him by different people with, as Stalker22 repeated, very different password suggestions. If I were to put his shoes on, I'd refuse to work on this, too.

As for version verification, there were no issues with the password (including the version with the Arabic suffix)—everything works perfectly; the only error was related to the `peers.dat` file in certain versions, which prevented them from launching.

To my knowledge you can ignore issues with the peers.dat file. You could delete it and Bitcoin Core would create a new one. This file is not important for your case.

OP, regarding help to recover this with some tools yourself, open a new topic for it in Bitcoin Technical Support board. Some of the more knowledgeable users there likely don't frequent this section of the forum. It's of course possible that they aren't much interested to help you because they might not believe you're the real owner of this wallet and sold wallet files are mostly, if not all, faked.

Regarding the potential character encoding issues, I can't give much advise, I don't know your tool. My first idea would be to tackle your problem with tools like btcrecover or more likely with hashcat. The latter can operate with GPU acceleration to my knowledge. I don't know if your tool can find a valid solution. This is something you would need to test with a model case, where you know the solution and your tool has to find it. If it can't, your tool is crap.

[Chris_Farli]

Regarding the potential character encoding issues, I can't give much advise, I don't know your tool. My first idea would be to tackle your problem with tools like btcrecover or more likely with hashcat. The latter can operate with GPU acceleration to my knowledge. I don't know if your tool can find a valid solution. This is something you would need to test with a model case, where you know the solution and your tool has to find it. If it can't, your tool is crap.

I ran a test by specifying the characters needed to unlock the test password, and my program—Bitcoin Password—successfully found it. The btcrecover program also handles the task perfectly, provided the password is in the list.