You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+10-2Lines changed: 10 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,13 +13,21 @@ Thanks to [.Net core](https://github.com/dotnet/core) and [AvaloniaUI](https://g
13
13
User can enter a message signature (currently only for bitcoin) 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.
14
14
15
15
#### 2. Missing Base-58 characters
16
-
This option helps those who have a damaged paper wallet with the base-58 encoded private key (WIF) missing a couple of characters. It currently only supports private keys but in the future more string types such as master private key (xprv...) will be added.
16
+
This option helps those who have a damaged paper wallet with the base-58 encoded private key (WIF) missing a couple of characters. It currently only supports private keys but in the future more string types such as master private key (xprv...) will be added.
17
+
This also supports a "special case" where a compressed private key is missing 3 characters at unknown positions.
18
+
19
+
#### 3. Missing Base-16 characters
20
+
This option is similar to previous feature but works for base-16 (hexadecimal) private keys. It currently requires an address
21
+
and only checks compressed public keys. Unlike the other options, this one is very slow since it depens on ECC and that is not
22
+
yet optimized.
17
23
18
24
## Future plans
19
25
* Optimization is always at the top of the to-do list
20
26
* Mnemonic recovery (seed phrases missing a couple of words, having wrong order,...)
21
27
* BIP-32 path finder (user has master key and at least one child key but doesn't know the derivation path)
22
28
* Password recovery (user knows some parts of his password but not all and has the encrypted wallet file)
* Converting versioned WIFs to regular WIFs (BIP-178 and early vertion 3 Electrum wallets)
23
31
24
32
## Downloading
25
33
Compiled binaries of each version can be found under [releases](https://github.com/Coding-Enthusiast/FinderOuter/releases)<sup>1</sup>. There will only be self-contained deployment targetting 64-bit Linux operating systems. There is two main reasons for this decision:
@@ -33,7 +41,7 @@ download the last two files if you are looking for compiled version.
33
41
34
42
## Build from source code
35
43
1. Get Git: https://git-scm.com/downloads
36
-
2. Get .NET Core 3.0 SDK: https://www.microsoft.com/net/download (see `TargetFramework`[here](https://github.com/Coding-Enthusiast/FinderOuter/blob/master/Src/FinderOuter/FinderOuter.csproj))
44
+
2. Get .NET Core 3.1 SDK: https://www.microsoft.com/net/download (see `TargetFramework`[here](https://github.com/Coding-Enthusiast/FinderOuter/blob/master/Src/FinderOuter/FinderOuter.csproj))
0 commit comments