Skip to content
This repository has been archived by the owner on Sep 15, 2022. It is now read-only.

Generating not correct privatekeys on MacBook #39

Open
gkucmierz opened this issue Feb 19, 2021 · 1 comment
Open

Generating not correct privatekeys on MacBook #39

gkucmierz opened this issue Feb 19, 2021 · 1 comment

Comments

@gkucmierz
Copy link 

  Time:    29s Score:  5 Private: 0x3729ecb8967a1c2d24ad6a40cddba81fbc052e7478c28f156e580a6dd7f6e99f Address: 0x00000e364391609e72d61305631147f117350c1b
  Time:    30s Score:  7 Private: 0x3729ecb896a5548c24ad6a40cddba81fbc052e7478c28f156e580a6dd7f6e9a3 Address: 0x00000006fc03f831db616390e014ebee26bb0ce3
  Time:    47s Score:  8 Private: 0x3729ecb8968a602d24ad6a40cddba81fbc052e7478c28f156e580a6dd7f6ea57 Address: 0x000000002b788945a91b4357c0ccc59515e4f7cd

Zrzut ekranu 2021-02-19 o 21 38 19

It is generating not correct addresses on this card:

Intel UHD Graphics 630

Zrzut ekranu 2021-02-19 o 21 42 28
@Brucecarl
Copy link

Brucecarl commented Apr 29, 2021 •
edited
Loading

I have the same issue.But in my mac, Intel UHD Graphics 630 can generate correct address while AMD generate error address! Will this bug fixed in the future?

@gobigobigobigobi gobigobigobigobi mentioned this issue Feb 1, 2023
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gkucmierz @Brucecarl