Topic: Looking for a working configuration for a BTCrecover seedlist token file (Read 1016 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.
June 18, 2021, 12:26:33 PM
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
I've got the seedlist token file for the next attempt ready and waiting.
I've got the seedlist token file for the next attempt ready and waiting.
June 18, 2021, 03:26:46 AM
Hope I get results... My power bill is gonna suck this month 
You certainly deserve them given how much work you've put in. I'm not sure what the issue was with the previous attempt using Win 10 that made so many issues and ultimately making it crash.
Win 10
I think that's your problem right there. So at 17 hours for 3 billion combos, that's about 180 million an hour. To try 8.6 billion possibilities as above should take around 48 hours. With words 7/8 being swapped, and the last known word in position 3 or 4, that's 4 sets of 8.6 billion, coming in at 8 days (provided everything else in your tokens file is correct). Good luck!
June 17, 2021, 06:20:34 PM
So I hit a major milestone. I just hit 3 billion results at the 17 hour mark using the BTCrecover configured Ubuntu 20.04 OS with absolutely no issues at all. I'm not sure what the issue was with the previous attempt using Win 10 that made so many issues and ultimately making it crash.
The Linux method seems to have less jinxable bits to it. Gonna let it run till it gives me a reason to do my happy dance or it goes splat in which I've prepared the new token txt file.
The Linux method seems to have less jinxable bits to it. Gonna let it run till it gives me a reason to do my happy dance or it goes splat in which I've prepared the new token txt file.
June 17, 2021, 03:32:09 PM
Right now I'm running the routine with the "best guess" option. I was intending to see how stable this Linux OS is with BTCrecover. Originally it read at 48.5 kp/s which was half of what the Win 10 OS was putting out, but in this instance numbers did lie
I've been running it for 14 hours and I'm at 2.5 billion results. (around 200 million an hour) Thats a day and a half shorter than the Win 10 OS and it seems much more stable. I've witnessed ZERO hangups and it seems to keep pluggin and chuggin along. Once I cross 3 billion, I will know I got a better approach model. Anyone know how long this routine would run?
In regards to the seedlist token file, I know I can lock the loose known word to the third or fourth position. I am 90% certain I can lock positions for the others. And as you recommended, I can play mnemonic jenga and token tetris later if they don't play nicely.
Hope I get results... My power bill is gonna suck this month
I've been running it for 14 hours and I'm at 2.5 billion results. (around 200 million an hour) Thats a day and a half shorter than the Win 10 OS and it seems much more stable. I've witnessed ZERO hangups and it seems to keep pluggin and chuggin along. Once I cross 3 billion, I will know I got a better approach model. Anyone know how long this routine would run?
In regards to the seedlist token file, I know I can lock the loose known word to the third or fourth position. I am 90% certain I can lock positions for the others. And as you recommended, I can play mnemonic jenga and token tetris later if they don't play nicely.
Hope I get results... My power bill is gonna suck this month
June 17, 2021, 02:44:23 AM
Yeah, I think the best way to do thisnis going to be to lock words 7 and 8, and then lock the last known word to slot 3. Then, as you say, you need to include three lines of every word on the word list. This should give 8.6 billion possibilities. Run that to completion, and if no success then move the locked word from slot 3 to slot 4 and repeat. Do the same again moving it to slot 5, then to slot 6. Then reverse words 7 and 8 and do another 4 runs with the last word in slot 3, 4, 5, then 6.
I think this is the best way of approaching this without making your tokens file overly complicated, and also means if you crash or freeze you don't havenl to repeat everything from the very start.
I think this is the best way of approaching this without making your tokens file overly complicated, and also means if you crash or freeze you don't havenl to repeat everything from the very start.
June 16, 2021, 01:48:23 PM
Thank you oeleo for everything you've helped with. It's good to see you still rockin and rollin with me on the forum
I didn't even know what the listpass command did let alone how to implement it. I was worried creating too many things in the argument would contribute to bogging things down let alone going through to another crash. I'll look into this
Do you want to share you current tokens file (with the words obfuscated, of course) for us to take a look?
This is a mix of what I need and what I was trying to get to work
^1^1stwordlocked
^2^2ndwordlocked
one word is known out of 4 spots
7th and 8th words are known but unsure of order
^9^9thwordlocked
^10^tenthwordlocked
^11^eleventhwordlocked
^12^lastwordlocked
I believe I'm supposed to include 3 lines of all mnemonics here to fill the unknowns
I can try to narrow things down more but if I wanted to take the slow boat with a more assured approach for my needed results, I need the wiggle room at the sacrifice of time
I didn't even know what the listpass command did let alone how to implement it. I was worried creating too many things in the argument would contribute to bogging things down let alone going through to another crash. I'll look into this
My latest hangup is it completes too quickly and I have no confidence my seedlist token file was configured right
Have you tried using the --listpass command to have btcrecover print all the seed phrase combinations it is trying rather than actually trying them?BTCRecover can also print the seeds that will be tested via the --listpass command, something that can be useful for debugging your tokenlist
Do you want to share you current tokens file (with the words obfuscated, of course) for us to take a look?
This is a mix of what I need and what I was trying to get to work
^1^1stwordlocked
^2^2ndwordlocked
one word is known out of 4 spots
7th and 8th words are known but unsure of order
^9^9thwordlocked
^10^tenthwordlocked
^11^eleventhwordlocked
^12^lastwordlocked
I believe I'm supposed to include 3 lines of all mnemonics here to fill the unknowns
I can try to narrow things down more but if I wanted to take the slow boat with a more assured approach for my needed results, I need the wiggle room at the sacrifice of time
June 16, 2021, 04:20:32 AM
My latest hangup is it completes too quickly and I have no confidence my seedlist token file was configured right
Have you tried using the --listpass command to have btcrecover print all the seed phrase combinations it is trying rather than actually trying them?BTCRecover can also print the seeds that will be tested via the --listpass command, something that can be useful for debugging your tokenlist
Do you want to share you current tokens file (with the words obfuscated, of course) for us to take a look?
June 15, 2021, 05:59:10 PM
Happy Summer and hope everyone is enjoying some modicum of festivity in frivolity. It's been a minute or 2 since my last post and I am back with a working version of BTCrecover in a Linux OS environment.
After initial tests it seems to run slower than molasses over a witches nips in January but if I gotta sacrifice speed for stability for a time, I'll try once more before I run out and buy one of those new zen 3 rdna2 radeon 6000 gaming rigs to run btcrecover
As Oeleo worked out, I significantly need to decrease the amount of entropy left in my seedlist. Still trying to get a working configuration. My latest hangup is it completes too quickly and I have no confidence my seedlist token file was configured right
I still got some time this week to figure out how to modify my arguments for command line. Let me know if anyone has some working examples or insights.
After initial tests it seems to run slower than molasses over a witches nips in January but if I gotta sacrifice speed for stability for a time, I'll try once more before I run out and buy one of those new zen 3 rdna2 radeon 6000 gaming rigs to run btcrecover
As Oeleo worked out, I significantly need to decrease the amount of entropy left in my seedlist. Still trying to get a working configuration. My latest hangup is it completes too quickly and I have no confidence my seedlist token file was configured right
I still got some time this week to figure out how to modify my arguments for command line. Let me know if anyone has some working examples or insights.
March 30, 2021, 01:24:02 AM
Crypto Guide suggested I may be running out of memory and that's why the OS crashes at the same spot. I got 40 gb of memory and 6 disks in a 0 raid array. Can't think of any other reason why it would crash other than Win 10 or anything Microsoft would be the weakest link
Have you ever measured the memory usage from Task Manager? It's true you'll get a blue screen if you finish both your RAM and swap (and the swap itself is quite small ~8GB), but normally the system's supposed to slow down to a crawl first as your swap is filled and you're out of RAM.
Luckily or unluckily Win 10 wasnt compatible with the Nvidia GPU and I was relying on dual processors and 44 cores to pickup the slack. Given what I'm working with it seems to limp along ok.
I was considering setting up btcrecover on a linux OS since openCL can't take advantage of the outdated GPU, or I may run it on my gaming computer for a week or 3 if it will get better results.
I was considering setting up btcrecover on a linux OS since openCL can't take advantage of the outdated GPU, or I may run it on my gaming computer for a week or 3 if it will get better results.
I don't think Windows 10 will work with GeForce 8xxx and 9xxx if that's what you have, all newer cards should be recognized.
That may also explain why they don't have decent OpenCL support for them
Yeah, I got 40 GB of ram. That is a big 4 (four) 0 (zero) F O U R T Y GB of ram and it's still crashing.
So I'm gonna take a small break, let my head recover from bashing it into a wall so many times, then I will install ubuntu 20.04 then install all the needed packs for BTCrecover to work.
Thanx for all the help you guys have given me and hopefully when I return it will be with news of progress and potentially leading to a happy ending for this story.
March 30, 2021, 12:40:53 AM
Crypto Guide suggested I may be running out of memory and that's why the OS crashes at the same spot. I got 40 gb of memory and 6 disks in a 0 raid array. Can't think of any other reason why it would crash other than Win 10 or anything Microsoft would be the weakest link
Have you ever measured the memory usage from Task Manager? It's true you'll get a blue screen if you finish both your RAM and swap (and the swap itself is quite small ~8GB), but normally the system's supposed to slow down to a crawl first as your swap is filled and you're out of RAM.
Luckily or unluckily Win 10 wasnt compatible with the Nvidia GPU and I was relying on dual processors and 44 cores to pickup the slack. Given what I'm working with it seems to limp along ok.
I was considering setting up btcrecover on a linux OS since openCL can't take advantage of the outdated GPU, or I may run it on my gaming computer for a week or 3 if it will get better results.
I was considering setting up btcrecover on a linux OS since openCL can't take advantage of the outdated GPU, or I may run it on my gaming computer for a week or 3 if it will get better results.
I don't think Windows 10 will work with GeForce 8xxx and 9xxx if that's what you have, all newer cards should be recognized.
That may also explain why they don't have decent OpenCL support for them
March 29, 2021, 11:34:34 AM
So it did it again in likely the exact same spot of 2.8 billion.
Now I'm trying to work out where to stick the --autosave command in the argument. Could use some extra insight and common sense as my brain is migrating towards my sledgehammer at the moment.
Now I'm trying to work out where to stick the --autosave command in the argument. Could use some extra insight and common sense as my brain is migrating towards my sledgehammer at the moment.
Was your seedrecover invocation using GPU acceleration? Because sometimes a badly written nvidia CUDA program locks up or crashes not just Windows but also Linux systems.
This kind of thing should not happen if it is only CPU-bound, because the worst that would happen would just be a program crash.
Luckily or unluckily Win 10 wasnt compatible with the Nvidia GPU and I was relying on dual processors and 44 cores to pickup the slack. Given what I'm working with it seems to limp along ok.
I was considering setting up btcrecover on a linux OS since openCL can't take advantage of the outdated GPU, or I may run it on my gaming computer for a week or 3 if it will get better results.
March 29, 2021, 11:30:01 AM
Crypto Guide suggested I may be running out of memory and that's why the OS crashes at the same spot. I got 40 gb of memory and 6 disks in a 0 raid array. Can't think of any other reason why it would crash other than Win 10 or anything Microsoft would be the weakest link
March 29, 2021, 04:23:15 AM
So it did it again in likely the exact same spot of 2.8 billion.
Now I'm trying to work out where to stick the --autosave command in the argument. Could use some extra insight and common sense as my brain is migrating towards my sledgehammer at the moment.
Now I'm trying to work out where to stick the --autosave command in the argument. Could use some extra insight and common sense as my brain is migrating towards my sledgehammer at the moment.
Was your seedrecover invocation using GPU acceleration? Because sometimes a badly written nvidia CUDA program locks up or crashes not just Windows but also Linux systems.
This kind of thing should not happen if it is only CPU-bound, because the worst that would happen would just be a program crash.
March 29, 2021, 03:37:42 AM
Ahh, my bad. I just tried to use the autosave feature on mine and couldn't get it working either. On closer inspection, it seems it is only implemented for btcrecover (for passwords) and not for seedrecover (for seed phrases). There is an open GitHub issue about it, but it has not yet been implemented: https://github.com/3rdIteration/btcrecover/issues/45
I guess the best option for you then is going to be to simplify the tokenlist file as much as possible, and run it multiple times. So lock Word3 in to position 3, for example, and run that to completion. If no matches, then change Word3 to position 4, and go again. And so on.
I guess the best option for you then is going to be to simplify the tokenlist file as much as possible, and run it multiple times. So lock Word3 in to position 3, for example, and run that to completion. If no matches, then change Word3 to position 4, and go again. And so on.
March 28, 2021, 06:05:53 PM
So it did it again in likely the exact same spot of 2.8 billion.
Now I'm trying to work out where to stick the --autosave command in the argument. Could use some extra insight and common sense as my brain is migrating towards my sledgehammer at the moment.
Now I'm trying to work out where to stick the --autosave command in the argument. Could use some extra insight and common sense as my brain is migrating towards my sledgehammer at the moment.
March 28, 2021, 06:21:01 AM
I was 2 billion + passwords up, then the Win 10 OS crashed. I may be better off trying to run this in Linux since Win 10 is as stable as my X girlfriend
Lol, but what a nightmare!When you start running it again, include the argument --autosave savefile. This will make btcrecover save its progress with your tokenlist every 5 minutes or so. If it crashes again, then with the same tokenlist and the savefile you can pick up where you left off without having to start again as you are going to have to do now.
See here for more info: https://btcrecover.readthedocs.io/en/latest/TUTORIAL/#autosave
March 27, 2021, 08:12:31 PM
I was 2 billion + passwords up, then the Win 10 OS crashed. I may be better off trying to run this in Linux since Win 10 is as stable as my X girlfriend
March 27, 2021, 02:31:01 PM
I'm currently running a routine as if everything is locked except the 4 spots with the one known word in the 3 spots. I could reduce that to 2 spots if I want to be ambitious. I am currently at 1.845 billion possibilities and still counting.
I am 90% certain spots 9 and 10 are a lock. 7 and 8 are known but could be reversed.
I wish I could be more specific with spots 3-6 but at least I know one word.
Thanx again for helping me along in this mess. I hope the popcorn has been enjoyable.
I am 90% certain spots 9 and 10 are a lock. 7 and 8 are known but could be reversed.
I wish I could be more specific with spots 3-6 but at least I know one word.
Thanx again for helping me along in this mess. I hope the popcorn has been enjoyable.
March 27, 2021, 03:44:35 AM
If I was to give definitive locks to words 9 and 10,
POSSIBLY lock 7 and 8
By locking 9 and 10, you cut the number of possibilities in half. By locking 7 and 8, you cut it in half again. Doing both of these would take it down to 25.77 billion possibilities, which at your speeds would be around 15 days to exhaust the entire space (although bear in mind that the law of averages says you would find your seed phrase on average after 50% of this time, provided your seed phrase would be found by this tokensfile configuration at all).POSSIBLY lock 7 and 8
By far the biggest contribution to your number of possibilities is the 3 unknown words. Each of those has 2048 possibilities, meaning 20483 = 8.59 billion possibilities just for those 3 words.
March 26, 2021, 07:36:03 PM
Had to shut it down. 2 whole months running this thing is just too long. I believe I can narrow things down by one more step at least
^1^Word1
^2^Word2
^3^Word3 ^4^Word3 ^5^Word3
^7^Word7 ^8^Word7
^7^Word8 ^8^Word8
^9^Word9
^10^Word10
^11^Word11
^12^Word12
If I was to give definitive locks to words 9 and 10,
POSSIBLY lock 7 and 8
and only work with the 4 spaces with the one known word,
what would that do for my time table? I believe some of those would be an easy confirmation after a night or 2 worth of work.
^1^Word1
^2^Word2
^3^Word3 ^4^Word3 ^5^Word3
^7^Word7 ^8^Word7
^7^Word8 ^8^Word8
^9^Word9
^10^Word10
^11^Word11
^12^Word12
If I was to give definitive locks to words 9 and 10,
POSSIBLY lock 7 and 8
and only work with the 4 spaces with the one known word,
what would that do for my time table? I believe some of those would be an easy confirmation after a night or 2 worth of work.
March 26, 2021, 03:32:36 PM
OH boy... discovered the botch when trying to run it with no eta. My token file was correct, except the bottom 10 11 and 12th lines that had the bip39 wordlist. I had combined 3 in one so I was running 9 wordlists with "abandonzoo" conjoined. So I fixed the tokenfile and I'm currently running the argument with no eta.
Got 24 worker threads running and processing at a rate of 19.7 kP/s. 100 billion possibilities. At current processing time that's about 2 months right? Isnt the end of the word I guess 
Got 24 worker threads running and processing at a rate of 19.7 kP/s. 100 billion possibilities. At current processing time that's about 2 months right? Isnt the end of the word I guess
March 26, 2021, 02:57:20 PM
So is this the normal and expected way for this to function?
No, and I'm not sure why it is taking that long. Given that there are 3 possible configurations for Word3, 2 for Word7/8, 2 for Word 9/10, and 2048 each for Words 4, 5, and 6, then you are going to have just over 103 billion possible seed phrases to try. If it's has only managed to count (let alone attempt) 0.5 billion of them in 24 hours, then you are going to be waiting a long time.You could try running the whole command again with the additional argument of --no-eta, which should skip the "counting" step and go straight to the brute forcing step.
March 26, 2021, 12:34:54 PM
So it's morning and I've got over 450 million passwords so far. At last nights ETA was about 40 min. Now it's at 2 hours and counting. After a few more hours both cmd lines hung up again like it did yesterday. Not too worried and I'm not seeing billions of passwords in the future. Was averaging 100k new passwords every .5 seconds.
So is this the normal and expected way for this to function?
So is this the normal and expected way for this to function?
March 26, 2021, 12:14:50 AM
I hit a wall. The ETA was counting slowly from 3 minutes all the way up to 33 minutes over hours of time.
I was getting 100k new addresses every .25 seconds then after hours of building, it shortened to 100k every 20 seconds. After getting to 151 million, it stalled and didn't move for hours.
Started another cmd line and let it run for a couple hours, then both started working together
I'll let them both run overnight and see if anything results from not touching it.
I was getting 100k new addresses every .25 seconds then after hours of building, it shortened to 100k every 20 seconds. After getting to 151 million, it stalled and didn't move for hours.
Started another cmd line and let it run for a couple hours, then both started working together
I'll let them both run overnight and see if anything results from not touching it.
March 25, 2021, 06:34:11 PM
I just copied the python.py file, seedtoken.txt and the addresses file to the new and latest version of btcrecover. It's running. Using the seedtoken.txt file. NO hangups. Counting passwords and got an ETA.
Thanx for sticking it with me.
Thanx for sticking it with me.
March 25, 2021, 04:32:02 PM
AttributeError: 'Namespace' object has no attribute 'keep_tokens_order'
That's a bug with older versions. Just update to the master branch. https://github.com/3rdIteration/btcrecover/issues/121#issuecomment-776299682 March 25, 2021, 04:15:43 PM
So I modified the seedtoken.txt file to include only 12 lines.
9 lines of
^1^Word1
^2^Word2
^3^Word3 ^4^Word3 ^5^Word3
^7^Word7 ^8^Word7
^7^Word8 ^8^Word8
^9^Word9 ^10^Word9
^9^Word10 ^10^Word10
^11^Word11
^12^Word12
and the next 3 lines of the entire bip39 wordlist. Even with wordwrap off and all the words creating more lines, notepad still lists at the bottom "Ln 12 Col 38979" for the template
I used the argument with the changes to "--tokenlist" and it gave me the following
AttributeError: 'Namespace' object has no attribute 'keep_tokens_order'
I think we're getting close
9 lines of
^1^Word1
^2^Word2
^3^Word3 ^4^Word3 ^5^Word3
^7^Word7 ^8^Word7
^7^Word8 ^8^Word8
^9^Word9 ^10^Word9
^9^Word10 ^10^Word10
^11^Word11
^12^Word12
and the next 3 lines of the entire bip39 wordlist. Even with wordwrap off and all the words creating more lines, notepad still lists at the bottom "Ln 12 Col 38979" for the template
I used the argument with the changes to "--tokenlist" and it gave me the following
AttributeError: 'Namespace' object has no attribute 'keep_tokens_order'
I think we're getting close
March 25, 2021, 03:45:45 PM
Okay, I've been able to play around with this and I've got it working on my device. Here's what I needed to change from your set up.
First of all, your tokens file has to have exactly 12 lines in it. If you have 3 missing words in your seed phrase, then you must include 3 lines at the end, each line of which contains the entire BIP39 list of 2048 words separated by a space.
Secondly, you need to replace the --seedlist command with the --tokenlist command. The seedlist command treats every individual line of your tokens file as a complete seed phrase. The tokenlist command treats every individual line of your tokens file as one potential word contributing to your seed phrase.
I also removed the --bip32-path argument as I stated above.
So all in, my command looked like this:
And my tokens file looked like this:
Try that out and let us know how it goes.
First of all, your tokens file has to have exactly 12 lines in it. If you have 3 missing words in your seed phrase, then you must include 3 lines at the end, each line of which contains the entire BIP39 list of 2048 words separated by a space.
Secondly, you need to replace the --seedlist command with the --tokenlist command. The seedlist command treats every individual line of your tokens file as a complete seed phrase. The tokenlist command treats every individual line of your tokens file as one potential word contributing to your seed phrase.
I also removed the --bip32-path argument as I stated above.
So all in, my command looked like this:
Code:
python seedrecover.py --no-dupchecks --mnemonic-length 12 --language EN --dsw --wallet-type BIP39 --addr-limit 1 --tokenlist .\seedtoken.txt
And my tokens file looked like this:
Code:
^1^Word1
^2^Word2
^3^Word3 ^4^Word3 ^5^Word3
^7^Word7 ^8^Word7
^7^Word8 ^8^Word8
^9^Word9 ^10^Word9
^9^Word10 ^10^Word10
^11^Word11
^12^Word12
abandon ability able about above absent absorb abstract absurd abuse access accident account accuse achieve acid acoustic acquire across ...
abandon ability able about above absent absorb abstract absurd abuse access accident account accuse achieve acid acoustic acquire across ...
abandon ability able about above absent absorb abstract absurd abuse access accident account accuse achieve acid acoustic acquire across ...
^2^Word2
^3^Word3 ^4^Word3 ^5^Word3
^7^Word7 ^8^Word7
^7^Word8 ^8^Word8
^9^Word9 ^10^Word9
^9^Word10 ^10^Word10
^11^Word11
^12^Word12
abandon ability able about above absent absorb abstract absurd abuse access accident account accuse achieve acid acoustic acquire across ...
abandon ability able about above absent absorb abstract absurd abuse access accident account accuse achieve acid acoustic acquire across ...
abandon ability able about above absent absorb abstract absurd abuse access accident account accuse achieve acid acoustic acquire across ...
Try that out and let us know how it goes.
March 25, 2021, 02:02:08 PM
So my 12 word seed is based off knowing the first 2 words and their positions. The next 4 words are the most vague but I do know ONE of them for sure, just not sure which exact position. I know position 6 is a standalone word and NOT the known word. This is the format I was working with
BTCrecover is very unforgiving but for good reason. I had to account for every space and make sure nothing wasn't there unless it had a reason. A simple blank space left after a seed word, wouldn't even budge. I clear the lines up and it made every bit of difference
But in this process it halts as soon as I get to line 3
Keyerror: ^3^Word3
Haven't even gotten to the 7-10 lines but it seems to hang up on the way it's appears to be locked on word 3 as it's uncertain where it should be and I need to give it other words to process.
I'm trying to give it the command to include the known word in those first 3 spots then let it fill in the others randomly.
If I need to I can run the known word in different positions in several standalone tokens and let BTCrecover sort out the others but I wanted to do a single inclusive routine for my own sanity sake.
Code:
^1^Word1
^2^Word2
^3^Word3 ^4^Word3 ^5^Word3
^7^Word7 ^8^Word7
^7^Word8 ^8^Word8
^9^Word9 ^10^Word9
^9^Word10 ^10^Word10
^11^Word11
^12^Word12
^2^Word2
^3^Word3 ^4^Word3 ^5^Word3
^7^Word7 ^8^Word7
^7^Word8 ^8^Word8
^9^Word9 ^10^Word9
^9^Word10 ^10^Word10
^11^Word11
^12^Word12
BTCrecover is very unforgiving but for good reason. I had to account for every space and make sure nothing wasn't there unless it had a reason. A simple blank space left after a seed word, wouldn't even budge. I clear the lines up and it made every bit of difference
But in this process it halts as soon as I get to line 3
Keyerror: ^3^Word3
Haven't even gotten to the 7-10 lines but it seems to hang up on the way it's appears to be locked on word 3 as it's uncertain where it should be and I need to give it other words to process.
I'm trying to give it the command to include the known word in those first 3 spots then let it fill in the others randomly.
If I need to I can run the known word in different positions in several standalone tokens and let BTCrecover sort out the others but I wanted to do a single inclusive routine for my own sanity sake.
March 25, 2021, 12:59:49 PM
I've ran the argument and it appears to automatically default to the 8 GB address database that's generated from the bitcoin block. I'll include that portion of the argument if needs be.
Ah, ok. I didn't realize it has this functionality. If it seems to be working, then leave this out.This seed was made in Jan 2012 & it does seem I should include the bip32 path since it seems I was using Electrum only as a utility to look at things and to make the seedlist using bip39 EN words, nothing else.
In which case, just remove the --bip32-path argument. As long as you include --wallet-type bip39, it will automatically search the most common derivation paths for legacy, nested segwit, and segwit address, which includes m/44' 49' 84'/0'/0'/0.See here:
Quote from: https://btcrecover.readthedocs.io/en/latest/bip39-accounts-and-altcoins/#accounts-checked-by-default
By default, seedrecover.py will check the first account of each address type using common derivation paths for BIP39 wallets. (BIP39 will default to Bitcoin if no coin is specified)
Can you share the tokenlist file you used when it successfully gave you an ETA? (With your words obfuscated, obviously).
March 25, 2021, 12:21:39 PM
The current argument I have going is
You haven't specified what it is going to check against. You either need to provide a known address using the argument:Code:
python seedrecover.py --no-dupchecks --mnemonic-length 12 --language EN --dsw --wallet-type BIP39 --addr-limit 1 --bip32-path --seedlist .\seedtoken.txt
Code:
--addrs bc1YOURADDRESSHERE
Or provide it with an address database using the argument:
Code:
--addressdb ./PATH/DATABASEFILE.db
You also haven't specified a BIP32 path. Is it a P2PKH, P2SH, or P2WPKH wallet? If you want to check all of them, then leave out the --bip32-path argument as by specifying --wallet-type BIP39 it will automatically check all three. If you want to specify to only check one, then after --bip32-path you need to add "m/xx'/0'/0'/0" (including " at start and end), and replacing xx with 44, 49, or 84 respectively.
See the usage examples on this page: https://btcrecover.readthedocs.io/en/latest/Usage_Examples/2020-05-02_Descrambling_a_12_word_seed/Example_Descrambling_a_12_word_seed/
Good to see you Oeleo.
I've ran the argument and it appears to automatically default to the 8 GB address database that's generated from the bitcoin block. I'll include that portion of the argument if needs be.
This seed was made in Jan 2012 & it does seem I should include the bip32 path since it seems I was using Electrum only as a utility to look at things and to make the seedlist using bip39 EN words, nothing else.
python seedrecover.py --no-dupchecks --mnemonic-length 12 --language EN --dsw --wallet-type BIP39 --addr-limit 1 --bip32-path
m/44? 49? 84?'/00'/0'/0 --seedlist .\seedtoken.txtBut now the seedlist tokenfile aspect is the most troubling. Already tried the --seedlist --listpass tests with no luck. When I tried to include the seedlist, I got it to give me an ETA only once out of a week of attempts. Other than that it went kaput in a second.
I'll keep working on this as most of the hard work is done, now it's just a matter of dotting and crossing the I's & t's.
March 25, 2021, 04:50:18 AM
The current argument I have going is
You haven't specified what it is going to check against. You either need to provide a known address using the argument:Code:
python seedrecover.py --no-dupchecks --mnemonic-length 12 --language EN --dsw --wallet-type BIP39 --addr-limit 1 --bip32-path --seedlist .\seedtoken.txt
Code:
--addrs bc1YOURADDRESSHERE
Or provide it with an address database using the argument:
Code:
--addressdb ./PATH/DATABASEFILE.db
You also haven't specified a BIP32 path. Is it a P2PKH, P2SH, or P2WPKH wallet? If you want to check all of them, then leave out the --bip32-path argument as by specifying --wallet-type BIP39 it will automatically check all three. If you want to specify to only check one, then after --bip32-path you need to add "m/xx'/0'/0'/0" (including " at start and end), and replacing xx with 44, 49, or 84 respectively.
See the usage examples on this page: https://btcrecover.readthedocs.io/en/latest/Usage_Examples/2020-05-02_Descrambling_a_12_word_seed/Example_Descrambling_a_12_word_seed/
March 24, 2021, 07:58:15 PM
Got some Bitcoin in 2012 blah blah blah, read all about it here
https://bitcointalksearch.org/topic/m.56605523
Now that I got BTCrecover running, the last thing I need is to make the working argument and the seedlist token file
tried making one work based off this and it was a no go.
^1^Word1
^2^Word2
^3^Word3 ^4^Word3 ^5^Word3
^7^Word7 ^8^Word7
^7^Word8 ^8^Word8
^9^Word9 ^10^Word9
^9^Word10 ^10^Word10
^11^Word11
^12^Word12
The current argument I have going is
Tried running it without the token with additional argument and it gave me a 36 hour eta just counting possibilities and at 6 hours it was at 7 billion.
The seedlist token is the only way to be sure I'm doing it right if I do let it run for days or weeks. Let me know if you have any insight how to configure the seedlist token file correctly
https://bitcointalksearch.org/topic/m.56605523
Now that I got BTCrecover running, the last thing I need is to make the working argument and the seedlist token file
tried making one work based off this and it was a no go.
^1^Word1
^2^Word2
^3^Word3 ^4^Word3 ^5^Word3
^7^Word7 ^8^Word7
^7^Word8 ^8^Word8
^9^Word9 ^10^Word9
^9^Word10 ^10^Word10
^11^Word11
^12^Word12
The current argument I have going is
Code:
python seedrecover.py --no-dupchecks --mnemonic-length 12 --language EN --dsw --wallet-type BIP39 --addr-limit 1 --bip32-path --seedlist .\seedtoken.txt
Tried running it without the token with additional argument and it gave me a 36 hour eta just counting possibilities and at 6 hours it was at 7 billion.
The seedlist token is the only way to be sure I'm doing it right if I do let it run for days or weeks. Let me know if you have any insight how to configure the seedlist token file correctly
Jump to: