Quote from: nc50lc on March 07, 2024, 07:16:03 AM

Quote from: kauai_lost_boi on March 05, 2024, 09:17:12 PM

-snip- I will configure my BTCrecover either on the current POP OS or try to get a flavor that can get pyopencl running correctly for GPU acceleration. I will then go over the different Electrum versions while trying to get the V-1.* derivation path to work along with the other possible avenues of approach discussed. Might take me some days but I will update the progress as it rolls out.

BTW, some clarifications with the "quite huge search space" for --big-typos 8, based from the uncertain words in the other post.
I mean that it's huge that it's not humanly possible to brutefoce even with your GPU; and for the follow-up,
I can't find other options in seedrecover to set a tokenlist in v1.x electrum seed so it has to rely on "best guess" and "--big-typos", maybe someone else does.

If you can make a bunch of manual "3 mistakes" iterations of your mnemonic phrase based from the know and possible words, that will make it plausible.

Example (now based from this):

Quote from: kauai_lost_boi on March 02, 2024, 05:33:18 PM

^1^knownwordlocked
^2^knownwordlocked
^7^knownwordlocked
^8^knownwordlocked
^9^knownwordlocked
^10^knownwordlocked
^11^knownwordlocked
^12^knownwordlocked
5 words including the known word that is position 3 or 4
5 words including the known word that is position 3 or 4
5 words NOT including the known word that is position 3 or 4
2 words that are position 6

There's only two attempts that should be made with --big-typos 3:
1st "best guess": word1 word2 word3A word4A word5A word6A word7 word8 word9 word10 word11 word12
2nd "best guess": word1 word2 word3A word4A word5A word6B word7 word8 word9 word10 word11 word12

Since there are only 4 uncertain words in this case and word6 has only two possible words, you can let it bruteforce up to 3 mistakes in two separate attempts with word6-A and word6-B.
That's faster than setting it to --big-typos 4.

Hey peoples. Just wanted to poke my head in and give an update as to what my latest attempts have lead too. Once again I cannot begin to fathom the amount of invaluable information and assistance I have been given in this new leg of approach and in my entire experience chasing down every lead for years. Thank you all for sharing your time, advice and determination to help me and others along the way.

I am at a much more refined place after I researched all the great information gathered in this thread. We have narrowed down the version of Electrum used, We've come up with ways to implement varying approaches to BTCrecover but the most important fact we've all but confirmed is this key I'm after behaves in a unique and unorthodox way because of the way it was derived by the Electrum version.

I was able to not only use the "best guess" method for BTCrecover using the Electrum 1.* derivation selection, but I was also able to forge an argument allowing me to use the token file. But then began the problem. Even though I have one of the most powerful PC configs, when this thing went to work with 32 threads, I was just a few degrees short of hitting red. I think my major issue was getting BTCrecover to use GPU acceleration but I've been having issues finding a Debian based distro that uses the proprietary AMD drivers or finding a way for BTCrecover to recognize the CPU and not label the hardware "generic" in the terminal error data.

So now it is a hardware issue that needs to be resolved before I can proceed further. So far, nc50lc, apogio & Pmalek have been exemplary with their spot-on knowledge and when I do get a working method on both the hardware and software end of things, we can move ever more closer to the glorious final resolution.