#136
Unsolved13.6 BTCStill unsolved, and the public key is not known either — so the only approach is generating keys through the interval one at a time and comparing addresses. There are 2135 keys in the interval, so sweeping all of it costs that many attempts (on average, half).
0x8000000000000000000000000000000000 ~ 0xffffffffffffffffffffffffffffffffff
2^135 = 4.4×10^40
13.60000000 BTC · 3 tx
snapshot from 2026-08-23
A transaction moving puzzle funds carries the public key and the signature. The moment it reaches the mempool, bots take the same coins with a higher fee. That is exactly how #66 and #69 were lost. How to prevent it
How to actually run this puzzle
With no public key there is nothing to do but generate addresses one at a time and compare. BitCrack does that on the GPU. On NVIDIA that means the CUDA build, cuBitCrack.
git clone https://github.com/brichard19/BitCrack cd BitCrack make BUILD_CUDA=1 # On Windows, open BitCrack.sln in Visual Studio and build the cuKeyFinder project # to get cuBitCrack.exe. macOS is not supported.
./cuBitCrack -d 0 -b 288 -t 256 -p 1024 -c --keyspace 8000000000000000000000000000000000:ffffffffffffffffffffffffffffffffff --continue progress-136.txt -o found-136.txt 1UDHPdovvR985NrWSkdWQDEQ1xuRiTALq
- The best values for -b/-t/-p differ per GPU. Run it once at the defaults, look at the rate, then adjust.
- Always include --continue. It keeps your position across restarts.
- To split across machines, turn on “split the work” above. --share divides the range without overlap.
- This shard covers 8000000000000000000000000000000000 ~ ffffffffffffffffffffffffffffffffff.
CPU only. Handles both addresses and public keys, and is the easiest to install — good for learning and for checking your setup.
This puzzle's public key is not exposed. There is no discrete logarithm to solve.
On a single RTX 4090 this takes 5.5×10^23 years — 4.0×10^13× the age of the universe. That is not “eventually”; in most cases it means “no”. Doing it anyway means accumulating GPUs or joining a pool.