Topic: Looking for a working configuration for a BTCrecover seedlist token file (Read 985 times)
March 01, 2024, 02:58:40 PM
https://imgur.com/3hwjYs7
I've been busy... More to come in another post.
https://bitcointalk.org/index.php?topic=5487238.new#new
March 20, 2023, 11:24:25 PM
1.1 billion again and it's hung up badly but started up again after an hour. Didn't get the process kill code yet but I got a feeling it's coming. Gonna let this play out and see what happens but I think this is it for me on this angle. Gonna have to get a better setup before trying again but at least I know I got the winning formula, just need the right tools to work it out.
One thing of note. While getting to 1.1 billion, it seems to have been running off the RAM because the 6 disk raid array were not blinking. Ever since the hangup, it's running much slower with less results and all 6 disks are blinking like it's Xmas.
Maybe I'll be back in a month or so. Thanx to everyone who contributed. For now I may be beaten, but I'm far from defeated.
One thing of note. While getting to 1.1 billion, it seems to have been running off the RAM because the 6 disk raid array were not blinking. Ever since the hangup, it's running much slower with less results and all 6 disks are blinking like it's Xmas.
Maybe I'll be back in a month or so. Thanx to everyone who contributed. For now I may be beaten, but I'm far from defeated.
I read your saga with interest. 2 years later, have you had any success?
December 24, 2022, 10:21:49 AM
How finish this story? I have the same issue.
July 25, 2021, 12:45:15 AM
1.1 billion again and it's hung up badly but started up again after an hour. Didn't get the process kill code yet but I got a feeling it's coming. Gonna let this play out and see what happens but I think this is it for me on this angle. Gonna have to get a better setup before trying again but at least I know I got the winning formula, just need the right tools to work it out.
One thing of note. While getting to 1.1 billion, it seems to have been running off the RAM because the 6 disk raid array were not blinking. Ever since the hangup, it's running much slower with less results and all 6 disks are blinking like it's Xmas.
Maybe I'll be back in a month or so. Thanx to everyone who contributed. For now I may be beaten, but I'm far from defeated.
One thing of note. While getting to 1.1 billion, it seems to have been running off the RAM because the 6 disk raid array were not blinking. Ever since the hangup, it's running much slower with less results and all 6 disks are blinking like it's Xmas.
Maybe I'll be back in a month or so. Thanx to everyone who contributed. For now I may be beaten, but I'm far from defeated.
July 24, 2021, 09:00:02 PM
So I am at 700 million at the 6 hour mark. At current pace, If I make 1.4 billion by the 12 hour mark, I will have passed the previous hurdle. I chose to run against 1 address instead of 10 and I saw a 2x jump in speed. Instead of the 22 k/ps I'm running at 38-32 k/ps. I will know more by the time I have my milk stout and cookies.
July 24, 2021, 03:00:14 PM
So after reworking the token file I am now working with this arrangement -
^1^lockedword
^2^lockedword
^3^floatingknownword ^4^floatingknownword
^7^lockedword
^8^lockedword
^9^lockedword
^10^lockedword
^11^lockedword
^12^lockedword
and then 3 lines of the entire BIP39 wordlist
Getting 2.5 million results a minute. I may need to get a better computer with GPU acceleration if this project is a lost cause on the current rig I got. Looking at running this on an Asus g17 Advantage Edition when I can get it and fully upgrade the 32GB of ram
^1^lockedword
^2^lockedword
^3^floatingknownword ^4^floatingknownword
^7^lockedword
^8^lockedword
^9^lockedword
^10^lockedword
^11^lockedword
^12^lockedword
and then 3 lines of the entire BIP39 wordlist
Getting 2.5 million results a minute. I may need to get a better computer with GPU acceleration if this project is a lost cause on the current rig I got. Looking at running this on an Asus g17 Advantage Edition when I can get it and fully upgrade the 32GB of ram
July 24, 2021, 02:36:16 AM
So I am back at it, this time with another approach. I installed the Ubuntu 20.04 SERVER ISO (Had to install a desktop interface. Loads of fun with that one.) in the hopes of eliminating the kill process issue.
Gonna try the same thing as before with my argument and my tokenlist. If anyone has input, suggestions or well wishes, I could use all 3 right now.
My morale is flagging and Guinness can only get me so far.
Gonna try the same thing as before with my argument and my tokenlist. If anyone has input, suggestions or well wishes, I could use all 3 right now.
My morale is flagging and Guinness can only get me so far.
June 22, 2021, 02:04:37 PM
When I was running BTCrecover using the "best guess" option, I was also using other specifically directed arguments, such as derivation paths, wallet types, amount of typos etc.
Maybe the current working argument using the token file is having a conflict. Without setting wallet type and derivation paths, it will give me the option to chose. I select bitcoin and it will search for all 3 BTC derivation types by default.
Whatever the difference is, I gotta determine what made the "best guess" work so fluidly and what is making it go splat with the token file at the exact same spot after some lagging and stuttering.
Maybe the current working argument using the token file is having a conflict. Without setting wallet type and derivation paths, it will give me the option to chose. I select bitcoin and it will search for all 3 BTC derivation types by default.
Whatever the difference is, I gotta determine what made the "best guess" work so fluidly and what is making it go splat with the token file at the exact same spot after some lagging and stuttering.
June 22, 2021, 03:40:11 AM
It's not very important, but you might want to find out why exactly btcrecover process was killed. Try this guide https://askubuntu.com/a/709366.
"Killed [12345]" message can happen for a variety of reasons and aren't limited to out-of-memory situations. BTCrecover makes use of multiple CPU threads, so it's possible that if one of them crashed, the entire program terminates and the shell displays this message. If btcrecover made any log files, it's best to check them to see if this is the true reason for the crash or if it's something else.
June 21, 2021, 12:08:44 PM
I don't get how it could run out of memory. I was working with over 9 billion results and counting over a course of nearly 3 days on the first shakedown pass. This latest pass didnt even get to 2 billion in 12 hours and it was killed. I got 44 gigs of RAM on this thing, how could it run out of memory?
I ran it again starting last night, and it crashed in the exact same place and same time, just over 1 billion results 15 hours in. "killed214264"
Unfortunately btcrecover doesn't have feature to allocate memory based on available RAM. Have you tried using these parameter to prevent OOM?
Code:
--no-dupchecks --no-eta flags
Yes, I had both of those in my most current working argument listed back several posts ago
Code:
python3 seedrecover.py --no-dupchecks --mnemonic-length 12 --language EN --dsw --no-eta --tokenlist ./seedtoken.txt
June 20, 2021, 05:36:10 PM
I ran it again starting last night, and it crashed in the exact same place and same time, just over 1 billion results 15 hours in. "killed214264"
In the shakedown runs using the "best guess" option amassing over 9 billion results with not even so much as a sniffle, In this run I noticed some stuttering, pausing and lagging but it would resume after a minute or so. The only difference in this instance from the other runs is I'm running off the token file.
At least I got the token file working, but still... This sucks
In the shakedown runs using the "best guess" option amassing over 9 billion results with not even so much as a sniffle, In this run I noticed some stuttering, pausing and lagging but it would resume after a minute or so. The only difference in this instance from the other runs is I'm running off the token file.
At least I got the token file working, but still... This sucks
June 20, 2021, 11:31:00 AM
I don't get how it could run out of memory. I was working with over 9 billion results and counting over a course of nearly 3 days on the first shakedown pass. This latest pass didnt even get to 2 billion in 12 hours and it was killed. I got 44 gigs of RAM on this thing, how could it run out of memory?
June 20, 2021, 01:36:51 AM
Just when I thought things were going as smooth as they could be, the terminal process stopped and I got a "killed215704" reading.
WTF
WTF
June 19, 2021, 11:40:07 PM
So I'm happy I got the token file working but I'm mystified as to why it's going so damn slow. 13 hours in and I'm just about to crack my first billion.
Patience is definitely virtual and good things come to those who have high bitrate. Might be time for that Guinness, in a nice hot bath and a good Terry Pratchett book while I meditate on good things
Patience is definitely virtual and good things come to those who have high bitrate. Might be time for that Guinness, in a nice hot bath and a good Terry Pratchett book while I meditate on good things
June 19, 2021, 03:35:58 PM
So it's been 5 hours and for whatever reason it's seems to be parsing at 20.1 kp/s and only at 360 million results. At least it's working.
Even with 24 worker threads, 44 cores and 6 striped disks, I may need to get a 'bigger boat'.
Went from 170 million to 7.2 million an hour. Sacrificing speed for semblance and stability indeed
Even with 24 worker threads, 44 cores and 6 striped disks, I may need to get a 'bigger boat'.
Went from 170 million to 7.2 million an hour. Sacrificing speed for semblance and stability indeed
June 19, 2021, 10:37:19 AM
Firstly, you have a typo. It should be --mnemonic-length 12. Your dash is in the wrong location.
Secondly, you don't need the --typos 3 or --big typos 3 arguments when using a tokens file. Your tokens file should be configured in such a way that it contains all the possible combinations to try. You can use these I believe, but they will exponentially increase your search space.
Thirdly, and the reason you are getting the "seed not found" error, is because you are using --seedlist instead of --tokenlist. The seedlist command tries every line in the text file as an individual seed, whereas the tokenlist command treats each line as an individual word in a potential seed phrase.
Glad to have you with me this morning. The only silver lining to not being able to sleep. So I fixed the code. I free typed it and fatigue is my excuse for mistakes.
I believe Cryptoguide also said the typos would be redundant. Thank you for reminding me. Been 2 1/2 months and still trying to jumble everything together.
So the "token list" now looks like this
1^1^lockedword
2^2^lockedword
3^4^lockedword (switching between position three and four)
4^7^lockedword
5^8^lockedword
6^9^lockedword
7^10^lockedword
8^11^lockedword
9^12^lockedword
10 abandon ability etc
11 abandon ability etc
12 abandon ability etc
The argument now looks like
Code:
python3 seedrecover.py --no-dupchecks --mnemonic-length 12 --language EN --dsw --no-eta --tokenlist ./seedtoken.txt
I just hit enter and BEHOLD, it's running and counting!!! It's 5.30 in the morning, is it too early to celebrate this tiny victory with a bottle of Guinness...?
June 19, 2021, 09:48:11 AM
My current argument is
Code:
python3 seedrecover.py --no dupchecks --mnemonic length-12 --language EN --dsw --no-eta --typos 3 --big typos 3 --seedlist ./seedtoken.txt
Firstly, you have a typo. It should be --mnemonic-length 12. Your dash is in the wrong location.
Secondly, you don't need the --typos 3 or --big typos 3 arguments when using a tokens file. Your tokens file should be configured in such a way that it contains all the possible combinations to try. You can use these I believe, but they will exponentially increase your search space.
Thirdly, and the reason you are getting the "seed not found" error, is because you are using --seedlist instead of --tokenlist. The seedlist command tries every line in the text file as an individual seed, whereas the tokenlist command treats each line as an individual word in a potential seed phrase.
June 19, 2021, 09:31:07 AM
At your current speed of 178 million per hour, that's going to run for 442 days.
Welp, had to kill that process because I'm likely gonna have to pay the power bill in the next year and a half. But I did manage to get 9.6 billion results before I closed the terminal.
Now I'm still dealing with the seedlist token file and it doesn't wanna make things easy. I'm still convinced I'm not using this thing right or creating a correctly formatted token file.
My current argument is
Code:
python3 seedrecover.py --no-dupchecks --mnemonic-length 12 --language EN --dsw --no-eta --typos 3 --big typos 3 --seedlist ./seedtoken.txt
I then get the GUI pop ups
I cancel the wallet file
I select Bitcoin Standard BIP39/BIP44
I cancel Master xpub key
I cancel Addresses and run off the address DB
I chose the default 10 addy limit, then it runs
I've gone through all the different variations of what we've all discussed for the token file and it's giving me the 'seed not found, sorry' almost instantly, even when I remove the ^#^ in front of the word.
I know I got a winning approach, even if it might mean sitting on the thing for a weekend or even a week, but I don't believe some things are corresponding correctly.
June 19, 2021, 07:35:43 AM
For this shakedown pass I've initially gone with the "best guess" option with the 3 big typos in the argument. I saw the remarkable difference in this stress test and decided to let the thing fly. Just wondering if I'm expecting results by 9 billion without the word locks or if i'm gonna be waiting for weeks and should stop it now. After 31 hours I'm standing at 6.15 billion
Did you fill in 3 random words for the 3 words you had missing and then just run the basic recovery without a tokens file? If that's the case, then your other 9 words aren't locked, and so it will try replacing any 3 words in your seed phrase with others. Since there are 220 different ways to pick any 3 words out of 12, and there are 20483 possible combinations for those 3 words, then that would result in somewhere around 1.89 trillion combinations. At your current speed of 178 million per hour, that's going to run for 442 days. That doesn't even include other "typos" it might try, such as words being swapped or in the wrong order. June 19, 2021, 01:11:21 AM
So it's been 48 hours and I'm at 8.4 billion. I'll leave it overnight and check for replies in the morning. Maybe when I rise for the day I'll have some lucky surprise to greet me. If that happens i'll be like a kid again giddy for a new season of Saturday morning cartoons and a big bowl of sugary cereal.
Jump to: