The creator, labeled

Claim — On 27 April 2017, BitcoinTalk user saatoshi_rising posted “I am the creator.” That is the only named authorship claim in the public record. Origin — BitcoinTalk thread #1306983, 2017-04-27. Evidence — A forum post. Anyone can type those words. No signature from a puzzle key, no PGP, no on-chain message from the genesis outputs that cryptographically binds the handle to the endowment. Verdict — Treat as the primary public claim. Do not treat as a proof of identity. Quote — “I am the creator.”

Claim — The same post frames the puzzle as “a crude measuring instrument, of the cracking strength of the community.” Not a riddle with a hidden algebraic trick. Origin — Same 2017-04-27 post, quoted across the thread and later write-ups. Evidence — The structure matches the claim: 256 P2PKH outputs, each locked to an N-bit interval that doubles every step. That is a ladder of search cost. It is also what an educational demo or a vanity staircase would look like. Verdict — Stated purpose of the only public claimant. Still a statement, not a proof of motive. Quote — “There is no pattern. It is just consecutive keys from a deterministic wallet (masked with leading 000…0001 to set difficulty). It is simply a crude measuring instrument, of the cracking strength of the community.”

Claim — The claimant said the keys have no extra structure beyond the bit-length mask. Community threads still hunt for one. Origin — Same 2017-04-27 post. Recurs in later BitcoinTalk pages whenever someone proposes a closed form. Evidence — Spent keys #1–#3 look like 2^N − 1 (1, 3, 7). #4 is 8. After that they wander. That is compatible with a deterministic generator plus an N-bit mask, and compatible with “no extra pattern.” A local regularity at the start is not a law for #71. Verdict — Hunting a secret formula is a story. The public claimant denied it. Spent keys do not revive it.

Claim — Keys were not 256 independent rolls. They are consecutive outputs of a deterministic wallet, then masked with leading zeros and a high 1 so puzzle N sits in [2^N−1, 2^N − 1]. Origin — saatoshi_rising, 2017-04-27: “consecutive keys from a deterministic wallet (masked with leading 000…0001 to set difficulty).” Evidence — A deterministic wallet maps (seed, index) → 256-bit scalar, typically via HMAC. “Consecutive” here is derivation index, not consecutive integers. Spent keys are not k, k+1, k+2. The mask explains the ranges. The seed has never been published. Verdict — Best mechanical description we have, from the only public claimant. Unverified. Useful as a model, not as a shortcut.

Claim — The claimant agreed those 96 addresses were “silly,” said it had not occurred in two years, and promised to spend them into the unsolved lower set and to add funds. Origin — Same 2017-04-27 post: “You are quite right, 161–256 are silly… I will spend from 161–256 to the unsolved parts.” Evidence — On 2017-07-11 those outputs were emptied into #53–#160. The move matches the promise. It still does not cryptographically identify the poster. Verdict — Forum promise, later matched on-chain. The catalog of 160 is the surviving set.

Claim — Whoever emptied #161–#256 still held those keys in July 2017 and chose to top up #53–#160. That is continued control of the original endowment, two years after genesis. Origin — On-chain spends, 2017-07-11, matching the April forum promise. Evidence — The spends are observable. They prove that someone with the 161–256 keys acted. They do not prove that person is saatoshi_rising, and they do not prove the same person still holds #71 or #140 today. Verdict — On-chain fact of 2017 control over the high addresses. Identity and present custody are separate questions.

Claim — On 16 April 2023, transaction 12f34b58… sent 872.19 BTC (85 outputs, block 785620). The catalog prize became N × 0.1 BTC. That looks like the original patron still paying for the instrument. Origin — On-chain top-up, 2023-04-16. The 2017 post had promised “further funds.” Evidence — Someone with a lot of bitcoin chose these addresses. That is compatible with the original seed holder and compatible with a later whale. The chain does not name them. Verdict — On-chain patronage. Identity of the sender is not a catalog fact.

Claim — If a single seed produced every puzzle key, the seed holder can sweep any remaining address at will. Unsolved does not mean lost. Origin — Logical consequence of the deterministic-wallet claim, repeated whenever a high puzzle sits untouched. Evidence — No independent check exists. A live balance on an explorer only shows the coins are still there. It does not show who can sign. The 2017 and 2023 movements are compatible with a retained seed and also with a later whale copying the pattern. Verdict — Possible if the wallet story is true. Not a fact. Hunt math does not change either way.

Claim — The handle, the size of the 2015 endowment, and the date are offered as signs that the puzzle is a message from Bitcoin’s author. Origin — BitcoinTalk thread #5201811 (November 2019) and recurring quotes of the 2017 post. Evidence — None. The name is a pun. 32.896 BTC is large and still tiny next to attributed Satoshi holdings. Satoshi’s last public posts are 2010–2011. A 2015 transaction and a 2017 forum claim do not identify that person. The thread itself is argument, not evidence. Verdict — A story about a name. File it as speculation. It does not change the catalog or the search.

Claim — The bit-length staircase exists to show, in public, how search cost grows and how far an ordinary 256-bit key sits from anything a GPU can inventory. Origin — Community reading of the “measuring instrument” sentence. No separate primary source. Evidence — Compatible with the structure and with the claimant’s wording. Also compatible with patronage, vanity, or a canary. Motive is not observable. Verdict — A plausible reading of a forum sentence. Not a fact.

