another issue not finding genesis block

[jlopp]

another issue not finding genesis block

[mycroft]

I do not think there is an issue here. You're just being unlucky and it just takes time to find a valid hash with the parameters. I was able to get one valid hash with your parameters and it took 30-45 min on my end unfortunately:

$ ./generate-genesis -nonce 0 -psz "03/May/2024 Bitcoin block 000000000000000000001ebd58c244970b3aa9d783bb001011fbe8ea8e98e00e" -timestamp 1714777860 -pubkey 000000000000000000000000000000000000000000000000000000000000000000 -workers 48 -maxprocs 128

Ctrl Hash:      0x00000000f3c23edbdaabb23bab7598874aed89a515ef182c121f7469c9b8b05e
Target:         0x00000000ffff0000000000000000000000000000000000000000000000000000
Blk Hash:       0x00000000f3c23edbdaabb23bab7598874aed89a515ef182c121f7469c9b8b05e
Mkl Hash:       0x44c6a56ff59c8016031e3be56c4c9d60fa95086a7803a454f7b507084d0c6e12
Nonce:          3185950820
Timestamp:      1714777866
Pubkey:         000000000000000000000000000000000000000000000000000000000000000000
Coins:          5000000000
Psz:            '03/May/2024 Bitcoin block 000000000000000000001ebd58c244970b3aa9d783bb001011fbe8ea8e98e00e'

It went from timestamp 1714777860 to 1714777866 which means it computed like 30 trillions signatures (~60 trillions sha256 unless I'm wrong) to get there.

Please remember this piece of code is written in golang which is definitely not the best language for this kind of stuff as I'm 100% sure our modern CPUs could handle a lot more hashes/sec and have faster results.

However, it's been a while I did not profile golang compiled stuff but I might give a look to find out if there is no quick win scenario to have faster results. I've already added configurable workers/GOMAXPROCS flags to customize cpu usage but golang seems to limit cpu usage to 85% here (50% prior modification)

[jlopp]

Aha, fair enough!