Invalid keys generated by GPUs

[DefiDebauchery]

Continuing the discussion from #2 --

I was indeed able to generate a valid address using my M1 Mac, which I understand had been the majority of the changes in Profanity2. However, GPU support is still an important aspect of this tool, and I'm consistently getting keys that don't match through my environment (Ubuntu 18.02 with Vega 56 GPU(s))

Unfortunately, I admittedly don't know C++, so I'm not sure what direct help I can be, but would be open to testing any potential changes.

[k06a]

@DefiDebauchery try one more time. If you did no mistakes - this issue should occur very rare.

[DefiDebauchery]

Okay. With the most recent update, this appears to be fixed.

Pardon my naive question, but do you think there would be any way to generate the proper account with the keys provided by the previous build?

[k06a]

@DefiDebauchery I believe I didn’t changed any logic, it was about dependencies.

[slavik0329]

On my M1 every key generated by this script does not correlate to the address

[k06a]

@slavik0329 did you sum private keys correctly?

[slavik0329]

@k06a That was it 😅 Thanks!