NICE WORK!!! :)

[trextrader]

By far probably the easiest github source I have ever cloned to get up and running in seconds! I am not sure I understand the output however, as it looks like a private-key-hex, yet its in an invalid format and it looks like its html so I have both a question and a suggestion:

The question: What precisely was output ad I will be more than happy to send you 10% of a rather large btc wallet I have owned since 2010 and my ex-fiance before she left accidentally threw away the private keys I had printed for this and reversal others. The others are minimal by comparison to my primary wallet and it looks like it output something that looks like a private key hex(???) 10% is of the second order of magnitude 10^2 - worth taking some time to help me resolve this if it did in fact resolve my old private key for this wallet you deserve it!

The suggestioon: If you could output a table and label the table of precisely what each string represents, so effectively, merge matja/Bitcoin tool in to your code-base such that the output file or print to screen looks like this:

address.hex:000511096ab078473911e0222fcbc3375314e2bab1
address.base58:156T6Af12SKCQGbjEWNeTkADhJNk
address.base58check:1TnnhMEgic5g4ttrCQyDopwqTs4hheuNZ
public-key-ripemd160.hex:0511096ab078473911e0222fcbc3375314e2bab1
public-key-ripemd160.base58:56T6Af12SKCQGbjEWNeTkADhJNk
public-key-ripemd160.base58check:TnnhMEgic5g4ttrCQyDopwqTs4k6XbAK
public-key-sha256.hex:b17978b7528353483429a758fb9ec833882a5ddbb27c1fc2bb4a66436f7e342f
public-key-sha256.base58:CwnbNMmu9yCkXE32543pfPAgVSynE2wjGYv9Mip4yrb8
public-key-sha256.base58check:2MAMBCve8eVyrbxxBzqn5HLNqqyc8CysKPdfaKPzA81mHxPvyu
public-key.hex:04a32ed011213146495f58d3ed83a6cc3fc0fd107d5fa2887bbc2fcea81e8bc84f650e81f4ddc84424daab546945f0d7d9dfd4dce39ce3776ee6b8ba78e6eddc7a
public-key.base58:QjfX2h4LdAA21NTa2K5dVcxcuQVTtvT3dL5JFLvxAMuCGKY3t8yCKNzJid8MHWbYmoHSRXAS9hggkhQUDiwaaGAV
public-key.base58check:3gKQTqtZhdBHDDe1echja7ac39tup3SnNSzwZSrnHb417QbL7T8JcTfW7GgEQsvhYrPqLsiraabne6xDrSGZ6bBB4S5YGM
private-key-wif.hex:8030caae2fcb7c34ecadfddc45e0a27e9103bd7cfc87730d7818cc096b1266a683
private-key-wif.base58:f5g1GA5uH4gsfEU6ANnGCzoe1VZvnZ1mYh3frnVSPR1nJ
private-key-wif.base58check:5JBmuBc64pVrKLyDc8ktyXJmAeEwKQogn6jsk6taeq8zRMtGZrE
private-key.hex:30caae2fcb7c34ecadfddc45e0a27e9103bd7cfc87730d7818cc096b1266a683
private-key.base58:4HTpd7gVSeVJDurhJKYGEYyFWMZRCNjSnXaEcan9K6Gz
private-key.base58check:NVKW9zzMvs4LawZwJztUZdx3R27Gwc4Hg6WvqqQxHMFkbn3Wz

Instead of a random alpha-numeric string that I cannot seem to figure out what precisely that output is, its close...look at the private-key-hex above (labeled and in bold) - 2 more characters of your output and if it started with a 5 followed by a capital letter, now we are talking about useful output, labeled, so there is no possibility of anyone being clueless...

In general, this would be the ideal system:

1. Select real-time scanner or static offline computation
2. In this case, its an offline computation being fed several transactions including r,s,z values, the raw transactions, the TXID's for each transaction...alot of hashes as it goes into the computation engine. Also adding rapid search of like nonces either via json in real-time updating every second or Freq. is user definable as a cmd line arg, find like r and/or k values, immediately invoke the computation to push out the private key, otherwise continue to use algo you are using to crack with.
3. Output a table like above, or not even as much information as that just the private key compressed, uncompressed, public key compressed uncompressed, and do a quick balance check to output the balance to ensure that it is the wallet, and BINGO! Why on Earth has nobody done this it seems as if everyone has a piece here and there but nobody has ever really put something that is the master integration of algos - input .dat, hashes file, base58 addresses, ripemd160 addresses, etc whatever and pop it in the oven, set the timer for the GPU computation or multi-threaded CPU or better a combination of both for maximum efficiency and lighting fast computations, and anyone needing to recover their BTC can do so with ease instead of this dancing on a bed of coals jumping from one software package to another which is just insanity.

Literally, it does not even have to be UI driven, cmd would look like this .recover -input file1 file2 filen -output Fileo
where file1...filen can be of different types, invoking multiple algos together and use the power of convergence to rapidly compute the private key, output as WIF, user copy pastes wif into client wallet software, and DONE!

Why does this not exist? It seems it would not be very difficult to do...if I did not have children and many other things on my plate by merging code bases and a little clever coding no doubt this could be done in under 1 to 2 months max by a solo developer then offer it to the world for free and let people actually recover from substantial losses...dev takes 10% and becomes the richest person in the world rather fast! :) [and i take x% for giving everyone the obvious idea which I find it rather amusing this shuffle game - simplicity is always better for the end-user, nightmare for the devs, but in this case, not so much of a nightmare for a dev...I wish I had the time I would do it myself...

Cheers!

/Zap