Hey everyone,
So, I’m dealing with a bit of a situation for one of my clients. He’s got 11 words from his mnemonic seed, but he doesn’t remember the order, and there’s one word missing. He thought it was "casual," but apparently it’s not. I’m looking for the right command line to run btcrecover since he’s missing one word and the other 11 are all mixed up. I’ve got plenty of GPUs can we actually recover the wallet? What’s the exact command I should use in seedrecover.py to tackle this, along with enabling the GPUs with their IDs?
I’ve got multiple GPUs but it seems like when I use gpuid 0 1 2 3 4, seedrecover is only picking up one GPU. Any suggestions? I’d really appreciate some help on this, and I’m looking for a specific command line to get seedrecover working to fix this issue.
The wallet address is bc1qlmal276kkvrkn36m33xvlylfgqspcdkp0l2zsz.
Honestly, I’m counting on your expertise here, and I promise to reward anyone who helps out. I’ve been grinding on this since December and I even posted about it before, but after trying so many times with the given words, we still can’t get it back. The client is super stressed about losing access to his wallet. If we can make it work, he’ll definitely show his appreciation.
Thanks a lot!
In your December 2023 thread, there was no unknown word and the issue was just the arrangement.
I'm doubtful that there's just additional 1 missing word at play here.
Anyways, just do the same as the previous token file but instead of the line "casual", replace it with the whole BIP39 word list without break lines (enter).
So the whole 2048 words are only separated by spaces occupying only one line.
Example:
As for the GPU, I can't add anything aside from what's already mentioned in the other topic.
I don't know how possible you can find the missing word, if only you're sure that it is only one word left then you can use the btcrecovery tool (The FinderOuter, a bitcoin recovery tool)[1] /[2] you could follow the instructions and but you only have to put a little energy in finding it.
Or you can put your client in play with the bip39 word list[2] to take a proper look if he or she could remember the exact/or closer word by going through the wordlist.
[1] https://bitcointalk.org/index.php?topic=5214021.0
[2] https://github.com/3rdIteration/btcrecover
[3] https://github.com/bitcoin/bips/blob/master/bip-0039/bip-0039-wordlists.md
Something smells fishy here. In 2021, you were missing 29 characters of a 488BTC private key. A few months later, you were offering your services to "recover easily" Bitcoins. Last December, you had "a friend" who can't access his 2500BTC bud didn't know how to do this trivial thing with btcrecover.
If any of this is real, your client/friend should be talking to an expert instead of you.
Looking at https://github.com/3rdIteration/btcrecover/blob/master/btcrecover/btcrpass.py which process CLI argument, btcrecover doesn't even accept gpuid argument. I think you'll need --list-gpus to see name of all your GPUs and then use multiple --gpu-names instead. See @nc50lc response below for correct argument.
Meanwhile we must trust you to share the reward, where we can't even know you actually solve the problem and got paid by your client.
But it's for btcrecover while OP is utilizing "seedrecover.py" script which doesn't use btcrpass.py but btcrseed.py.
In seedrecover, as of btcrecover v1.12, his options to use GPU is under "OpenCL acceleration" when prompted for commands via seedrecover.py -h.
Here are the available args for seedrecover gpu acceleration: github.com/3rdIteration/btcrecover/blob/master/btcrecover/btcrseed.py#L3204-L3210
The developer has a note in the official documentation page that it's currently buggy though.
My test with "Positional Anchors" for the first 6 words (to speed-up testing) are successful.
Just make sure that those 2048 words are listed in the same line so it will only try one word in that line in each combination
Because otherwise, each line wont be treated as "Mutual Exclusion" and will be tried together with the other words.
(refer to the old/new BTCRecover's token file documentation for the terms)