Private keys not matching address about profanity2 HOT 4 CLOSED

@sniperbnb could you provide example with non-real private key?

from profanity2.

yes, just tested again right now.

./profanity2.x64 -z 41f980b05d9c479c8564b6cdcb6609d99d90b9f4339c4d7823b35d479eb6a9f4e1d71228f695676758b0e1f60f7a1052bc64911d4963defaeb2e9e1defe3cf28 --leading 0

Mode: leading
Target: Address
Devices:
GPU0: Apple M1, 5726633984 bytes available, 8 compute units (precompiled = no)

Time: 35s Score: 5 Private: 0x000090c20d4856172ab0039bfe16cf16395979c0873cb5fe5c4df184862751d0 Address: 0x000009671b1057aff95e9cd05116071a05a70183
Time: 36s Score: 6 Private: 0x000090c20d4b07472ab0039bfe16cf16395979c0873cb5fe5c4df184862751d3 Address: 0x000000b240a90ff6c886f8ea42635b6daecad697
Time: 40s Score: 7 Private: 0x000090c20d4c05742ab0039bfe16cf16395979c0873cb5fe5c4df184862751fb Address: 0x0000000225fea3c5599f325d970d6f5e7b6d6a1b

none matching
@k06a

from profanity2.

@sniperbnb did you added found private keys to original private key of public key you provided with -z parameter? Those are partial private keys (actually they are offsets for your initial private key)

from profanity2.

edit: understood thank you

from profanity2.