Bitcoin Puzzle #72

Unsolved  Prize 7.2 BTC · 72-bit keyspace

Status
Unsolved (as of 2026-06-23)
Reward
7.2 BTC
Key range
2^71 … 2^72 − 1
Range (hex)
800000000000000000 … ffffffffffffffffff
Target address
1JTK7s9YVYywfm5XUH7RNhHJH1LshCaRFR

What puzzle #72 is

Puzzle #72 is one address in a set of 160 created in January 2015, when someone funded a sequence of Bitcoin addresses whose private keys were deliberately confined to ever-larger ranges. Puzzle #72's key is an integer somewhere in 2^71 … 2^72 − 1 — in hexadecimal, from 800000000000000000 to ffffffffffffffffff. Whoever finds that integer controls the 7.2 BTC held at 1JTK7s9YVYywfm5XUH7RNhHJH1LshCaRFR.

How hard is it?

The range holds about 2^71 candidate keys. A fast multi-core browser search covers a few million keys per second; at that pace, sweeping the entire range would take on the order of 1.5×10^7 years. In practice nobody sweeps the whole range — a solver simply hopes to land on the key by chance, so raw speed buys lottery tickets rather than a deadline.

For puzzle #72 only the address is public, not the public key. That rules out fast discrete-log methods like Pollard's kangaroo, so the only approach is to generate candidate keys and check each one's address — exactly what the scanner below does.

Why the key is safe to search for

Searching is legal and harmless: these funds were placed deliberately as a public challenge by their owner. The scanner runs entirely in your browser, generates candidate keys locally, and never transmits anything. The practical catch is not the search but the claim — recent solvers of nearby puzzles had winning transactions snatched from the public mempool by bots, so anyone who did find a key would need to broadcast with great care.

Scan puzzle #72 in your browser

Each thread jumps to a random spot, scans this many keys, then jumps again.

Idle

startend
0Keys checked
–Keys per second
0:00:00Running time
–To cover the full range
ThreadKeys checkedCurrent key

Log

Other frontier puzzles

Status and balances last checked 2026-06-23. For live confirmation see the privatekeys.pw tracker.