profanity icon indicating copy to clipboard operation
profanity copied to clipboard

Private key not matches address on macOS

Open k06a opened this issue 5 years ago • 3 comments

./profanity.x64 --leading 0
Mode: leading
Target: Address
Devices:
  GPU0: Intel(R) UHD Graphics 630, 1610612736 bytes available, 24 compute units (precompiled = no)
  GPU1: AMD Radeon Pro 5500M Compute Engine, 4278190080 bytes available, 24 compute units (precompiled = no)

Initializing OpenCL...
  Creating context...OK
  Compiling kernel...OK
  Building program...OK
  Saving program...OK

Initializing devices...
  This should take less than a minute. The number of objects initialized on each
  device is equal to inverse-size * inverse-multiple. To lower
  initialization time (and memory footprint) I suggest lowering the
  inverse-multiple first. You can do this via the -I switch. Do note that
  this might negatively impact your performance.

  GPU1 initialized
  GPU0 initialized

Initialization time: 98 seconds
Running...
  Always verify that a private key generated by this program corresponds to the
  public key printed by importing it to a wallet of your choice. This program
  like any software might contain bugs and it does by design cut corners to
  improve overall performance.

  Time:    99s Score:  5 Private: 0x89f61b1ec4eb6f10febc6b60bc4d6ad9fd92bb6b34b0928eb3bc6ed0a754c7c3 Address: 0x0000040330a2a2d9ac73363c253d61e2cbfe23f5
  Time:    99s Score:  6 Private: 0x2a5287598ee65bb33b4db28aadf26b4122e94de11d6d2e26c8018821832720eb Address: 0x000000a5714ec98568c661e2be88eb789b007c18
  Time:   109s Score:  7 Private: 0x2a5287598f0f46b53b4db28aadf26b4122e94de11d6d2e26c80188218327216d Address: 0x00000003ae1d96d6b8a6801532e6942ea9fd0cb7
^Ctal: 39.783 MH/s - GPU0: 4.689 MH/s GPU1: 35.094 MH/s

But it seems these private keys are not matching vanity addresses.

k06a avatar Apr 29 '20 20:04 k06a

Only first PrivateKey works!

k06a avatar Apr 30 '20 07:04 k06a

@k06a Did you ever find a solution or workaround for this? This seems to be the case for me as well, where private keys do not derive to the addresses shown

mds1 avatar Mar 03 '22 16:03 mds1

Think I figured it out: I also have both an Intel and AMD GPU on my mac, and the AMD one seems to be the problem. If I run profanity with just the AMD GPU, keys do not match, and if I run it with just the Intel GPU, keys match

mds1 avatar Mar 03 '22 19:03 mds1