Quote from: ABCbits on Today at 09:18:03 AM

Quote from: jstyler on February 21, 2025, 11:48:11 AM

i'm really sorry to hear about your situation, it's a nightmare to deal with. bitcoin core's lack of straightforward private key access is indeed a frustrating flaw. have you considered reaching out to some of the bitcoin core devs or security experts for guidance on wallet.dat and private key recovery? they might be able to provide some valuable insights or point you in the right direction.

Please don't suggest to contact one of Bitcoin Core developer/contributor, they're not tech support. It's been stated many times, here are few examples
https://github.com/bitcoin/bitcoin/issues/9153#issuecomment-260216788
https://github.com/bitcoin/bitcoin/issues/31832#issuecomment-2647314964

Quote from: SpaceMarine770 on Today at 03:26:55 AM

I'm going to look into running with GPU to see if that increases speed. If my speed was faster by some orders of magnitude, it would be much more feasible. Right now it's testing approximately 3,000 password combos every minute. I'm pretty sure that number can be brought up to the tens of thousands per minute once I optimize efficiency.

Even with one mid-end GPU, BTCRecover can try hundred thousand combo per minute. Looking at https://btcrecover.readthedocs.io/en/latest/GPU_Acceleration/, single Nvidia GTX 1660 Ti can perform 6750 password/second or 405 thousand per minute.

I've been working on setting up the GPU acceleration all night and finally got it working. Now I'm at approximately 10,000 passwords per minute which is already alot better.

It says that if i optimize the --global-ws and --local-ws parameters that it's possible to get a 10X improvement, so God willing I can get it upwards of 100,000 passwords a minute.

Also, this can run multiple servers / computers / GPUs in parallel, so I'm gonna start working on that. Then I can scale up much more.

I really wanna get it strong in case I have to start running all the typo parameters. I'm truly baffled it hasn't cracked it yet, so it might be a typo situation