Facts, labeled

One transaction, 256 outputs, 32.896 BTC (that is thirty-two point eight nine six: the sum of 0.001×n for n = 1…256). Block 339085, 18:07:14 UTC, txid 08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15. No announcement. No instructions. Every later puzzle address in this catalog descends from this funding event.

BitcoinTalk thread #1306983. Community records: puzzles 1–50 were already spent. Found by Bulista (brute-force bot) and noted earlier by amaclin. Forum chronology, not a signed statement. The original English timeline dated this 2015-12-27; the opening post of thread #1306983 displays “December 28, 2015, 04:12:47 PM”. Treat the calendar day as off-by-one until the forum timezone is documented. Thread #1305887 is a precursor, not a replacement for #1306983.

On BitcoinTalk: consecutive keys from a deterministic wallet, left-padded with zeros to set difficulty, as a crude instrument of community cracking power. Forum statement, not a cryptographic proof of identity. The 27 April 2017 wording is quoted on thread #5201811 and reachable through the message permalink below; the account profile link is listed as the handle, not as a person. Later funding movements are consistent with that post — compatible action is not proof that the account controlled the funding keys. A forum handle is not a legal identity.

Block 475240, 05:00:53 UTC. 97 inputs, 109 outputs, 103.527 BTC. High-range puzzle outputs were moved. The 103.527 BTC is the transaction total, not a prize figure. Community records describe the low-range puzzle destinations as #53–#160 and the emptied high range as #161–#256; this atlas does not map every output to a puzzle number, and the 109 outputs also include puzzle #1 (1BgGZ9tcN4rm9KBzDn7KprQz87SZ26SAMH). Treat the per-output grouping as a labelled community account, not a verified mapping.

Block 576251, 04:25:45 UTC. 21 outputs of 1,000 sat (0.00021 BTC in total). Those 21 destinations are puzzle #1 (1BgGZ9tcN4rm9KBzDn7KprQz87SZ26SAMH) plus the 20 leak-series addresses: every fifth address from #65 to #160. That is one puzzle output plus twenty leak-series addresses — not 21 leak-series addresses, which is how the story is sometimes told. A P2PKH receive does not reveal the public key, so the deposit itself leaked nothing; the following spend is what mattered.

Block 578732, 02:07:26 UTC. A 21-input spend of those 1,000-sat outputs. The unlocking script of a legacy P2PKH spend carries the compressed public key, which is how a small spend publishes a large key. Twenty of the inputs are the catalog leak series: every fifth address from #65 to #160 (twenty addresses). The 21st input is 1PvaqLqRAivje7CactLR55xQBYvBeaDrXN — not puzzle #1, and not an address in the 2015 256-output set. The corrected account is therefore: deposit = 1 puzzle output + 20 leak-series addresses; spend = those 20 leak-series inputs + one different extra input. The resulting twenty known public keys are what make kangaroo/BSGS work possible on a bounded interval, and they are also why #140, #145, #150, #155 and #160 are the remaining kangaroo-class targets. A P2PKH spend is one publication channel for a public key, not the only possible one: an unsolved puzzle may have a published key too.

Block 778498, 09:40:55 UTC. Explorer shows 1.20001 BTC funded and spent on this address — the unit then was still N × 0.01 BTC. The catalog column today prints 12.0 BTC for #120; that figure was not the UTXO. RetiredCoder is credited in community records; no primary self-attribution was found.

Block 785620, 06:29:48 UTC. 1 input, 85 outputs, 872.19 BTC. After this transaction the catalog unit becomes N × 0.1 BTC instead of N × 0.01 BTC. The 872.19 BTC is the total moved in this transaction; it is not a live balance, and no current balance is claimed anywhere on this page.

Block 797930, 10:24:07 UTC. Explorer shows 12.50004706 BTC funded and spent, consistent with the post-increase unit. RetiredCoder is credited in community records; no primary self-attribution was found. Do not confuse 2019-06-01, when this address's public key became public, with this spend: some public dumps print the leak date as if it were the solve date.

Multiple transactions on 12–13 September 2024 are observable (blocks 861068, 861069 and 861166), and the address shows further activity afterwards. Confirmed spends that day are different UTXOs; 861166 is a 12-sat receive, not a spend. Who found the key, whether one or more parties were involved, and what any of them intended are community interpretation — including the widely repeated story that a bot recovered the key from a mempool broadcast. The published scalar matches the address; a matching scalar still does not name a person. Details and the on-chain/rumor split: /cases/.

Block 862493, 08:13:37 UTC. Known public key since the 2019 leak series, so this was a kangaroo-class target before it was spent. RetiredCoder is credited in community records; the spend transaction carries no message and no primary self-attribution was found. Spent eleven days after #66; that timing is coincidence unless someone publishes evidence tying the two events, which this atlas does not.

Kowala attribution and a private-channel account: community reports. The key is in the catalog because it matches the address; the name on the solve is a report this atlas does not treat as cryptographic proof.

Kowala attribution, a work estimate, and a private-submission account: community reports, not facts encoded in the transaction.

Key 0x101d83275fb2bc7e0c sits 0.72% into [2⁶⁸, 2⁶⁹ − 1]. Two spends in blocks 894620 (14:45:54 UTC) and 894621 (14:58:29 UTC) are observable. Ownership and intent are not confirmed here.

08:20:16 UTC, block 959946, txid 817535430c600810080662dd425a2e335f771effd950d28fc443bce4a92fa812. The published private key matches the catalog compressed public key and the P2PKH address 16RGFo6hjq9ym6Pj7N5H7L1NR1rVPJyw2v. A later transaction in block 960138 (2026-07-29 19:35:34 UTC, txid 840d3ed5183fd1309c364d5f5a71a9686e78b24ec2e8a502062fc5a9258a9ba7) is also on the address. That transaction sweeps 3,408 sat of post-solve dust, not prize funds. Finder identity is a public statement by RetiredCoder, with a claimed work estimate; the identity claim and the key match are separate claims.