lotterypuzzle atlas

Start

If you arrived from the thread

A seven-step path through the 2015 160-address P2PKH catalog: what the object is, which two search classes exist, and where claim risk lives.

A first sitting

Read in order if you came from BitcoinTalk. Each step points at one atlas page. This path does not install software, rent hardware, or collect a key.

What this is

On-chain

160 P2PKH addresses funded 15 January 2015. Address N is restricted to keys in [2N−1, 2N - 1]. This site maps that set.

The 160 records

Snapshot

Class, hex range, genesis transaction. Live balance is on an explorer, not in this prose. Nominal catalog allocation became N x 0.1 BTC after the 16 April 2023 reward transaction. Catalog unit is not UTXO.

The two that matter now

Method

#71 is the lowest address-only target (HASH160 brute force, no public key from the 2019 leak). #140 is the primary kangaroo-class target (known compressed public key, interval width 2139). Higher address-only ranges are not practical as brute force.

How a search actually works

Method

Kangaroo and BSGS need a public key. A P2PKH spend publishes that key in the scriptSig. The first four private keys look patterned; they are not a method for #71. Calculators on this site teach ranges and probability. They do not run a hunt.

Wrong ideas, before the math

Refuted

ASICs hash SHA-256d; they do not search secp256k1. Kangaroo without a public key is the wrong algorithm for #71. A pool share is not the UTXO. GitHub demos that finish in minutes are replaying already-spent first keys. Expected value on remaining high targets is usually negative.

If you ever find a key

On-chain

A public P2PKH spend reveals the public key before confirmation. Confirmed spends on #66 and #69 are different UTXOs on those days, not two spends of one outpoint. This atlas will not ask for a private key. Read the claim page as a risk reference, not as a claim recipe.

Who funded this, labeled

Forum statement

Forum statements, on-chain facts, speculation, mix-ups. A story is not a method. History is the labeled timeline. saatoshi_rising's 2017 authorship post is a forum statement, not a proof.

What this path leaves out

This path stays inside the public catalog: object, two search classes, and claim risk. It does not include a rental walkthrough, a GPU vendor list, or an account.

The same reading order is in Spanish at /es/empezar/ and in Russian at /ru/nachalo/.