|
Title: The FinderOuter, a bitcoin recovery tool (v0.19.1 2024-01-24) Post by: Coding Enthusiast on January 01, 2020, 05:07:03 AM Table of Contents
Introduction The FinderOuter is a bitcoin recovery tool that focuses on making the recovery process easy for everyone with any level of technical knowledge. It uses a simple user interface with a list of recovery options. Each option has an explanation and many hints helping user figure out what is needed. It always consist of filling some text boxes and selecting some options and finally clicking the Find button. This eliminates the need to read long guide pages on how to use the application. Each option also has some example cases that can show a simple preview of how each option should be filled for different cases. FinderOuter is specialized for maximum efficiency, each recovery option and their parts are written from scratch and all those parts down to the basic cryptography used (such as SHA, ECC,...) are specialized for that operation. Thanks to .Net core and AvaloniaUI FinderOuter can run on all operating systems. This project is written fully in C# and is 100% open source and will always remain free to use. You can make a donation if you found this tool useful.. FinderOuter is still in beta and under development. New features are slowly added and everything is optimized. Contribution is always welcome. Please report any bugs you find or any improvement suggestions you have by creating a new issue (https://github.com/Coding-Enthusiast/FinderOuter/issues/new). Quick guide
https://www.talkimg.com/images/2023/11/15/z4YpD.jpeg ↑ (#post_tocHeader) Features 1. Message signature verification User can enter a message signature here to verify it. In case there is a problem with the message (except being an actually invalid signature), the code can search to find the common issues that some signing tools have and fix them. 2. Missing Base-58 characters This option can be used to recover any base-58 encoded string with a checksum that is missing some characters. For example a damaged paper wallet where some characters are erased/unreadable. The position of missing characters must be known. It works for (1) WIFs (Base-58 encoded private key) (2) Addresses (Base-58 encoded P2PKH or P2SH address) (3) BIP-38 (Base-58 encoded encrypted private key). 3. Missing Base-16 characters This option is similar to previous feature but works for base-16 (hexadecimal) private keys. Since there is no checksum in this encoding it requires an additional input to check each permutation against. It accepts any address type and public keys. This option is slower in comparison because it uses ECC and that is not yet optimized. 4. Missing mini-privatekey characters This option is similar to 2 and 3 but works for mini-privatekeys (eg. SzavMBLoXU6kDrqtUVmffv). It requires the corresponding address or public key of the minikey to check each possible key against, as a result it is also slower since it depends on ECC and has 2 additional hashes. 5. Missing mnomonic (seed) words This option works for both BIP-39 and Electrum mnemonics that have some missing words. It requires knowing one child (private/public) key or address created from that seed and the exact derivation path of it. 6. Missing mnemonic passphrase This option is used to recover the extension words (aka passphrase) used in mnemonics. It works for both BIP-39 and Electrum mnemonics algorithms. The available passphrase recovery modes are: a. Alphanumeric: This is when the passphrase consists of letter, numbers and symbols and is random. Example: OT!pA?8i b. CustomChars: This mode allows user to define their own set of characters to be used in the passphrase. c. soon 7. Missing BIP-38 password This option can recover passwords used in encrypting bitcoin private keys using the BIP-38 proposal. The available password recovery modes are the same as mnemonic passphrase option. 8. Missing BIP-32 derivation path This option could be used to find derivation path of a child key (private key, public key or the address) by having the mnemonic or the extended master keys (xprv or xpub). It only checks a hard-coded list of popular derivation paths. 9. Missing characters in Armory recovery phrase This option is used to recover Armory paper backups (containing 2 or 4 lines of 36 characters in Base-16 with custom char-set) that are missing some of their characters. Since the last 4 characters of each line is the checksum this option can be very fast (1 trillion keys/sec) if the checksum is available or extremely slow (100 key/sec) if not. 10. Missing string encoding This option could be used to determine the encoding of an arbitrary text. It currently supports Base-16, Base-43, Base-58, Base-58 with checksum and Base-64. All inputs will be converted to hexadecimal. ↑ (#post_tocHeader) Links Source code on GitHub: https://github.com/Coding-Enthusiast/FinderOuter Want to help? Review the code and leave your feedback in this topic about the code, features any possible bug(s), ... Contributions are always welcome. Here is the conventions (https://github.com/Autarkysoft/Conventions) that FinderOuter adheres to. If You found this tool helpful consider making a donation: 1Q9swRQuwhTtjZZ2yguFWk7m7pszknkWyk (bitcoin:1Q9swRQuwhTtjZZ2yguFWk7m7pszknkWyk) bc1q3n5t9gv40ayq68nwf0yth49dt5c799wpld376s (bitcoin:bc1q3n5t9gv40ayq68nwf0yth49dt5c799wpld376s) ↑ (#post_tocHeader) To Do List (aka future features!) See roadmap here: https://github.com/Coding-Enthusiast/FinderOuter/issues/47
Title: Re: The FinderOuter Post by: Coding Enthusiast on January 01, 2020, 05:07:18 AM Major Updates (see commits on github for details)
Complete change-log: https://github.com/Coding-Enthusiast/FinderOuter/blob/master/CHANGELOG.md Title: Re: The FinderOuter (initial release 2020-01-01) Post by: ABCbits on January 01, 2020, 06:49:34 PM I see you're switching to .NET Core and user don't need to deal with dependency at all. I can even run it on niche Linux distro :)
As for finding missing Base58, IMO you should consider scenario when user missing few character but don't know location of the missing character. Title: Re: The FinderOuter (initial release 2020-01-01) Post by: Coding Enthusiast on January 02, 2020, 02:41:23 AM I see you're switching to .NET Core and user don't need to deal with dependency at all. I can even run it on niche Linux distro :) Yeah, netcore has been a fantastic decision by Microsoft. It is not only runs on multiple OS/platforms but also is fully open source and also highly optimized.I'll slowly migrate all of my previous projects (eg. transaction tool) to netcore too but as a new project called Denovo (https://github.com/Autarkysoft/Denovo). As for finding missing Base58, IMO you should consider scenario when user missing few character but don't know location of the missing character. Thanks for your feedback. I'll add this to my to-do list.Title: Re: The FinderOuter (initial release 2020-01-01) Post by: buwaytress on January 02, 2020, 10:39:03 AM Cool beans. I suppose we'll just have to look for those inevitable threads of people who've lost access and see if this tool will help them the way it's designed to (opening it up, putting in a line and clicking go). Still needs a bit of basic understanding for the casual user though (that includes people like me).
Title: Re: The FinderOuter (initial release 2020-01-01) Post by: Coding Enthusiast on January 16, 2020, 12:27:33 PM Next release (0.2.0) is probably going to take some more time as I am busy releasing Denovo (20k LoC so far) these days and the next feature requires optimization of ECC. However I keep releasing the code which could be used if you compile it yourself.
New feature is Missing Mnemonic which is when you have a seed phrase missing a couple of words. There is also a changelog (https://github.com/Coding-Enthusiast/FinderOuter/blob/master/CHANGELOG.md) which helps you follow all the changes (and commits). There is also a continuous integration workflow to ensure successful builds and deployment. you should consider scenario when user missing few character but don't know location of the missing character. I haven't been able to come up with a way to generalize this. The alternative is to hard code it for each case individually (one method for missing 1 char, another for 2 and so on) which I don't really like. I'm going to place it in an issue #1 (https://github.com/Coding-Enthusiast/FinderOuter/issues/1) until I can come up with a neat solution.Title: Re: The FinderOuter (initial release 2020-01-01) Post by: bitmover on January 16, 2020, 01:01:28 PM
Will it verify messages from Segwit addresses? It is still a problem, only Electrum does that until now, as far as I know. I am only able to sign from legacy addresses using most software Title: Re: The FinderOuter (initial release 2020-01-01) Post by: Coding Enthusiast on January 16, 2020, 01:11:21 PM Will it verify messages from Segwit addresses? Of course it will. The 3 basic script types used in signing are supported (https://github.com/Coding-Enthusiast/FinderOuter/blob/f62a32013b368047ac8a490c9443caf1a7961c0a/Src/FinderOuter/Services/MessageSignatureService.cs#L88-L116): P2PKH (address starting with 1), P2WPKH (address starting with bc1) and P2SH-P2WPKH (address starting with 3). I don't think there is anything else left apart from BIP-322 which I will add soon. Title: Re: The FinderOuter (initial release 2020-01-01) Post by: LoyceV on February 16, 2020, 10:17:50 PM Quote from another topic:
Thanks is there a tool i can use to recover ? as i must have missed a few characters off or could someone help me via private message as i do not want to disclose it on here !! You could use The FinderOuter (https://bitcointalk.org/index.php?topic=5214021.0). Compile it from source code or download the released version, run it offline. The program only has 2 options for now and you need the second option ("Missing Base58"). I believe the rest is self explanatory.It should take a second to find the right key(s) with 3 missing characters. Any chance you can add a loop to search all possible locations for the 3 missing characters? That is, assuming the rest of JBRai's key is correct. I've tested it with a known key: it takes about 2 seconds to find 3 missing characters. To do the same on 3 unknown locations would take about 58^3 times longer, which means several days, but it'll still be manageable. Title: Re: The FinderOuter (initial release 2020-01-01) Post by: Coding Enthusiast on February 18, 2020, 06:15:41 PM I'm trying to recover JBRai's private key with 49 out of 52 characters known. I've installed The FinderOuter (in a VM), but it asks for the locations of the missing characters. Any chance you can add a loop to search all possible locations for the 3 missing characters? That is, assuming the rest of JBRai's key is correct. I've tested it with a known key: it takes about 2 seconds to find 3 missing characters. To do the same on 3 unknown locations would take about 58^3 times longer, which means several days, but it'll still be manageable. I'm not a math expert but I think it should take 20,825 times longer (583=195,112)*. There is also the fact that the underlying algorithm will also be different that lacks most of the pre-computation that the current algorithm for known missing places has so it will be slightly slower. However, as I said before I have no idea how to generalize this so I hardcoded the heck out of it (only for this special case: missing 3 chars, probably will add a couple more smaller cases later), the benefit of it is that I know how to run it in parallel so the more threads your CPU has the faster it would run and I don't think 4 billion is going to take that long to finish. * The problem with not knowing the missing places is that you'll have to first select different locations then loop through the 58 possible characters and keys are long (52/51 characters) so things get out of hand quickly. Example: Code: 1 missing char (assuming compressed key): 20,825 in last example (like others) is calculated using combination (https://en.wikipedia.org/wiki/Combination) in mathematics which is n!/[k!(n-k)!] where n is 51 for compressed keys (52 char long with first one fixed to K or L) and k is 3 (the 3 missing places). https://github.com/Coding-Enthusiast/FinderOuter/commit/73e8596993cdf68be49a4f20ba52afa2b1c1a5b1 Here is a preview, will publish a released version soon (the checkbox needs to be selected to enable this "special" case): https://i.imgur.com/O0Ggs6s.jpg Title: Re: The FinderOuter (v0.1.1 2020-02-19) Post by: Coding Enthusiast on February 19, 2020, 07:31:37 AM Version 0.1.1 is released.
https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.1.1.0 See changelog (https://github.com/Coding-Enthusiast/FinderOuter/blob/master/CHANGELOG.md#release-011-2020-02-19) for more information. Most notable changes are: - A new feature for a special case where a compressed private key has 3 missing characters at unknown locations. - Some small optimizations, bug fixes and improvements. Future ideas (as soon as I publish my Bitcoin.Net (https://github.com/Autarkysoft/Denovo#bitcoinnet) library): - Recovering mini private keys with missing characters (eg. a damaged physical coin) - Converting versioned private keys (BIP-178 and a couple of Electrum versions) to normal keys - Finding BIP-32 paths by only having the mnemonic/xkeys and a single child address/key Title: Re: The FinderOuter (v0.1.1 2020-02-19) Post by: LoyceV on February 19, 2020, 10:21:49 AM Version 0.1.1 is released. Thanks for the improvements! It's currently running, I expect it to take around 18 hours. I didn't give the VM full CPU access (80% of 2 CPUs) so it shouldn't bother me too much.https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.1.1.0 I don't have high hopes though: I tested all possible combinations of JBRai's private key with 54 characters, and none of them lead to a valid private key. I've seen what he wrote down, and apart from too many or not enough characters, he also has terrible handwriting, which makes it likely there are more mistakes. If this doesn't produce any result, I'll stop trying. It's not the first time I've seen someone lose access to funds because of bad hand writing. And that's why I always try to recover anything before funding a key: test your backups! Update: After 4.5 hours, it produced a private key! But the key is invalid, so something must have gone wrong in checking the key. Title: Re: The FinderOuter (v0.1.1 2020-02-19) Post by: iluvbitcoins on February 20, 2020, 02:34:56 PM Why do all of these bruteforce things run on Linux/Ubuntu? :D
Only btcrecover is for Windows :-\ Dunno if it's better to run this on a VM Linux or use btcrecover on Windows? I have an integrated GPU :S Title: Re: The FinderOuter (v0.1.1 2020-02-19) Post by: LoyceV on February 20, 2020, 03:01:20 PM Why do all of these bruteforce things run on Linux/Ubuntu? :D Lol, I actually had to install a bunch of Microsoft tools to run it, so I guess it works on Windows too.Title: Re: The FinderOuter (v0.1.1 2020-02-19) Post by: Coding Enthusiast on February 21, 2020, 07:04:31 AM Why do all of these bruteforce things run on Linux/Ubuntu? :D FinderOuter can run on any operating system. You just have to compile it yourself if you want to run it on Windows since I've only released the compiled version for 64-bit Linux OS. I can release more compiled versions if there is an overwhelming demand for it but security-wise it is best if you run it on a clean Linux specially if you are a windows user and want to use the same OS you use daily and may already be infected without you even knowing it.Why do all of these bruteforce things run on Linux/Ubuntu? :D Lol, I actually had to install a bunch of Microsoft tools to run it, so I guess it works on Windows too.Title: Re: The FinderOuter (v0.1.1 2020-02-19) Post by: LoyceV on February 21, 2020, 10:04:03 AM hmm. Did you use the released zip file under "releases" and run it on Linux or did you compile it yourself? Because I can see you needing to install extra stuff for compiling (SDKs, Nuget packages,...) but there is no need to download anything else if you run the compiled version since it is self contained meaning even the framework (.net core) is included. I did not know that! As a Linux user, I picked the only tar.gz available, and didn't look at the zip. That indeed gave me the source code, and I followed instructions there.Title: Re: The FinderOuter (v0.1.1 2020-02-19) Post by: Coding Enthusiast on February 21, 2020, 02:00:57 PM I did not know that! As a Linux user, I picked the only tar.gz available, and didn't look at the zip. That indeed gave me the source code, and I followed instructions there. It is GitHub that automatically adds the repository's source code as both a zip file and a tarball whenever a new release is published there (both named Source code) so that the source code at that exact commit is always available under the same binaries. In any case, thanks for the report. I've added a short explanation to the ReadMe file that can hopefully prevent similar future confusions. Title: Re: The FinderOuter (v0.1.1 2020-02-19) Post by: LoyceV on February 21, 2020, 03:03:48 PM Update: After 4.5 hours, it produced a private key! But the key is invalid, so something must have gone wrong in checking the key. Any idea why this could have happened?Title: Re: The FinderOuter (v0.1.1 2020-02-19) Post by: Coding Enthusiast on February 21, 2020, 06:47:58 PM Update: After 4.5 hours, it produced a private key! But the key is invalid, so something must have gone wrong in checking the key. Any idea why this could have happened?Do you know the reason for the key being invalid (for example is it the checksum, invalid character or out of range value)? Or is it just producing a different address? (You could use bitaddress.org for decoding, it will tell you the reason). Title: Re: The FinderOuter (v0.1.1 2020-02-19) Post by: LoyceV on February 21, 2020, 06:55:51 PM Do you know the reason for the key being invalid (for example is it the checksum, invalid character or out of range value)? Or is it just producing a different address? (You could use bitaddress.org for decoding, it will tell you the reason). I tried Electrum and Mycelium, both didn't tell me the reason. I didn't use bitaddress because I couldn't run it offline at that moment. I guess the checksum must have failed.The resulting key was the original, with 2 characters added at one place, and further one 1 character added. I was very hopeful at that moment that it would have found the the correct key. Title: Re: The FinderOuter (v0.1.1 2020-02-19) Post by: Coding Enthusiast on February 21, 2020, 07:55:28 PM I ran some tests with different compressed keys with 3 missing characters at different locations while editing the code to limit the search space (to shorten the time for tests), I couldn't figure out the issue since they all succeed.
https://github.com/Coding-Enthusiast/FinderOuter/commit/e949a711dc5dfcbaa01d393ebaa32e3ea8911507 With this commit, when an invalid but full key (no missing characters) is typed in that text box, the message is more clear about where the problem was. Title: Re: The FinderOuter (v0.1.1 2020-02-19) Post by: CoolBeans333 on February 23, 2020, 10:28:00 PM Hi, is there a way for this tool to work for TRX private key? My private key is messing 4 characters at the end of it.
Thank you Title: Re: The FinderOuter (v0.1.1 2020-02-19) Post by: Coding Enthusiast on February 24, 2020, 05:08:37 AM Hi, is there a way for this tool to work for TRX private key? My private key is messing 4 characters at the end of it. This project is designed to only work for bitcoin but it may be used for any altcoin that is similar to bitcoin. I took a quick look at Tron's source code and it seems like it is using the same curve (secp256k1) as bitcoin and has base58 encoding although I couldn't figure out if they use the same encoding for WIFs. If your key encoding is hexadecimal then it doesn't work but if it is a base-58 encoded string with a checksum and same additional bytes then you can use this tool. Title: Re: The FinderOuter (v0.1.1 2020-02-19) Post by: AmirKsh on February 25, 2020, 12:15:56 PM Hello Coding Enthusiast / first i want to thank you for working on such a software with a GUI user friendly because as you said , there are people who do not know to use/apply a code or even use the cmd ( and belive me there are a lot of them) ; your software just makes the things more easy :D
On the other hand i also have a problem with my private key but your software will not work for my scenario because my key is saved in 64 hexadecimal format: If you would modify the software to accept also the hexa format and not only base58 , i would send you a small tip as soon as i will recover my private key (i have 7 missing characters out of 64;i know the location of them ) here is the original post of my matter if you want to take a look please : https://bitcointalk.org/index.php?topic=5227915.0 Also i belive this update will help others too and not only me because there are many people who prefer the hexadecimal format and not base58 because even if the first one it's longer (64 hexa characters instead of 51/52 base58 characters) , you don't have to deal with capital or small letters :) especially for cold paper wallets it is prefered this method waiting for a replay from you :D i will keep my prommise and send a tip/donation to you as soon as i recover my private key Title: Re: The FinderOuter (v0.1.1 2020-02-19) Post by: Coding Enthusiast on February 25, 2020, 02:18:35 PM On the other hand i also have a problem with my private key but your software will not work for my scenario because my key is saved in 64 hexadecimal format: If you would modify the software to accept also the hexa format and not only base58 OK, let me see what I can do but unlike base-58 it will be very slow since it requires EC point multiplication which is slow by nature and my ECC code is particularly slow since I still haven't had time to optimize it. I'll post an update here when it is finished. Title: Re: The FinderOuter (v0.1.1 2020-02-19) Post by: Coding Enthusiast on March 10, 2020, 10:54:48 AM Version 0.1.2 is released.
https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.1.2.0 See changelog for more details. Most notable changes are: - New feature: missing chars in base-16 encoded keys (unfortunately unlike other options this is very slow for now) - Simplified Base-58 option to no longer need a checkbox for special case. - Base-58 will return a friendly error message if a full private key was entered and was invalid. - Some optimization and code cleanup. Title: Re: The FinderOuter (v0.1.2 2020-03-10) Post by: AmirKsh on March 16, 2020, 08:34:50 AM hey Coding Enthuziast thank you for the update , i was not expected to be done that soon .
i've downloaded your software aaand ...now it seem i have another obstacle :((( oooh man , it never eeeends :((( the software you made is for Ubuntu Linux , well i have a macbook ,anyway i also have a virtual machine windows 10 app installed ( the name of application is Parallels Desktop-it is a virtual Windows 10 with full licence wich is running inside my IOS ) I opened the virtual windows 10 and tryed to install inside , a virtualbox with ubuntu ! something like : Ubuntu running inside Windows 10 , running inside an IOS , a mess, i know :)))))) but they don't let do do that :(((( i think i can not run a virtual machine inside another virtual machine I've seen on github on your page some instructions for converting the software and make it run in windows but i can not handlle them :( how can i make it run on Windows 10 or IOS??? with instructions step by step for noobs .... :/ Hey , and by the way , you said the soft will run verry slow for base16 privatekeys, well , just curios.... how slow ? like 1/2 private keys per seconds ?? with all of that beeing said , i want to thank you again for your efort :D Title: Re: The FinderOuter (v0.1.2 2020-03-10) Post by: Coding Enthusiast on March 16, 2020, 11:23:21 AM the software you made is for Ubuntu Linux , well i have a macbook I'd recommend doing the following (more info here: https://github.com/Coding-Enthusiast/FinderOuter#running-the-finderouter):1. Download FinderOuter release or source and build it yourself (deterministic builds and PGP signature will be added in near future) 2. Download Ubuntu 3. Verify Ubuntu's iso 4. Disconnect network cable (to remain offline) 5. Boot from a DVD or USB 6. Run FinderOuter I've seen on github on your page some instructions for converting the software and make it run in windows but i can not handlle them :( how can i make it run on Windows 10 or IOS??? with instructions step by step for noobs .... :/ You may find it easier if you used Visual Studio (https://visualstudio.microsoft.com/vs/mac/), if you install that then all you have to do is to open the solution file (FinderOuter.sln) and change solution configuration to "Release" and build using Build > Build solution from menu or press Ctrl+Shift+B and you'll find the binary atCode: ...\Src\FinderOuter\bin\Release\netcoreapp3.1\FinderOuter.dll If you didn't want to download VS. then MSDN has some good posts to get you started on how to use dotnet commands. https://docs.microsoft.com/en-us/dotnet/core/get-started An example: https://docs.microsoft.com/en-us/dotnet/core/tutorials/cli-create-console-app the dotnet build command: https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-build Basically you'll have to run: Code: dotnet build FinderOuter.sln --configuration Release --runtime osx-x64 Hey , and by the way , you said the soft will run verry slow for base16 privatekeys, well , just curios.... how slow ? like 1/2 private keys per seconds ?? To have a comparison the Base-58 part searches for 1.4 million keys per second but the Base-16 part is searching for 1200 keys/sec on my PC.I am trying to optimize ECC (which is what slows things down here) but unfortunately that will take a very long time to be ready. Title: Re: The FinderOuter (v0.1.2 2020-03-10) Post by: Dydy94 on March 22, 2020, 09:39:53 AM Bonjour l'équipe,
Je voudrais savoir ? Les sauvegarde bit coin core : Peuvent elles être récupérer avec le logiciel? (FinderOuter) Je n'arrive pas à le télécharger. De plus j'ai pas ubuntu . Juste Windows 8. Merci pour votre réponse (Sauvegarde bitcoin core dans un fichier) ( je n'ai pas réussis avec btcrecover ou pywallet) Title: Re: The FinderOuter (v0.1.2 2020-03-10) Post by: Coding Enthusiast on March 22, 2020, 05:35:32 PM Sorry, The FinderOuter doesn't support wallet files (bitcoin core backups) yet.
And please ask your questions in English so that I don't have to use Google Translate. Title: Re: The FinderOuter (v0.1.2 2020-03-10) Post by: bonhomme on April 21, 2020, 05:54:31 AM Thank you for all Coding Enthusiast. But that's very difficult to follow for people who are not involved in IT, I tried all night long to launch FinderOuter but that doesn't work... maybe I am too idiot.
Title: Re: The FinderOuter (v0.1.2 2020-03-10) Post by: Coding Enthusiast on April 22, 2020, 06:18:26 AM Thank you for all Coding Enthusiast. But that's very difficult to follow for people who are not involved in IT, I tried all night long to launch FinderOuter but that doesn't work... maybe I am too idiot. Did you try to build the project from source code and faced difficulties or did you try to run the compiled version (the 27 MB file called v0.1.2.0.zip) and had problems?And please mention the difficulties you encountered explicitly so that I could improve the project and make things easier. Title: Re: The FinderOuter (v0.2.0 2020-05-11) Post by: Coding Enthusiast on May 11, 2020, 03:35:04 AM Version 0.2.0 is released.
https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.2.0.0 See changelog (https://github.com/Coding-Enthusiast/FinderOuter/blob/master/CHANGELOG.md) for more details. Most notable changes are: - Replacing backend with the well tested Bitcoin.Net (https://bitcointalk.org/index.php?topic=5224578.0) library which improves performance and fixes some bugs - Added 2 new features: recovering Base-58 addresses and BIP-38 encrypted keys - Fix some bugs including a bug that prevented the FinderOuter from running on Ubuntu 20 Title: Re: The FinderOuter, a bitcoin recovery tool (v0.2.0 2020-05-11) Post by: xgustavoo on May 16, 2020, 11:30:10 AM Hello!
I have an address with 12 characters left. Is it feasible to try to recover? "Total number of keys to test: 1.449.225.352.009.601.191.936" Could this take years? Title: Re: The FinderOuter, a bitcoin recovery tool (v0.2.0 2020-05-11) Post by: LoyceV on May 16, 2020, 12:24:27 PM I have an address with 12 characters left. Is it feasible to try to recover? Do you mean a private key with 12 characters left? Forget it!If it's an address, 12 characters is enough to check if it holds funds (https://bitcointalk.org/index.php?topic=5246271.msg54438145#msg54438145). Title: Re: The FinderOuter, a bitcoin recovery tool (v0.2.0 2020-05-11) Post by: xgustavoo on May 18, 2020, 01:34:05 PM It is a privatekey with 51 characters, I lost 12 characters. I lost everything? :(
Title: Re: The FinderOuter, a bitcoin recovery tool (v0.2.0 2020-05-11) Post by: Coding Enthusiast on May 18, 2020, 02:14:29 PM It is a privatekey with 51 characters, I lost 12 characters. I lost everything? :( Short answer is it's impossible to recover this private key since the number of possible keys to check is enormous. You'll need to construct and compute 1,449*1018 hashes, in comparison current total bitcoin hashrate (the entire bitcoin mining power) is about 100*1018 and that is hash of a rather fixed input that doesn't have the same additional computation step on each round. That means even if you had all the ASICs operating today and had a way of modifying them to compute the hash you want, you still wouldn't even be able to go through 5% of the cases. On top of that since the number of missing characters is huge, the number of correct results is going to be large and in order to go through all of them there is another bottleneck which is computation of public key and if needed the address to compare with an input (FinderOuter doesn't do that in current version). PS. I don't want to get your hopes up but there may be a small chance if you have your public key. I still haven't looked into the algorithm (Pollard's kangaroo) but it may be possible if we could get a manageable range of keys from what you already have. Merging 2 consecutive comments I tried Electrum and Mycelium, both didn't tell me the reason. I didn't use bitaddress because I couldn't run it offline at that moment. I guess the checksum must have failed. The resulting key was the original, with 2 characters added at one place, and further one 1 character added. I was very hopeful at that moment that it would have found the the correct key. I still haven't been able to find any problem that involves checksum, it appears to be working correctly. However I found another problem while testing. It was due to checksum collision and the fact that second character was missing, it ended up producing a wrong starting byte hence an invalid key. I'm currently refactoring the way reports work and will add more checks before printing result. For now my latest commit is a simple fix that makes the loop continue running (like all the rest of the loops!). The result is that even if it finds an invalid key it still continues running until it searches the entire space so there may be another possible key down the line that is valid. https://github.com/Coding-Enthusiast/FinderOuter/commit/5ed05806c64a7790a8c9c300fe5722809bc7e4ec For reference the test vector was this: Code: K**M*jGmerYanjeui5SHS7JkmpZ*VipYvB2*JGU1ZxJwYvP98617 Title: Re: The FinderOuter, a bitcoin recovery tool (v0.4.0 2020-06-30) Post by: Coding Enthusiast on July 23, 2020, 03:06:29 PM Version 0.3.0 is released. https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.3.0.0 See changelog (https://github.com/Coding-Enthusiast/FinderOuter/blob/master/CHANGELOG.md) for more details. Most notable changes are: - New feature: mini-privatekey (of length 22, 26 or 30) missing characters - Some bug fixes in missing base-58 option - Improved reports Version 0.4.0 is released. Version 0.4.1 is released.https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.4.0.0 See changelog (https://github.com/Coding-Enthusiast/FinderOuter/blob/master/CHANGELOG.md) for more details. Most notable changes are: - New feature: BIP-39 mnemonic recovery - Code improvement, optimization of hash algorithms, more tests https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.4.1.0 See changelog (https://github.com/Coding-Enthusiast/FinderOuter/blob/master/CHANGELOG.md) for details. This is a minor version released with a little bit of delay that introduces the Example button. It is an easy and quick way of seeing how to fill different text boxes. Hopefully it can clear some confusions that some beginners may have with things such as BIP-32 paths. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.5.0 2020-09-17) Post by: Coding Enthusiast on September 17, 2020, 05:29:55 AM Version 0.5.0 released (The Parallelization Update)
This is the parallelism update with tons of optimization from a small 10% speed gain to more than 1800% in some cases. - Most of these optimizations are in Base58 recovery option. - Compressed and uncompressed private key recovery uses all available CPU cores for maximum speed and at 100% capacity. - Two special cases were added to recover private keys that are missing characters from their end (up to 9 missing for uncompressed and 11 for compressed is the default for now and can be recovered in less than a minute). - Recovery of Base58 addresses and BIP-38 encrypted keys are also optimized the same way. - Mini private key recovery - It uses all available CPU cores - It suffers from the known issue #9 (https://github.com/Coding-Enthusiast/FinderOuter/issues/9) - The extra input has more options like other recovery options to enter different types of addresses or a public key. - Mnemonic recovery - New wordlist added (Czech) - There is a simple checkbox now to set the key index itself to be hardened - It suffers from the known issue #9 (https://github.com/Coding-Enthusiast/FinderOuter/issues/9) whenever there is EC multiplication involved (private key to public key), otherwise if there weren't any the code will run at maximum efficiency using all cores at 100% (see 5th example in mnemonic recovery (https://github.com/Coding-Enthusiast/FinderOuter/blob/937ac0f7edb4663db65c93d0df3369333f0af010/Src/FinderOuter/ViewModels/MissingMnemonicViewModel.cs#L237-L258)) Other most notable changes: - Now there is a progress bar at the bottom that will be used when recovering in parallel to show the progress so far. Other times when using single core the recovery process never takes up longer than a minute (usually less than 10 seconds) so progress bar is disabled. - Addition of more examples for each recovery option. - Various code improvements and bug fixes. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.5.0 2020-09-17) Post by: dextronomous on November 04, 2020, 06:25:01 PM Hi Coding Enthusiast, i cant compile it >:( broken os.
could you get a compiled one up and ready to use, for windows 10 probably, thanks a lot, just did fix the not compiling issue, used ps net . Title: Re: The FinderOuter, a bitcoin recovery tool (v0.5.0 2020-09-17) Post by: Coding Enthusiast on November 05, 2020, 02:41:21 AM Hi Coding Enthusiast, i cant compile it >:( broken os. Glad it worked out for you but you should know that it is not safe to handle your private keys and other secrets on Windows specifically if the system is what you regularly use for everything else too. This is why I have only released compiled version for Linux.could you get a compiled one up and ready to use, for windows 10 probably, thanks a lot, just did fix the not compiling issue, used ps net . Title: Re: The FinderOuter, a bitcoin recovery tool (v0.6.0 2020-12-24) Post by: Coding Enthusiast on December 24, 2020, 05:40:29 AM Version 0.6.0 is released.
https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.6.0.0 See changelog (https://github.com/Coding-Enthusiast/FinderOuter/blob/master/CHANGELOG.md) for details.
As you may already know FinderOuter has always been a bitcoin recovery tool but we may add altcoin recovery options some day. By request I created a new branch for recovering Tron private keys, it can recover a hexadecimal Tron private key if you have the damaged hex and your public key or address. https://github.com/Coding-Enthusiast/FinderOuter/tree/Tron Title: Re: The FinderOuter, a bitcoin recovery tool (v0.6.0 2020-12-24) Post by: dextronomous on December 25, 2020, 12:48:07 AM Version 0.6.0 is released. https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.6.0.0 See changelog (https://github.com/Coding-Enthusiast/FinderOuter/blob/master/CHANGELOG.md) for details.
As you may already know FinderOuter has always been a bitcoin recovery tool but we may add altcoin recovery options some day. By request I created a new branch for recovering Tron private keys, it can recover a hexadecimal Tron private key if you have the damaged hex and your public key or address. https://github.com/Coding-Enthusiast/FinderOuter/tree/Tron Hi there Coding Enthusiast, got it working now, thanks again for this great piece, merry christmas, Title: Re: The FinderOuter, a bitcoin recovery tool (v0.6.0 2020-12-24) Post by: BlackHatCoiner on January 07, 2021, 07:39:33 AM Is FinderOuter available for console only? I believe that it would go faster. Also question, can I run it with my gpu? I'm brute forcing an mnemonic with 10 words and it has to search among 4.1 million mnemonics. I left it all night, it seems to be in the middle.
Edit: Another question, does it searches until it finds the correct mnemonic or does it try all the possible combinations first? As I said I've reached the middle and I want to know if my chances are getting smaller. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.6.0 2020-12-24) Post by: Coding Enthusiast on January 07, 2021, 03:22:46 PM Is FinderOuter available for console only? I believe that it would go faster. No. UI isn't consuming that much CPU power, it is just a thread that will be updated every now and then.Quote Also question, can I run it with my gpu? Not yet.Quote I'm brute forcing an mnemonic with 10 words and it has to search among 4.1 million mnemonics. I left it all night, it seems to be in the middle. 10 words out of how many? 2 missing out of 12 takes only an hour on my old PC, having 10 out of more like 24 is impossible to brute force.Quote Edit: Another question, does it searches until it finds the correct mnemonic or does it try all the possible combinations first? As I said I've reached the middle and I want to know if my chances are getting smaller. It will stop as soon as it finds the correct combination of words and prints the result.Title: Re: The FinderOuter, a bitcoin recovery tool (v0.6.0 2020-12-24) Post by: BlackHatCoiner on January 07, 2021, 05:15:53 PM 10 words out of how many? 2 missing out of 12 takes only an hour on my old PC, having 10 out of more like 24 is impossible to brute force. Really? It just finished after 19 hours.There are 12 words in the given mnemonic with 2 missing. A total of 4,194,304 mnemonics should be checked. Running in parallel. Elapsed time: 19:02:45.5941064 k/s= 61 I must have a really slow PC. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.6.0 2020-12-24) Post by: Coding Enthusiast on January 07, 2021, 05:43:33 PM I must have a really slow PC. Sorry I should have asked about your path first, BIP39 recovery speed depends a lot on the path, doubly so in my code that has a known issue with ECC.Generally speaking the shorter your path is (eg. m/0 vs m/0/0/0/0) the faster the recovery. The more hardened indexes the path has (eg. m/0'/0'/0'/0' vs m/0/0/0/0) the faster the recovery. Additionally when the path is using hardened indexes it avoids the issue in FinderOuter so the speed goes up by a lot and it can also use the all CPU cores. To compare your PC speed with mine in the most optimal case check out the fifth example. On my corei3 CPU it barely takes 3 min (0:02:40) to check the 4.1 million cases. https://imgur.com/a/uRHbDef Title: Re: The FinderOuter, a bitcoin recovery tool (v0.6.0 2020-12-24) Post by: BlackHatCoiner on January 07, 2021, 09:44:06 PM It will stop as soon as it finds the correct combination of words and prints the result. I've noticed that this works only if you've chosen "Electrum". This is what happens on BIP39:https://i.imgur.com/NW3n3gN.png Nevermind, I had to change path equal with m/84'/0'/0'/0 Generally speaking the shorter your path is (eg. m/0 vs m/0/0/0/0) the faster the recovery. What? Why should this be true? Am I missing anything? Besides, I tried it and it goes terribly slow, just like before.Title: Re: The FinderOuter, a bitcoin recovery tool (v0.6.0 2020-12-24) Post by: Coding Enthusiast on January 08, 2021, 05:55:48 AM I've noticed that this works only if you've chosen "Electrum". This is what happens on BIP39: Whenever there is an "additional info" textbox in any of the recovery options, the result is always checked against that and the loop will break as soon as the comparison was successful.Quote What? Why should this be true? Am I missing anything? Besides, I tried it and it goes terribly slow, just like before. Each depth adds another round of HMACSHA512 and some small math for all index types, but also adds another EC point multiplication if the index wasn't hardened. For example m/0 only performs one additional EC mult and one HMACSHA512 compared to m/0/0/0/0 which has to perform 4 which makes it 4 times slower. Have you tried the 5th example? Just click on Example button 5 times, and it should only take a minute to solve. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.6.0 2020-12-24) Post by: BlackHatCoiner on January 08, 2021, 07:35:14 AM To compare your PC speed with mine in the most optimal case check out the fifth example. On my corei3 CPU it barely takes 3 min (0:02:40) to check the 4.1 million cases. https://imgur.com/a/uRHbDef This is me when I try the fifth example: https://i.imgur.com/aQC7oWg.png It most likely going to take more than 2 hours. I don't get why it only takes you 3 minutes to do that on BIP39. (On electrum it takes a minute to me) Title: Re: The FinderOuter, a bitcoin recovery tool (v0.6.0 2020-12-24) Post by: Coding Enthusiast on January 08, 2021, 09:33:22 AM It most likely going to take more than 2 hours. I don't get why it only takes you 3 minutes to do that on BIP39. (On electrum it takes a minute to me) Is your CPU older than mine? Or are you running FinderOuter in some sandbox/virtual machine that could limiting the CPU usage?If in example 5 I switch BIP39 to Electrum and change the path from m/0 back to m/0' then it only takes 11 seconds to check all combinations. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.6.0 2020-12-24) Post by: BlackHatCoiner on January 08, 2021, 09:38:14 AM Is your CPU older than mine? Or are you running FinderOuter in some sandbox/virtual machine that could limiting the CPU usage? If I'm not mistaken I have I-Duo Core. I'm running FinderOuter from Visual studio. The purpose is that I can't open the executable. https://i.imgur.com/70YIMIx.png Once I click "Yes", nothing happens. That's why I run it from visual studio. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.6.0 2020-12-24) Post by: Coding Enthusiast on January 08, 2021, 10:04:57 AM I believe your CPU is slower than mine but the main reason is that you are adding bottlenecks that are significantly slowing down the application.
First and biggest one is that you are running it in Debug mode which doesn't have a lot of the optimization. Switch to Released mode and you will experience a much faster run. Additionally when you run any application through V.S. it automatically attaches a debugger that will consume some CPU power and can slightly slow down the application. If you want to run it without V.S. then you either have to install .net or publish the application. Here is a walk-through: https://docs.microsoft.com/en-us/dotnet/core/tutorials/publishing-with-visual-studio Title: Re: The FinderOuter, a bitcoin recovery tool (v0.6.0 2020-12-24) Post by: BlackHatCoiner on January 08, 2021, 10:24:52 AM Switch to Released mode and you will experience a much faster run. I switched it, built it and ran it from FinderOuter\Src\FinderOuter\bin\Release\net5.0\FinderOuter.exe. I tried the 5th example again. It should take few minutes, but still, it takes long.Title: Re: The FinderOuter, a bitcoin recovery tool (v0.6.0 2020-12-24) Post by: BlackHatCoiner on January 17, 2021, 06:23:22 PM About the BIP39 option: Does it skip non-valid checksum mnemonics? I was wondering, because it would make brute forcing much faster. On electrum it takes much less time than on BIP39. Why does that happen?
Another question, are there wallets that generate non-valid checksum mnemonics? Title: Re: The FinderOuter, a bitcoin recovery tool (v0.6.0 2020-12-24) Post by: Coding Enthusiast on January 18, 2021, 07:37:47 PM Does it skip non-valid checksum mnemonics? Of course it does. Example for 24 words (https://github.com/Coding-Enthusiast/FinderOuter/blob/3a5d557812ae63aeee024c8da996197f69e0f3b7/Src/FinderOuter/Services/MnemonicSevice.cs#L555)On electrum it takes much less time than on BIP39. Why does that happen? It is because the slowest part of the code is SetBip32(...) (https://github.com/Coding-Enthusiast/FinderOuter/blob/3a5d557812ae63aeee024c8da996197f69e0f3b7/Src/FinderOuter/Services/MnemonicSevice.cs#L72) method and it is only called when the checksum of the created mnemonic is valid. When we call it less times, the speed is going to be a lot higher.The number of times checksum is valid depends on the size of the checksum, the bigger it is the less collision occurs and SetBip32() is called less times. A 12-words BIP39 mnemonic only has a 4-bit checksum while a 12-word Electrum mnemonic has at least 8 bits of checksum (8 bits for standard type, 12 bits for other types). Back to our 5th example Code: duck firm october practice soccer * result regret unveil * uncle ginger SetBip32() call count time The reason why the last 3 numbers are slightly different despite having the same checksum size is based on luck. Another question, are there wallets that generate non-valid checksum mnemonics? Not that I know of.Title: Re: The FinderOuter, a bitcoin recovery tool (v0.6.0 2020-12-24) Post by: cost203 on January 19, 2021, 09:59:36 AM Hi,
Does it work with Wallet.dat ? i have a wallet.dat and btc never arrived to it... Title: Re: The FinderOuter, a bitcoin recovery tool (v0.6.0 2020-12-24) Post by: Coding Enthusiast on January 19, 2021, 11:41:05 AM Does it work with Wallet.dat ? No.Quote i have a wallet.dat and btc never arrived to it... That is not a problem that a "recovery tool" can solve.Title: Re: The FinderOuter, a bitcoin recovery tool (v0.6.0 2020-12-24) Post by: cost203 on January 27, 2021, 07:33:41 AM thanks,
But a wallet have not a lot of adress in it ? in the past i go explore with python my wallet.dat and there was 50 or 100 adress in it... Title: Re: The FinderOuter, a bitcoin recovery tool (v0.7.0 2021-02-02) Post by: Coding Enthusiast on February 02, 2021, 02:10:26 AM Version 0.7.0 is released.
https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.7.0.0 See changelog (https://github.com/Coding-Enthusiast/FinderOuter/blob/master/CHANGELOG.md) for details.
https://bitcointalk.org/Themes/custom1/images/bdaycake.gif FinderOuter is 1 year old Title: Re: The FinderOuter, a bitcoin recovery tool (v0.7.0 2021-02-02) Post by: dextronomous on February 06, 2021, 10:32:10 PM thanks a lot for another greater release.
i have a question, could you make it search in a specific bit range=x thanks a lot. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.7.0 2021-02-02) Post by: Coding Enthusiast on February 07, 2021, 09:42:07 AM thanks a lot for another greater release. You're welcome.i have a question, could you make it search in a specific bit range=x If you mean something similar to the "puzzle solving" projects where they go from 2n to 2n+1 to find the private key to an address/pubkey then I don't think I'll ever add such an option to FinderOuter since the purpose of this tool is to help users recover their coins not to solve puzzles.But in some ways FinderOuter is essentially doing the same thing (although it needs more optimization), each option with a missing base58, base16 or mnemonic is searching within a fixed range. I also have a plan to let the user limit the search space if that's what you meant. For example in mnemonic recovery user would be able to set a smaller range of words (like 5) to set in place of a particular missing word instead of using the entire 2048 words. This requires some major refactor so I'm putting it off for now. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.7.0 2021-02-02) Post by: dextronomous on February 08, 2021, 04:05:06 PM thanks for the fast response, and yes that was a bit with the "puzzle" thing in mind,
like the range 8000000-fffffff or like with the numbers 1-160? great thanks noticing all the changes you applying to you'r newer versions. i noticed that with some lets say 17 characters amount of total keys to check as with 16 characters missing, stayed the same. but anyway a 110% release. and good luck so far. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.7.0 2021-02-02) Post by: Volken on February 08, 2021, 07:03:36 PM Quote I also have a plan to let the user limit the search space if that's what you meant. For example in mnemonic recovery user would be able to set a smaller range of words (like 5) to set in place of a particular missing word instead of using the entire 2048 words. This requires some major refactor so I'm putting it off for now. That would be great. For missing characters inside a private key choosing options like "numbers only" or "letters only" or putting a range of potential characters that you would remember can be realy useful and a time changer. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.7.0 2021-02-02) Post by: Coding Enthusiast on February 09, 2021, 04:45:47 AM i noticed that with some lets say 17 characters It shouldn't be the same. We simply compute 58missCount using BigInteger (has no size limit) and report that as the total number of keys to check. So the result should always be different if the number of missing characters are different.amount of total keys to check as with 16 characters missing, stayed the same. https://github.com/Coding-Enthusiast/FinderOuter/blob/26e3de339f56c702ddcfadaa8483dcc7ad1ea9c6/Src/FinderOuter/Services/Base58Sevice.cs#L106 Title: Re: The FinderOuter, a bitcoin recovery tool (v0.7.0 2021-02-02) Post by: BlackHatCoiner on February 15, 2021, 12:06:20 PM Hi, I have a question. Let's assume that I've forgotten 1 word out of 12. This means that it'll have to try among 2048 combinations. Does it skip the checksum validation? Because if it checks for valid checksums it should not take that much time. For example, when I have 2 missing words, it has to check among 20482 different combinations. But if it counts the checksum, it should take less than an hour.
I remember a thread talking about mnemonic checksum, but I can't find it so I'll ask it here. How many are the valid mnemonics assuming that there is one word missing? Title: Re: The FinderOuter, a bitcoin recovery tool (v0.7.0 2021-02-02) Post by: Coding Enthusiast on February 15, 2021, 03:04:34 PM Hi, I have a question. Let's assume that I've forgotten 1 word out of 12. This means that it'll have to try among 2048 combinations. Does it skip the checksum validation? Because if it checks for valid checksums it should not take that much time. For example, when I have 2 missing words, it has to check among 20482 different combinations. But if it counts the checksum, it should take less than an hour. I explained last time: https://bitcointalk.org/index.php?topic=5214021.msg56129399#msg56129399Let me know if you have any additional questions. I remember a thread talking about mnemonic checksum, but I can't find it so I'll ask it here. How many are the valid mnemonics assuming that there is one word missing? It is not possible to predict because it depends on how many collisions (purely by chance) we are going to get. It usually is somewhere between 120 and 130 for BIP39 and about 6 for Electrum.Title: Re: The FinderOuter, a bitcoin recovery tool (v0.7.0 2021-02-02) Post by: BlackHatCoiner on February 15, 2021, 03:38:29 PM I explained last time: https://bitcointalk.org/index.php?topic=5214021.msg56129399#msg56129399 Okay then, I'll reply on your previous post:Let me know if you have any additional questions. The number of times checksum is valid depends on the size of the checksum, the bigger it is the less collision occurs and SetBip32() is called less times. 4-bit checksum means 1 in 16. That's why you've written 261,774 (~ 20482 / 16) on the SetBip32() call count?A 12-words BIP39 mnemonic only has a 4-bit checksum while a 12-word Electrum mnemonic has at least 8 bits of checksum (8 bits for standard type, 12 bits for other types). Quote SetBip32() call count time I still don't understand why you wrote 00:02:44. There is no machine that can do so many operations in such little time. On my pc, brute forcing a 12-words mnemonic with 2 words missing takes me around 12 hours. (Given only the address) Title: Re: The FinderOuter, a bitcoin recovery tool (v0.7.0 2021-02-02) Post by: Coding Enthusiast on February 15, 2021, 04:06:22 PM 4-bit checksum means 1 in 16. That's why you've written 261,774 (~ 20482 / 16) on the SetBip32() call count? Essentially yes. I modified the code to add a simple counter that incremented on each call.I still don't understand why you wrote 00:02:44. There is no machine that can do so many operations in such little time. On my pc, brute forcing a 12-words mnemonic with 2 words missing takes me around 12 hours. (Given only the address) It's not really that many operations.Each SetBip32() method consists of 2048 HMACSHA512 + (path depth * 1 HMACSHA512). That is 2050 HMACSHA512 for brute forcing m/0'/0'. The 2:44 min is to compute 536,636,700 HMACs in total (it's actually a lot less due to using "specialized" code). The specialized part is that FinderOuter isn't using the general HMAC functions, everything is specialized to compute only what it's supposed to. For example each HMAC consists of computing at least 2 SHA512 and each SHA512 has at least 2 blocks to compress. PBKDF2 (the 2048 round) repeats this in a loop where roughly 50% of it (4094 block compressions) is skipped on each call which greatly improves the speed. The only reason why it takes a much longer time (hours) to recover using an address is because of issue #9 (https://github.com/Coding-Enthusiast/FinderOuter/issues/9). ECC on its own is very slow and my implementation of it turns out to be terribly slow. Additionally when the path is something like m/0/0 the final round (after the PBKDF2) is to compute public keys (so there is an ECMultiply) which is a slow process itself. As a result the recovery process becomes a lot slower and the slowness of FinderOuter on top of it makes it take that long. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.7.0 2021-02-02) Post by: BlackHatCoiner on February 15, 2021, 04:18:21 PM Additionally when the path is something like m/0/0 the final round And for me that I want to brute force a lot of derivation paths, makes the entire process even slower. This is what I enter on these fields:I'd also like to ask something else. Is it possible to brute force multiple mnemonics one after the other? One per line? If not, do you plan on doing something similar in the future? (Like adding some extra features on FinderOuter, not necessarily multiple mnemonics at once) Title: Re: The FinderOuter, a bitcoin recovery tool (v0.7.0 2021-02-02) Post by: Coding Enthusiast on February 15, 2021, 05:09:17 PM I'd also like to ask something else. Is it possible to brute force multiple mnemonics one after the other? One per line? If not, do you plan on doing something similar in the future? (Like adding some extra features on FinderOuter, not necessarily multiple mnemonics at once) Normally people have one mnemonic that is damaged and want to recover it and if they have more they can just enter the second one after the first finished. I don't think there is any point in accepting more than one at a time.You can make minimal modification to the code to run it for yourself though. Change this line (https://github.com/Coding-Enthusiast/FinderOuter/blob/68aa8f53d1b41b6616be9a2e6991e3d2a743c512/Src/FinderOuter/ViewModels/MissingMnemonicViewModel.cs#L149-L152) into a loop where it breaks each line into a single mnemonic and makes the call. And modify the Init() (https://github.com/Coding-Enthusiast/FinderOuter/blob/68aa8f53d1b41b6616be9a2e6991e3d2a743c512/Src/FinderOuter/Services/MnemonicSevice.cs#L1483) on report so that it doesn't clear the report on each call. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.7.0 2021-02-02) Post by: BlackHatCoiner on February 15, 2021, 06:24:11 PM Change this line (https://github.com/Coding-Enthusiast/FinderOuter/blob/68aa8f53d1b41b6616be9a2e6991e3d2a743c512/Src/FinderOuter/ViewModels/MissingMnemonicViewModel.cs#L149-L152) into a loop where it breaks each line into a single mnemonic and makes the call. And modify the Init() (https://github.com/Coding-Enthusiast/FinderOuter/blob/68aa8f53d1b41b6616be9a2e6991e3d2a743c512/Src/FinderOuter/Services/MnemonicSevice.cs#L1483) on report so that it doesn't clear the report on each call. I'll have to admit that your code is literally beautiful. Everything is organized and I can understand the functionalities of each file. Somehow, FinderOuter on Visual Studio 2019 goes really fast in contrast with my WinForms programs. Does it have to do with Avalonia? How did they manage to make it that light? Anyway, I got off topic. What I wanted to say is that by changing line 149 on ViewModels/MissingMnemonicViewModel.cs and line 1483 on Services/MnemonicSevice.cs it's not possible. For example line 1425 on Services/MnemonicSevice.cs returns me "Invalid mnemonic length." when I try to add more than one mnemonics: Code: words = mnemonic.Split(new char[] { ' ' }, StringSplitOptions.RemoveEmptyEntries);I guess that everything goes dominos if I change it to: Code: words = mnemonic.Split(new char[] { ' ' }, StringSplitOptions.RemoveEmptyEntries);Thanks in advance! Title: Re: The FinderOuter, a bitcoin recovery tool (v0.7.0 2021-02-02) Post by: Coding Enthusiast on February 16, 2021, 05:35:13 AM I'll have to admit that your code is literally beautiful. Everything is organized and I can understand the functionalities of each file. Somehow, FinderOuter on Visual Studio 2019 goes really fast in contrast with my WinForms programs. Does it have to do with Avalonia? How did they manage to make it that light? Thanks. I believe XAML is generally cleaner and faster for UI development but I'm not sure since I haven't really used WinForms myself.Anyway, I got off topic. What I wanted to say is that by changing line 149 on ViewModels/MissingMnemonicViewModel.cs and line 1483 on Services/MnemonicSevice.cs it's not possible. For example line 1425 on Services/MnemonicSevice.cs returns me "Invalid mnemonic length." when I try to add more than one mnemonics: The FindMissing(..) in Service expects a single mnemonic, changing that is a lot of work so you should just change the ViewModel code to call it more than one time with each mnemonic instead of onceVM code turns into: Code: public async override void Find() Code: public async Task FindMissing(string mnemonic, char missChar, string pass, .... https://github.com/Coding-Enthusiast/FinderOuter/blob/681225416796a926479c8d246fb7afbf1e34484c/Src/FinderOuter/Models/Report.cs#L60 Code: Message += $"{Environment.NewLine}Finished checking first input. Moving on to next.{Environment.NewLine}";Now you can enter multiple mnemonics in mnemonic textbox in mnemonic recovery option separating them with a new line and each will be checked one after the other. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.7.0 2021-02-02) Post by: BlackHatCoiner on February 17, 2021, 08:13:13 AM The FindMissing(..) in Service expects a single mnemonic, changing that is a lot of work so you should just change the ViewModel code to call it more than one time with each mnemonic instead of once I did had changed that. I wasn't taking the entire string with all the lines and starting the brute force. I just used for loop instead foreach as you did. But, I still face the same issue. I replaced everything you said, the Find() and the Message on Report.cs, but still I ge tthe same error: As for this one: Quote nvironment.NewLine Why is it nvironment? Why not Environment? Based on your code, it doesn't seem you've used it as a variable.Title: Re: The FinderOuter, a bitcoin recovery tool (v0.7.0 2021-02-02) Post by: Coding Enthusiast on February 17, 2021, 10:14:22 AM but still I ge tthe same error Try placing a break point where the error is being created and see what input is being checked. That should give you a good idea where the problem is. Here (https://github.com/Coding-Enthusiast/FinderOuter/blob/68aa8f53d1b41b6616be9a2e6991e3d2a743c512/Src/FinderOuter/Services/MnemonicSevice.cs#L1415-L1418) is the error message. See what the value of mnemonic is.My guess is that the input is not split into separate lines correctly. Why is it nvironment? Why not Environment? Based on your code, it doesn't seem you've used it as a variable. That's a typo.Title: Re: The FinderOuter, a bitcoin recovery tool (v0.7.0 2021-02-02) Post by: BlackHatCoiner on February 17, 2021, 10:42:55 AM Here (https://github.com/Coding-Enthusiast/FinderOuter/blob/68aa8f53d1b41b6616be9a2e6991e3d2a743c512/Src/FinderOuter/Services/MnemonicSevice.cs#L1415-L1418) is the error message. See what the value of mnemonic is. I don't believe that's the error message. Once I change it to the following I still get "Invalid mnemonic length.", that I shouldn't.Code: words = mnemonic.Split(new char[] { ' ' }, StringSplitOptions.RemoveEmptyEntries);I wanted to see, what mnemonic it reads. Is there any other part of the source code that prints the same error? That's a typo. Okay, changed.Title: Re: The FinderOuter, a bitcoin recovery tool (v0.7.0 2021-02-02) Post by: Coding Enthusiast on February 17, 2021, 11:27:03 AM I wanted to see, what mnemonic it reads. Is there any other part of the source code that prints the same error? No. https://github.com/Coding-Enthusiast/FinderOuter/search?q=Invalid+mnemonic+lengthAll I can think of is that you should debug the code line by line and see where it calls report.Fail("") (remember to change to debug mode if you haven't already). Title: Re: The FinderOuter, a bitcoin recovery tool (v0.7.0 2021-02-02) Post by: BlackHatCoiner on February 17, 2021, 11:43:42 AM All I can think of is that you should debug the code line by line and see where it calls report.Fail("") (remember to change to debug mode if you haven't already). It doesn't make sense. I comment the specific part of the code, but I still get the same error. Maybe, I do something wrong on building. Yes, I use Debug, but I've never used Avalonia in the past. Is there something that I have to prepair before building? I've also noticed that there is no syntax error detector shown in VS. For example, I can write something that is considered invalid inside a file, but it'll be normally built. It makes me curious. Do I change the program or not? Code: /*words = mnemonic.Split(new char[] { ' ' }, StringSplitOptions.RemoveEmptyEntries);https://i.imgur.com/PpgGFEI.png Title: Re: The FinderOuter, a bitcoin recovery tool (v0.7.0 2021-02-02) Post by: Coding Enthusiast on February 17, 2021, 01:01:10 PM Maybe, I do something wrong on building. Probably. This has nothing to do with the UI (Avalonia).Inside your Visual Studio place a break on the Find method line and then go to Debug > Start debugging (F5). After that enter your data in text boxes and click find, the execution should stop at that line where you placed the break. https://i.imgur.com/pGJzJKN.jpg Then continue pressing F11 to step into each method or F10 to step over until you figure out where the evaluation is failing. You can move your mouse over to any variable and see their value when in debug mode. https://i.imgur.com/M5gemIU.jpg I can write something that is considered invalid inside a file, but it'll be normally built. It makes me curious. Do I change the program or not? Did you open the solution file or the csproj file or did you just open the .cs file from your explorer? Because the only thing that I can think of is that when you open a .cs file you can't build it, it has to be inside a .csproj file.This file: https://github.com/Coding-Enthusiast/FinderOuter/blob/v0.6.0.0/Src/FinderOuter.sln or this https://github.com/Coding-Enthusiast/FinderOuter/blob/v0.6.0.0/Src/FinderOuter/FinderOuter.csproj Title: Re: The FinderOuter, a bitcoin recovery tool (v0.8.0 2021-03-20) Post by: Coding Enthusiast on March 20, 2021, 06:20:06 AM Version 0.8.0 is released.
https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.8.0.0 See changelog (https://github.com/Coding-Enthusiast/FinderOuter/blob/master/CHANGELOG.md) for details.
A small RoadMap
I've also started working on optimizing ECC to hopefully solve issue #9 (https://github.com/Coding-Enthusiast/FinderOuter/issues/9) but it's still very challenging. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.8.0 2021-03-20) Post by: Stroncow on April 04, 2021, 09:01:32 PM This fraudster is selling your software : https://youtu.be/zowg-o4Fszk
Title: Re: The FinderOuter, a bitcoin recovery tool (v0.8.0 2021-03-20) Post by: Coding Enthusiast on April 05, 2021, 02:02:53 AM This fraudster is selling your software : https://youtu.be/zowg-o4Fszk Thanks for informing me. The corresponding google account is banned now.Title: Re: The FinderOuter, a bitcoin recovery tool (v0.8.0 2021-03-20) Post by: Stroncow on April 05, 2021, 07:09:32 AM This fraudster is selling your software : https://youtu.be/zowg-o4Fszk Thanks for informing me. The corresponding google account is banned now.You're welcome. When searching for Base58 wif code, can you bring up a method of adding several addresses instead of one destination address? Title: Re: The FinderOuter, a bitcoin recovery tool (v0.8.0 2021-03-20) Post by: Coding Enthusiast on April 05, 2021, 05:51:11 PM When searching for Base58 wif code, can you bring up a method of adding several addresses instead of one destination address? It could be added but I don't see the point in it and here is why, the checksum in a WIF is big enough to have very little collisions when going through permutations. Most of the times with small number of missing characters (that would take reasonable time) only 1 valid key exists and as the number of missing characters grow the number of valid keys that are returned remain too small. For example with 7 missing chars at random positions worst case scenario is that you get 2 or 3 keys. It is easy for user to check all of them. If the number of missing chars is too big then recovery is most probably not possible, accepting more addresses won't change that. In any case the program is already printing any valid key it finds as it goes.BTW the Missing base58 option is not using the extra input field (ie. address/pubkey) for WIF recovery. It is just used for a special case where the missing chars are all located at the end. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.8.0 2021-03-20) Post by: Coding Enthusiast on April 06, 2021, 08:48:39 AM Version 0.9.0 is released.
https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.9.0.0 See changelog (https://github.com/Coding-Enthusiast/FinderOuter/blob/master/CHANGELOG.md) for details.
https://i.imgur.com/3ZcGxPm.jpg The KB will contain some general information about what the input is, how it is used, etc. https://i.imgur.com/uRCvyng.jpg
A good news I've made good progress on solving issue #9 (https://github.com/Coding-Enthusiast/FinderOuter/issues/9) and next release will hopefully solve it for good as we will replace BigInteger entirely with a UInt256 struct that doesn't have the same issues as BigInteger and also it adds a huge speed gain. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.9.0 2021-04-05) Post by: NotATether on April 23, 2021, 04:49:24 PM I am getting the following error when loading FinderOuter in VS2019:
Code: error : The project file cannot be opened. Unable to locate the .NET SDK. Check that it is installed and that the version specified in global.json (if any) matches the installed version. I'm clueless, because I already have .NET SDK and tools installed. Any ideas? Title: Re: The FinderOuter, a bitcoin recovery tool (v0.9.0 2021-04-05) Post by: Coding Enthusiast on April 23, 2021, 05:22:54 PM I am getting the following error when loading FinderOuter in VS2019: This is a Visual Studio related problem. Refer to SO: https://stackoverflow.com/questions/65209536/microsoft-visual-studio-2019-the-project-file-cannot-be-opened-unable-to-locatCode: error : The project file cannot be opened. Unable to locate the .NET SDK. Check that it is installed and that the version specified in global.json (if any) matches the installed version. I'm clueless, because I already have .NET SDK and tools installed. Any ideas? Title: Re: The FinderOuter, a bitcoin recovery tool (v0.10.0 2021-05-05) Post by: Coding Enthusiast on May 05, 2021, 05:59:04 AM Version 0.10.0 is released.
https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.10.0.0 See changelog (https://github.com/Coding-Enthusiast/FinderOuter/blob/master/CHANGELOG.md) for details. BigInteger Be Gone! This release introduced a new code for Elliptic Curve Cryptography that also solves issue #9. Effectively this brings a ton of optimization to almost all options, mainly the mnemonic recovery and Base16 rcovery. But also any option that required an ICompareService that used ECC. By getting rid of the old ECC code and BigInteger this also solves the pressure on garbage collector and lets FinderOuter utilize the entire CPU power during parallelism. Speed gain in this release is usually around 200% compared to previous releases. Good news is that this is the initial step for more optimization! For example the current ECC implementation uses radix 226 and contstant time operations, changing to radix 252 and using variable time operations, etc will improve the speed more. Some additional changes:
Title: Re: The FinderOuter, a bitcoin recovery tool (v0.12.1 2021-08-19) Post by: Coding Enthusiast on August 19, 2021, 03:16:28 AM Version 0.11.0 is released. https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.11.0.0 See changelog (https://github.com/Coding-Enthusiast/FinderOuter/blob/master/CHANGELOG.md) for details.
Version 0.12.0 is released. Version 0.12.1 is released.https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.12.0.0 See changelog (https://github.com/Coding-Enthusiast/FinderOuter/blob/master/CHANGELOG.md) for details.
https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.12.1.0 See changelog (https://github.com/Coding-Enthusiast/FinderOuter/blob/master/CHANGELOG.md) for details. This is a small bug fix in Missing mnemonic pass option where the first character of the founds passphrase weren't included in the final report. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.12.1 2021-08-19) Post by: wilej on October 12, 2021, 12:10:03 PM Hi!
Is it possible to pause the program when it runs? I have entered a Base58 WIF address where 8 characters are missing in the middle and now the computer runs on all 8 kernels with 100% CPU, which makes the computer almost unusable. The progress bar at the bottom stays at 0% and is not moving. The only thing I can do is to turn off a couple of cores in Task Manager to make the computer respond again, but the program still lags and I can't copy the already solved keys that are in the bottom text box as the program does not response. I do not want to shut down the program because I will lose the keys generated over the past 24 hours. Thanks in advance Willy Title: Re: The FinderOuter, a bitcoin recovery tool (v0.12.1 2021-08-19) Post by: LoyceV on October 12, 2021, 01:39:14 PM Is it possible to pause the program when it runs? I use VirtualBox (in my case for StellarCracker). It probably reduces performance a bit, but allows me to Pause the entire VM. Alternatively, I can adjust the VM's Processor Execution Cap to a lower percentage when needed.But that's for next time, it won't help you now. Quote The only thing I can do is to turn off a couple of cores in Task Manager to make the computer respond again, but the program still lags Can you adjust the priority? "Idle" seems perfect for cracking.Title: Re: The FinderOuter, a bitcoin recovery tool (v0.12.1 2021-08-19) Post by: onlixex on November 23, 2021, 01:49:06 PM I wanted to ask what character can be substituted for *. i want to try matching only uppercase and lowercase letters. is there such a possibility?
And another question I have a privatkey in it, 9 characters are lost at the beginning. After the number 5. I tried to shorten the search options. and tried to substitute other symbols for example 5KoR ******* and the search did not give any result at all. there are suspicions that not all symbols can be in places 3 and 4. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.12.1 2021-08-19) Post by: Coding Enthusiast on November 24, 2021, 04:39:01 AM I wanted to ask what character can be substituted for *. It doesn't matter but if you hold your mouse over the textbox you will see a popup showing what characters are accepted. This character will only be used to indicate the missing position and nothing else.i want to try matching only uppercase and lowercase letters. is there such a possibility? Unfortunately no.And another question I have a privatkey in it, 9 characters are lost at the beginning. After the number 5. I tried to shorten the search options. and tried to substitute other symbols for example 5KoR ******* and the search did not give any result at all. there are suspicions that not all symbols can be in places 3 and 4. The problem could be in existing characters but as far as the start goes the uncompressed keys start with 5H, 5J or 5K but the rest can be anything.Title: Re: The FinderOuter, a bitcoin recovery tool (v0.12.1 2021-08-19) Post by: PawGo on November 24, 2021, 12:47:47 PM I wanted to ask what character can be substituted for *. i want to try matching only uppercase and lowercase letters. is there such a possibility? And another question I have a privatkey in it, 9 characters are lost at the beginning. After the number 5. I tried to shorten the search options. and tried to substitute other symbols for example 5KoR ******* and the search did not give any result at all. there are suspicions that not all symbols can be in places 3 and 4. Of course not. The range is Code: 0000000000000000000000000000000000000000000000000000000000000001 Code: 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreAnchuDf 5Ko... is above the range. By the way - I invite you check also my program https://github.com/PawelGorny/WifSolver/ Maybe it will help you. But, as you said you have 9 characters missing (so WIF as I understand looks like 5?????????xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx) I think it is solvable. It could be also solved by converting your problem to another program. And additionally if you have public key (if you know address and it has outgoing transaction) could be solved in minutes ;-) Regards, Title: Re: The FinderOuter, a bitcoin recovery tool (v0.12.1 2021-08-19) Post by: Viktor-Alexander on November 24, 2021, 01:53:54 PM Can you add a decryption tool for wallets like: Electrum, Bitcoin Core etc... ?
That would be very nice. Example: I have 0.0015... BTC locked on a wallet and i can't remember what software i used. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.12.1 2021-08-19) Post by: Coding Enthusiast on November 24, 2021, 04:44:48 PM Can you add a decryption tool for wallets like: Electrum, Bitcoin Core etc... ? Wallet file encryption is a bit complicated and I haven't been able to find a good documentation I could use to implement it. So although it is in my todo list I'm not sure when I can actually implement it specially nowadays that I'm very busy, sadly.That would be very nice. Example: I have 0.0015... BTC locked on a wallet and i can't remember what software i used. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.12.1 2021-08-19) Post by: onlixex on November 24, 2021, 06:07:45 PM Thanks for answers. I will wait for the possibility of GPU matching.
unfortunately there were no outgoing transactions. the address is known. But there is no certainty. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.12.1 2021-08-19) Post by: onlixex on November 24, 2021, 08:30:47 PM I wanted to ask what character can be substituted for *. i want to try matching only uppercase and lowercase letters. is there such a possibility? And another question I have a privatkey in it, 9 characters are lost at the beginning. After the number 5. I tried to shorten the search options. and tried to substitute other symbols for example 5KoR ******* and the search did not give any result at all. there are suspicions that not all symbols can be in places 3 and 4. Of course not. The range is Code: 0000000000000000000000000000000000000000000000000000000000000001 Code: 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreAnchuDf 5Ko... is above the range. By the way - I invite you check also my program https://github.com/PawelGorny/WifSolver/ Maybe it will help you. But, as you said you have 9 characters missing (so WIF as I understand looks like 5?????????xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx) I think it is solvable. It could be also solved by converting your problem to another program. And additionally if you have public key (if you know address and it has outgoing transaction) could be solved in minutes ;-) Regards, Send email to you Title: Re: The FinderOuter, a bitcoin recovery tool (v0.13.0 2022-02-02) Post by: Coding Enthusiast on February 02, 2022, 09:15:47 AM Version 0.13.0 is released.
https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.13.0.0
A new RoadMap is also added to show what the plans are for the future. It will be updated on GitHub: https://github.com/Coding-Enthusiast/FinderOuter/issues/47 Title: Re: The FinderOuter, a bitcoin recovery tool (v0.13.0 2022-02-02) Post by: Coding Enthusiast on March 07, 2022, 01:02:02 PM Version 0.14.0 is released.
https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.14.0.0
Title: Re: The FinderOuter, a bitcoin recovery tool (v0.15.0 2022-05-19) Post by: Coding Enthusiast on May 20, 2022, 11:57:12 AM Version 0.15.0 is released.
https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.15.0.0
This release comes with a brand new feature to let you decrease the number of permutations. Lets say you have a mnemonic missing two words and you know the first word starts with letters "th". All you have to do is expand the Advanced option and click start so that FinderOuter can perform an initial analysis on your inputs and prepares the requires lists. Then enter letters "th" in the textbox and choose "Words starting with" button. As you can see in the screenshot below the list is automatically filled with any words from the selected wordlist that start with "th". You can also see the total number of items in your list. You can continue adding or removing items from this list until you are satisfied with the list and move on to the next missing item by clicking the next button ('>'). Repeat the same and when you are done setting all items click Find. https://i.imgur.com/fPZG4vO.jpg Title: Re: The FinderOuter, a bitcoin recovery tool (v0.15.0 2022-05-19) Post by: LoyceV on June 26, 2022, 10:35:05 AM I just noticed FinderOuter crashes when I search for Missing Base58 and enter a complete private key (52 characters, starting with L).
When I change the last character into a *, it works and gives 4 different address formats. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.15.0 2022-05-19) Post by: Coding Enthusiast on June 27, 2022, 11:56:48 AM I just noticed FinderOuter crashes when I search for Missing Base58 and enter a complete private key (52 characters, starting with L). Thanks for reporting this bug.When I change the last character into a *, it works and gives 4 different address formats. The recent SearchSpace feature introduced some bugs, inputs with no missing items is among them. I've already fixed and pushed the changes to the repository but haven't published the new binaries yet. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.16.0 2022-09-19) Post by: Coding Enthusiast on September 19, 2022, 10:27:12 AM It's been a rough couple of months but I finally managed to release the next version.
Version 0.16.0 is released. https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.16.0.0
The process is same as search spaces for missing characters. You fill the text boxes and then click the Start button to instantiate the arrays. After that, all it takes is adding characters or words for each item in the passphrase. For example if you have 3 word passphrase and you think the second word can be "was", "is", "Is" or a symbol like "!" or "@" is set like this: https://i.imgur.com/EapfoSV.jpg There is also an Open button (far right side) that can be used to read a .txt file containing a list of possible items in the passphrase (one item per line) that can be a word, a symbol or a full sentence. This list can be used by the Add all button. As before, FinderOuter is still using CPU only and brute forcing BIP38 is extremely slow this way. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.16.0 2022-09-19) Post by: Tofee on December 11, 2022, 08:47:10 PM Hi there, please let me know the commands required to install on Ubuntu/Debian OS after unzip, from Finderouter-master folder. Thanks
Title: Re: The FinderOuter, a bitcoin recovery tool (v0.16.0 2022-09-19) Post by: Coding Enthusiast on December 22, 2022, 05:59:35 AM Hi there, please let me know the commands required to install on Ubuntu/Debian OS after unzip, from Finderouter-master folder. Thanks Everything is already explained in ReadMe file. If you have the source code and want to compile Step 2 (https://github.com/Coding-Enthusiast/FinderOuter#step-2-download-and-build) or Step 3 (https://github.com/Coding-Enthusiast/FinderOuter#step-3-run) if you have the complied binaries and want to run.Title: Re: The FinderOuter, a bitcoin recovery tool (v0.16.0 2022-09-19) Post by: digaran on January 25, 2023, 12:35:08 PM Hi there, is there any ETR( expected time of release) on GPU supported version?
Title: Re: The FinderOuter, a bitcoin recovery tool (v0.16.0 2022-09-19) Post by: Coding Enthusiast on February 28, 2023, 07:32:02 AM We are heading for the first stable version (v 1.0) by fixing as many little bugs as possible and improving the code in general. Since that may take a while I'll try to publish more beta versions that act as pre-releases to 1.0 from now on. As always follow the roadmap (https://github.com/Coding-Enthusiast/FinderOuter/issues/47) to see updates on when new features like GPU support could be added.
Here is version 0.17.0 with lots of little improvements: Version 0.17.0 (2023-02-27) https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.17.0.0
PS. FinderOuter is 3 years old :) Title: Re: The FinderOuter, a bitcoin recovery tool (v0.17.0 2023-02-27) Post by: digaran on February 28, 2023, 02:28:31 PM Oh hello dear dev, it seems GPU support is at the end of your roadmap. Anyway, since you know some expert stuff about coding, I was wondering how much could it cost if we were trying to create a database of addresses like this for example:
Code: 1111111111111111111114oLvT2 Could you give me a price and time estimate please? Title: Re: The FinderOuter, a bitcoin recovery tool (v0.17.0 2023-02-27) Post by: Coding Enthusiast on March 01, 2023, 11:39:56 AM Could you give me a price and time estimate please? I'd say roughly 1-2 hundred millions of addresses can be encoded sequentially this way per second per core. Although since we are talking about 10160 addresses, the size is going to be massive and won't fit in any memory or storage space.Title: Re: The FinderOuter, a bitcoin recovery tool (v0.17.0 2023-02-27) Post by: digaran on March 03, 2023, 08:34:07 PM Some suggestions, it would be nice to have the ability to do SHA256 RIPEMD160, HASH-160, convert private key to u/compressed public keys, convert WIF to private key and vice versa, base58 checksum decode/ encode. Converting public keys to addresses, converting address to RIPEMD160, vice versa.
Basically manual key generator etc, It's hard to use several online tools for just computing a bitcoin address. Also having a windows compiled version would be greatly appreciated. I know that I might sound too demanding, but these are just suggestions. ~Regards. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.17.0 2023-02-27) Post by: Coding Enthusiast on March 08, 2023, 05:54:46 AM Also having a windows compiled version would be greatly appreciated. Under releases on GitHub there is always a zip file containing the binaries for Windows.https://github.com/Coding-Enthusiast/FinderOuter/releases/download/v0.17.0.0/FinderOuter-0.17.0.0-Win64SCD.zip As for your other suggestions, manual key generation doesn't really fit into a "recovery tool" so it can't be added to FinderOuter. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.17.0 2023-02-27) Post by: despo4helpo on March 25, 2023, 05:39:20 AM Hello.
I'm trying to find my passphrase. I have the 24 word seed phrase. Where can I enter the (presumed) words known for the passphrase? If I try in Customchars, it says to remove duplicate letters. What's the maximum number of allowed characters in the passphrase? It says 100 is too much. I don't think my passphrase is 100 but I put that since it's the maximum a Ledger will allow, which is what I used. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.17.0 2023-02-27) Post by: LoyceV on March 25, 2023, 08:53:50 AM What's the maximum number of allowed characters in the passphrase? It says 100 is too much. I don't think my passphrase is 100 but I put that since it's the maximum a Ledger will allow, which is what I used. Brute-forcing 100 characters will never ever succeed. You'll probably have a very hard time with 10 characters already, if your password is that long your only chance is to remember (most of) it.Title: Re: The FinderOuter, a bitcoin recovery tool (v0.17.0 2023-02-27) Post by: despo4helpo on March 26, 2023, 02:40:12 AM What's the maximum number of allowed characters in the passphrase? It says 100 is too much. I don't think my passphrase is 100 but I put that since it's the maximum a Ledger will allow, which is what I used. Brute-forcing 100 characters will never ever succeed. You'll probably have a very hard time with 10 characters already, if your password is that long your only chance is to remember (most of) it.If I do remember most of it, where do I enter that data in FinderOuter? Title: Re: The FinderOuter, a bitcoin recovery tool (v0.18.0 2023-06-23) Post by: Coding Enthusiast on June 24, 2023, 04:08:57 PM Version 0.18.0 (2023-06-23)
https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.18.0.0
[1] This will show the number of keys that were checked so far and an estimated speed in number of keys(permutations) per second and the estimated time remaining until the entire search space is checked. Note that in most cases the actual key could be found before the entire space is searched. See issue #30 for information on its limits. https://i.ibb.co/rMCKPMR/000-speed.jpg [2] When modifying the mnemonic search-space by entering possible words, user can switch to the Auto Complete mode so that a suggestion list opens up based on the letters that were entered so far. This should also make it easier to see all words that contain certain letters (like the image below with words containing "xi"). Mode can change any time using the switch button. https://i.ibb.co/tPwf0VR/000-auto-comp.jpg Title: Re: The FinderOuter, a bitcoin recovery tool (v0.18.0 2023-06-23) Post by: PawGo on June 28, 2023, 01:04:44 PM It becomes a really huge machine! Do you have any plans for the next release(s)?
Saving progress and restoring partial search? Using a range in derivation path? I was briefly comparing what you have with features of 'lostword' and looks like you have (almost) all :) Title: Re: The FinderOuter, a bitcoin recovery tool (v0.18.0 2023-06-23) Post by: Coding Enthusiast on June 29, 2023, 03:50:11 PM It becomes a really huge machine! Do you have any plans for the next release(s)? For now until version 1.0 I'm focusing on increasing my test coverage and finding bugs while improving the printed reports and messages.Saving progress and restoring partial search? Using a range in derivation path? I was briefly comparing what you have with features of 'lostword' and looks like you have (almost) all :) After that I'll start investigating how to add GPU support. Anything else I'll try to squeeze in if I have any idea of how to implement them efficiently without needing any significant code change. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.18.0 2023-06-23) Post by: digaran on June 29, 2023, 07:58:59 PM Hi dev, a suggestion : could you make it so the user could select how many threads to be used? Since it uses everything a CPU can offer, usually it just hangs if the load is too much, unless you go to task manager on windows and limit CPU usage, but having an option to set one time and the ability to save the user settings would be great.
Title: Re: The FinderOuter, a bitcoin recovery tool (v0.18.0 2023-06-23) Post by: Coding Enthusiast on July 12, 2023, 05:01:08 AM Hi dev, a suggestion : could you make it so the user could select how many threads to be used? Since it uses everything a CPU can offer, usually it just hangs if the load is too much, unless you go to task manager on windows and limit CPU usage, but having an option to set one time and the ability to save the user settings would be great. https://github.com/Coding-Enthusiast/FinderOuter/commit/09466f3e9fe2b57fa158c1f61add98e15cb6973dThis was added under an expander on the side with the name "Settings" that will allow you to set the number of threads the parallel loops use based on the number of cores .net can detect. The max value here may not be accurate in case the system has more than one processor group or has CPU utilization limit. I'll probably add an override option to go beyond that limit as a more advanced feature since going beyond the thread limit could potentially slow down the process. This also needs some guides on how it should be used etc. in our KnowledgeBase page which I'll add before v0.19.0 is released. https://i.ibb.co/nbDTg5k/threard-count.jpg PS. If you build at the given commit above, know that there is currently a bug in our UI where the slider appears to be at the minimum value (1) when the application starts but the actual value is set correctly to the maximum number of threads. This is fixed in the new AvaloniaUI 11.0 which we need to upgrade to but it takes time due to the breaking changes in the UI framework. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.18.0 2023-06-23) Post by: Viko19 on September 15, 2023, 12:22:52 PM Hi dev, a suggestion : could you make it so the user could select how many threads to be used? Since it uses everything a CPU can offer, usually it just hangs if the load is too much, unless you go to task manager on windows and limit CPU usage, but having an option to set one time and the ability to save the user settings would be great. https://github.com/Coding-Enthusiast/FinderOuter/commit/09466f3e9fe2b57fa158c1f61add98e15cb6973dThis was added under an expander on the side with the name "Settings" that will allow you to set the number of threads the parallel loops use based on the number of cores .net can detect. The max value here may not be accurate in case the system has more than one processor group or has CPU utilization limit. I'll probably add an override option to go beyond that limit as a more advanced feature since going beyond the thread limit could potentially slow down the process. This also needs some guides on how it should be used etc. in our KnowledgeBase page which I'll add before v0.19.0 is released. https://i.ibb.co/nbDTg5k/threard-count.jpg PS. If you build at the given commit above, know that there is currently a bug in our UI where the slider appears to be at the minimum value (1) when the application starts but the actual value is set correctly to the maximum number of threads. This is fixed in the new AvaloniaUI 11.0 which we need to upgrade to but it takes time due to the breaking changes in the UI framework. Hi, need to find private key for bitcoin wallet. Part of this key is 35 characters, I know how to find other characters, is there a program for sorting characters with an indication of mandatory ones. I would appreciate a tip on the bitcoin part Title: Re: The FinderOuter, a bitcoin recovery tool (v0.18.0 2023-06-23) Post by: Coding Enthusiast on November 15, 2023, 06:32:50 AM Version 0.19.0 (2023-11-15)
https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.19.0.0
Two major changes in this release are migration to the new Avalonia UI version 11.0 and .Net 6 with trimming option that reduces the binary size by roughly 40%. Even though most UI bugs were fixed before releasing v0.19 there may still be some uncaught ones, please report them on GitHub (or here) if you encounter any. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.19.1 2024-01-24) Post by: Coding Enthusiast on January 24, 2024, 06:59:58 AM Version 0.19.1 (2024-01-24)
https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.19.1.0
This minor release is fixing a critical bug but also moves to the new .net 8 which required changing UI bindings to compiled binding to prevent UI code from being trimmed. This also further decreases the binary sizes (~8%). The backend (Bitcoin.Net) is also updated to 0.26.0 with improvements and bug fixes in ECC implementation which should also bring some small optimization. Title: Re: The FinderOuter, a bitcoin recovery tool (v0.19.1 2024-01-24) Post by: Tofee on February 07, 2024, 09:42:45 PM I have a private key with 11 character’s missing from 3 to 6, 25 to 27 and 48 to 51. I understand that last four characters are the checksum. I tried FinderOuter but it’s taking more than a month and gives more than 100 private keys. I do not which software I can use to locate the correct private key. Any advice, please let me know.
Title: Re: The FinderOuter, a bitcoin recovery tool (v0.19.1 2024-01-24) Post by: LoyceV on February 13, 2024, 06:55:56 PM I tried FinderOuter but it’s taking more than a month and gives more than 100 private keys. This is weird. With 11 missing characters, I'd expect millions of valid private keys. If you know the address, you should know which one you need. But if you don't know the address, you should have many more private keys.Anyway, with just 100 private keys, you could even import them into a new Electrum wallet to see if any of them have transactions. See this post (https://bitcointalk.org/index.php?topic=3383265.msg35449672#msg35449672) to restore Segwit addresses. |