Claim — An unexpectedly fast spend of #140–#160, where the public key is known, would invite research into a new algorithm — quantum or otherwise — rather than into ordinary kangaroo work. Origin — Community speculation after the 2019 public-key leak. Recurs whenever someone asks if a quantum computer can “solve Bitcoin.” Evidence — None. A spend on a high kangaroo target does not identify the method. Hardware that exists today does not break secp256k1. Treating those five addresses as a canary is a story you can tell about any unsolved bounded ECDLP. Verdict — Speculation. A fast high spend would be news. It would not, by itself, name the machine.

Claim — The 1,000-sat spends from every fifth address between #65 and #160 were intentional: publish the public key so Pollard kangaroo / BSGS can run on a bounded interval. Origin — On-chain: deposits 2019-05-16, pubkey reveal 2019-06-01. Intent is a later community reading. Evidence — The spends are a fact. They do leave the public key in the P2PKH scriptSig. They do enable kangaroo on those intervals. Who signed, and whether the point was a lab, a gift, or a mistake, is not on the chain. Verdict — On-chain effect, speculative intent. For the hunter the effect is what matters: #140, #145, #150, #155, #160 are kangaroo targets.

Claim — The clustered spends around #66 (12 September 2024) were a designed test of mempool sniping: leak a public key with a public broadcast and watch who races. Origin — A public P2PKH broadcast reveals the public key before confirmation; that mechanism is real. Confirmed same-day spends can still be different UTXOs. The “lab” reading is community interpretation, also applied loosely to #69. Evidence — A public P2PKH broadcast reveals the public key before confirmation. A second holder of the same scalar can issue a conflicting spend. That mechanism is real. That it was the creator’s experiment is not shown. Verdict — The race is a fact of the script type. Attribution of intent is speculation. The claim page exists because of this, not because of a lore theory.

Claim — A solver credited with several high kangaroo spends is, in some threads, collapsed into the creator. Origin — BitcoinTalk speculation. RetiredCoder is credited in community records for #120, #125, #130 and, later, #135. Evidence — Solver and creator are different roles. Being credited with finds is not authorship of the 2015 genesis. No published argument binds the two handles. Verdict — Speculation with no evidence. Solver and creator are different roles. The finder labels stay dated on History; authorship stays on this page.

Claim — If the wallet used a particular language’s RNG or HMAC construction, brute-forcing that seed-space reconstructs every remaining key. Origin — BitcoinTalk pages from 2025 onward arguing C++ versus Python because “Satoshi wrote Bitcoin in C++.” Evidence — Without the seed, this is another brute force, now of a seed space whose size you do not know. A language guess is not a reduction of #71 or #140. No public reconstruction has produced a remaining key. Verdict — A rabbit hole. Not a method. The ranges in the catalog are still the work.

Claim — If the keys were masked, a clever unmasking step should recover them without search. Origin — A misreading of the 2017 sentence, recurring in later thread pages and chat rooms. Evidence — The mask sets the search interval. Puzzle N is already the masked scalar: an integer with N bits, MSB = 1. Spending it does not require an original 256-bit preimage. There is no second layer for the hunter. Verdict — False reading. The mask is the difficulty. It is not a cipher to invert.

Claim — If the keys came from one seed, recovering any puzzle key reveals the seed, hence every remaining puzzle. Origin — BitcoinTalk and later pages that quote the deterministic-wallet sentence and skip the one-way step. Evidence — HMAC(seed ∥ index) is not reversible from one output. Consecutive derivation is not consecutive integers. Finding the scalar for #71 gives you that scalar. It does not invert the wallet. Each remaining puzzle is still an independent range for everyone who is not the seed holder. Verdict — False even if the wallet story is true. The seed holder is a different person from a hunter who found one key.

Claim — The creator, or a silent solver, already emptied the open addresses. The catalog is a ghost. Origin — Recurring distrust of public trackers and of delayed explorer caches. Evidence — A UTXO is observable. This atlas stores a catalog sum, not a live wallet. If an open record is spent, the explorer shows it. Check the address, not a screenshot. Verdict — Checkable against a dated explorer snapshot, not a structural refutation. False until the explorer says otherwise. Verify on-chain.

Claim — In August 2026 a separate puzzle around a genesis-block OP_RETURN circulated. Some write-ups treat it as the same object as these 160 addresses. Origin — News and thread cross-talk in August 2026. Different script, different date, different key. Evidence — This atlas is the 2015-01-15 P2PKH set funded in transaction 08389f34…cd15. A genesis-block OP_RETURN is another artifact. Do not merge their math or their keys. Verdict — Different object. This page, this catalog, this hunt — 2015, 160 addresses.

Claim — 1FLAMEN6, the Chancellor Nakamoto series, DEF CON brainwallet talks, and random “puzzle” repos are treated as chapters of the same hunt. Origin — Name collision. BitcoinTalk itself cross-references unrelated riddles when the word “puzzle” appears. Evidence — Those objects have their own scripts, dates, and authors. They do not share the 2015 genesis transaction, the N-bit ranges, or the 2019 every-fifth leak. Verdict — Cite them if you must. Do not hunt them with this catalog.