Quote from: Desyationer on Today at 01:07:24 PM

Quote

And from Cyclone, we get Kangaroolone. 😄

Why do all the programs I know, such as BitCrack, KeyHunt-Cuda, and VanBitCracken, search for a single address using the full P2PKH address instead of its H160 hash? Searching by H160 could significantly speed up key enumeration—potentially increasing the rate from 4–5 GKey/s to 5–6 GKey/s for 4090

They don't. But if you want some prefix, than H160 might have a prefix that looks good, but is below (or above) the min/max addresses that have the given prefix. This is also the main reason why it's totally stupid to search for the address prefix - the H160 may have more or less actual exact bits then desired.

Do you also honestly think no one ever discovered that it's the H160, not the address (or some stupid prefix non-sense) that matters in reality?

Also, did you randomly guesstimated that you can simply enumerate the keys faster (whatever that means) and straight up go from 4-5 to 5-6? On what basis? Let me tell you the truth: what you said is already done, but you probably use the wrong code or app for this, because an RTX 4090 is capable of doing 7.0 - 7.1 GK/s to scan a given range, not 4 or 5. Yes, just the keys in a given interval, not the ones with symmetry or endo (in that case, it can surpass 10 GK/s).