The FinderOuter, a bitcoin recovery tool (v0.19.1 2024-01-24)

[Stroncow]

This fraudster is selling your software : https://youtu.be/zowg-o4Fszk

[1713931621]

1713931621

[1713931621]

1713931621

[Coding Enthusiast]

This fraudster is selling your software : https://youtu.be/zowg-o4Fszk

Thanks for informing me. The corresponding google account is banned now.

[Stroncow]

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?

[Coding Enthusiast]

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.

[Coding Enthusiast]

Version 0.9.0 is released.
https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.9.0.0
See changelog for details.

• New recovery option: find encoding of an arbitrary input string
  
  
• Add a new help view that shows up at startup and suggests which recovery option to choose

• Add knowledge Base window that contains explanation of different parts

There are small question marks on different UI objects that can be clicked to move to the respective KB

The KB will contain some general information about what the input is, how it is used, etc.

• Some small improvements in address validation and error message

A good news
I've made good progress on solving issue #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.

[NotATether]

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?

[Coding Enthusiast]

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?

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-locat

[Coding Enthusiast]

Version 0.10.0 is released.
https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.10.0.0
See changelog 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 2²⁶ and contstant time operations, changing to radix 2⁵² and using variable time operations, etc
will improve the speed more. 

Some additional changes:

• Path recovery can now accept any extended keys (xprv, ypub, zprv, ?pub, ...)
• It is now possible to recover a WIF missing up to 11 characters from the end
• Reports generated by MissingEncoding option are improved
• Various code improvements and tests
• From this version we are also releasing binaries for 3 operating systems (Linux, Windows and MacOs all x64)

[Coding Enthusiast]

Version 0.11.0 is released.
https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.11.0.0
See changelog for details.

• All hash algorithms are static and their arrays are allocated on the stack
• Added more hard-coded derivation paths for BIP-32 path recovery option
• Base58 algorithm for WIFs is reworked to increase the recovery speed up to 2.5x
• Two new special cases are added to WIF recovery for missing 1 and 2 characters at unknown locations
• Some code cleanup and additional tests

Version 0.12.0 is released.
https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.12.0.0
See changelog for details.

• New recovery option: recovering mnemonic (BIP39, Electrum) passphrase
  
• Report is improved to handle timer, progress and give a more accurate key/sec speed
  
• Mnemonic recovery option will return a better report when the input is not missing any words
• Small bug fix, code improvement and some tests

Version 0.12.1 is released.
https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.12.1.0
See changelog 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.

[wilej]

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

[LoyceV]

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.

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.

[onlixex]

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.

[Coding Enthusiast]

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.

[PawGo]

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
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140

which produces range of WIF (uncompressed):

Code:

5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreAnchuDf
5Km2kuu7vtFDPpxywn4u3NLpbr5jKpTB3jsuDU2KYEqetqj84qw

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,

[Viktor-Alexander]

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.

[Coding Enthusiast]

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.

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.

[onlixex]

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.

[onlixex]

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
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140

which produces range of WIF (uncompressed):

Code:

5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreAnchuDf
5Km2kuu7vtFDPpxywn4u3NLpbr5jKpTB3jsuDU2KYEqetqj84qw

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

[Coding Enthusiast]

Version 0.13.0 is released.
https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.13.0.0

• New recovery option: recovering BIP38 passwords
  
• Passwords can now include space
• Password recovery options (BIP38 and BIP39) can now accept a custom set of characters
• Base58 recovery of WIFs with unknown missing char position updates progress bar now
• Small bug fix, optimization and tests

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

[Coding Enthusiast]

Version 0.14.0 is released.
https://github.com/Coding-Enthusiast/FinderOuter/releases/tag/v0.14.0.0

• Added the EC mult encryption mode to BIP38 password recovery option
• KnowledgeBase is slightly improved
• Old ECC code is removed
• General code improvements and cleanup
• Some small optimization
• Small UI improvements