⭐ Merited by ETFbitcoin (1)
With some mod of your code, I could try another project, a vanity pubkey instead of an address pubkey:
https://crypto.stackexchange.com/questions/60239/elliptic-curve-and-vanity-public-keys
The "best" pubkey I have found with my onw cpu code so far is:
Without sha256 + ripemd160 + base58 encode, I guess I could achieve a very impressive key rate.
https://crypto.stackexchange.com/questions/60239/elliptic-curve-and-vanity-public-keys
The "best" pubkey I have found with my onw cpu code so far is:
Quote
02000000000000aeea7a7a5c04504f6e4e45452940431c9a264011686f3b746f92
Without sha256 + ripemd160 + base58 encode, I guess I could achieve a very impressive key rate.
Yes and there is also a CUDA intrinsic that search for the number of starting zero __ffsll which could be used to speed up the checking of public key.
CPU profiles of the last release:
(using compressed address)
(using uncompressed address)
EDIT: FindKey include, mainly, lookup table, ecc arithmetic (ModAdd and ModSub)
ModMulK1 is the SecpK1 modular mult, there are 2 ModMulK1 signatures for this method.
Added the 2 profiles for compressed and uncompressed.