Ninjastic
PostEdited versionsQuotes to this post
Post
Topic
Board Development & Technical Discussion
Re: BitCrack - A tool for brute-forcing private keys
by
almightyruler
on 19/05/2019, 04:25:53 UTC
Quote from: Trancefan on May 18, 2019, 11:39:51 PM
Why do I get two different private keys for the same BTC address?

[2019-05-18.18:30:34] [Info] Address:     1KWj99Jwd9LGGC2Y1c9c4cmvWvYTQrLFVc
                             Private key: 0000000000000000000000000000000000000000000000000000000220082201
                             Compressed:  no
                             Public key:
                             6A245BF6DC698504C89A20CFDED60853152B695336C28063B61C65CBD269E6B4
                             E022CF42C2BD4A708B3F5126F16A24AD8B33BA48D0423B6EFD5E6348100D8A82


[2019-05-18.18:16:37] [Info] Address:     1KWj99Jwd9LGGC2Y1c9c4cmvWvYTQrLFVc
                             Private key: 000000000000000000000000000000000000000000000000000000000000001F
                             Compressed:  no
                             Public key:
                             6A245BF6DC698504C89A20CFDED60853152B695336C28063B61C65CBD269E6B4
                             E022CF42C2BD4A708B3F5126F16A24AD8B33BA48D0423B6EFD5E6348100D8A82

Something strange going on there. Using Brainflayer, I see those two keys generate completely different addresses:

cb11810873f23140fba2c0d6715315fac23ebbab:u:(hex)priv:000000000000000000000000000000000000000000000000000000000000001F (1KWj99Jwd9LGGC2Y1c9c4cmvWvYTQrLFVc)
2fbd32c8dd59ee7c17e66cb6ebea7e9846c3040f:c:(hex)priv:000000000000000000000000000000000000000000000000000000000000001F (15MRQkVBF9crVPeHDjSEVEytCTVLJVGZSr)

f1c48962e20933c35cdcd4f9328fcd8ab587520b:u:(hex)priv:0000000000000000000000000000000000000000000000000000000220082201 (1P3MHqc6mWZvaaTE6WToE7mZ4gympSTYKd)
ce7355919e7ac1b58e9493700f42bc14032183b6:c:(hex)priv:0000000000000000000000000000000000000000000000000000000220082201 (1KpcN5j4Gpyd41Zy5gxtwDmmXArnWdUVdd)

(I have included both compressed and uncompressed keys for completeness.)

Note your output also provides the same public key, despite the private keys being drastically different. 1KWj99Jwd9LGGC2Y1c9c4cmvWvYTQrLFVc is the correct address associated with public key 6A245BF6DC698504C89A20CFDED60853152B695336C28063B61C65CBD269E6B4E022CF42C2BD4A7 08B3F5126F16A24AD8B33BA48D0423B6EFD5E6348100D8A82.