Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Code:
[13:53:46] Starting Kangaroo search
[13:53:46] Private key found: 19996463086597
[13:53:46] Starting Kangaroo search
[13:53:46] Key verified successfully!
[13:53:46] Key saved to found_key.txt
[13:53:46] Time taken: 0 hours 0 minutes 1 seconds
[13:53:46] Private key found: 19996463086597
[13:53:46] Starting Kangaroo search
[13:53:46] Key verified successfully!
[13:53:46] Key saved to found_key.txt
[13:53:46] Time taken: 0 hours 0 minutes 1 seconds
My python kangaroo with a twist can solve puzzle 45 in 1 second
2**23 jumps = 8 million point additions. So maybe the twist is simply to do the arithmetic in C and call it from Python?
Should take about half a second, start to finish, to solve any 44 bit private key from scratch. Now think, how long does it take to solve puzzle 80, from scratch?
Per core, I'm getting 4.8 MK/s with single Base58 address… Maybe that's close to Hash160 speed. @Nomachine, may i know the speed of a single core with Hash160?
4.8 MK/s per core, on a CPU, to do RIPEMD160(SHA256(...)) is pretty impressive. But even running the hashing on an empty buffer in a loop (no EC involved at all, simply hashing) is much slower than the actual EC throughput (12 MK to maybe 20 MK/s per core, using libsecp256k1), so it is futile to optimize that part until the hashing speed itself catches up. Currently, that means that H160 needs a 3x to 4x boost up in speed, which I find unlikely to ever happen (if it does, most likely the EC throughput would also be boosted up proportionally).