1Jvv4y
Solved puzzle #66 (6.6 BTC) on 2024-09-12. Had the prize stolen by mempool bots who RBF'd the transaction. The first public case of puzzle theft.
83 puzzles have been solved since January 2015. Forum-handle attributions are shown as claims when identity is not proven by the spend transaction.
01
Top solvers
| Rank | Solver | Puzzles | Nominal reward | Range | First solve | Last solve |
|---|---|---|---|---|---|---|
| #1 | 1aaRgu | 10 | 8.8 BTC | #2–#23 | 2015-01-15 | 2015-01-15 |
| #2 | 12x45A | 9 | 24.4 BTC | #22–#32 | 2015-01-15 | 2015-01-16 |
| #3 | 1ghost | 7 | 30.1 BTC | #40–#46 | 2015-01-30 | 2015-01-30 |
| #4 | zielar | 6 | 46.8 BTC | #59–#115 | 2019-02-12 | 2020-06-16 |
| #5 | pikachunakapika | 5 | 40.0 BTC | #70–#90 | 2019-06-09 | 2019-07-01 |
| #6 | 15L3Hy | 4 | 19.4 BTC | #47–#50 | 2015-09-01 | 2015-09-01 |
| #7 | LBC | 4 | 21.0 BTC | #51–#54 | 2017-04-05 | 2017-11-16 |
| #8 | 18sLsb | 3 | 10.1 BTC | #30–#38 | 2015-01-16 | 2015-01-19 |
| #9 | 1AqEgL | 3 | 16.8 BTC | #55–#57 | 2018-05-29 | 2018-11-08 |
| #10 | RetiredCoder | 4 | 51.0 BTC | #120, #125, #130, #135 | 2023-02-27 | 2026-07-28 |
| #11 | Kowala | 2 | 13.5 BTC | #67–#68 | 2025-02-21 | 2025-04-06 |
"Nominal reward" shows N × 0.1 BTC per puzzle (the current reward formula). Actual BTC swept on-chain may differ for puzzles solved before the April 2023 10× prize increase. Puzzle #135's RetiredCoder attribution is self-reported; its spend transaction proves the spend, not the forum identity. See statistics for details.
02
Notable single-puzzle solvers
bc1qlp
Solved puzzle #69 (6.9 BTC) on 2025-04-30 in under 1 month. Key was at 0.72% of range. Also had the prize stolen — transaction replaced 4 times.
36X5Cc
Solved puzzle #64 (6.4 BTC) on 2022-09-10. A 3-year gap between puzzle 63 and 64 showed how exponentially harder each bit becomes.
125CWt
Solved puzzle #100 (10.0 BTC) on 2019-07-08. First double-digit reward claimed. Required kangaroo on revealed public key.
Note: Solver names are Bitcoin addresses or handles from BitcoinTalk. Some may refer to the same person. On-chain data proves spends; a handle attribution can still be self-reported and is labeled accordingly.