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.
Topic: Looking for a working configuration for a BTCrecover seedlist token file - page 2. (Read 985 times)
June 18, 2021, 12:26:33 PM
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.
Jump to: