Finding public keys

[adminnu]

Very much would not prevent the functionality of searching only public keys, without converting them to addresses. This is not a complex functional, as it will only require checking before sha256 and ripemd160 hashing occurs. I tried simply to comment on the conversion execution block in KeyFinder::verifyKey and further verification, putting the test always returns false, but after initialization, the verification of these points begins and after nothing changes, gpu ceases to be used. Cpu does something actively.

[brichard19]

Hi,

What is your use case for searching for only public keys? If you know of public keys with short private keys, then there is an even quicker method to find the private-key than brute force.

Let me know what your use case is, then maybe I can implement something for you.

Thanks

[adminnu]

Applicant searching for lost wallets, whose owners have saved the public key. There are no other methods, only brute force, according to the chosen ranges.

[brichard19]

Hi,

The problem is if the wallet was generated correctly (fully random 256-bit private key), then there is no way to recover the private key. The range of keys needs to be smaller if a brute-force search is going to succeed.

[adminnu]

Hi,

I'm looking for a solution to reduce the range. Now, until a solution is found, I consider the search option on large ranges, but with a large number of public keys, which also increases the chance of finding. As it is possible, I will try to use algorithms such as a giant step, a child's step and a half-lord. I read that people found in a small range with the first algorithm 55 a private key puzzle in 30 seconds, using a single CPU core. It even became interesting to me to remove hashing, what speed your application could develop in the search of only public keys.

[bill32767]

BTC ADDRESS: 1LzhS3k3e9Ub8i2W1V8xQFdB8n2MYCHPCa PUB KEY: 0385a30d8413af4f8f9e6312400f2d194fe14f02e719b24c3f83bf1fd233a8f963 PK HEX RANGE: 2 ^ 55-2 ^ 56 36028797018963968 - 72057594037927936

Please help me with the private key (in hex) of the above, [FOR ADDRESS NUMBER 55 IN THE PUZZLE] thanks.

On Sun, Sep 2, 2018 at 4:17 PM brichard19 notifications@github.com wrote:

Hi,

What is your use case for searching for only public keys? If you know of public keys with short private keys, then there is an even quicker method to find the private-key than brute force.

Let me know what your use case is, then maybe I can implement something for you.

Thanks

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/brichard19/BitCrack/issues/28#issuecomment-417966700, or mute the thread https://github.com/notifications/unsubscribe-auth/Ae0S2SVxgOvI81ps2ey2ZSgfEF8txUGWks5uXGb3gaJpZM4WWlX4 .