§ 00 · The north star
Kill the bitcoin address.
The 42-character single-use address is a fifty-year usability failure. Bitcoin can do what every payment system before it did: one identity for life, private by default, eventually with nobody to trust in the middle.
This page is the destination the rest of this site is walking toward. It exists so the roadmap, the specs, and every future document can point at one fixed star instead of restating it.
§ 01 · The problem, honestly stated
One address for life already exists. Receiving it privately is the hard part.
Silent payments (BIP 352) already give you a reusable address that never touches the chain. The catch is receiving: finding your own money means scanning everything, so a helper server does the heavy half, and a helper you must trust is the weak link. It can go silently wrong, as one major wallet’s backend did in 2024; the worst designs learn everything about you.
Physics first: someone must compute the scanning data, and that takes full-node data. So “no helper” can never be literal. What it can mean, in order, is no one you must trust, and then no one in particular.
§ 02 · The ladder
Four stages, each one shrinking the trust
1 · A server whose lying is provable, running now
Every answer fingerprinted into a public chain, checkpointed on venues the operator does not control. Cheating quietly becomes impossible. This is the lookout, live, proven with real money.
2 · Many servers, one standard, in progress
One protocol, matching fingerprint heads: servers become interchangeable and check each other, so no single one needs trusting. The converged protocol draft is public, built on measurements nobody else has.
3 · The node network serves it, the class dissolver
Nodes serve the scanning data over the peer-to-peer network, as they already serve block filters (BIP 157/158; a Core tweak index exists as an unmerged branch). The helper class dissolves. Per-block fingerprints double as lying-peer detection, structurally what our chain already is.
4 · The destination: committed by consensus
A soft fork commits each block’s scanning fingerprint into the chain itself (the BIP 158 reserved-hook precedent: commit only to what is specified and deployed). Then the data cannot be wrong, whoever hands it to you; servers are couriers. Nobody has proposed this, including us. It becomes proposable once stages 1 to 3 exist, and not before.
No rung skips the others: consensus can only commit to what is already specified, measured, and running. The boring work is the path.
§ 03 · The honest edges
What even the endgame does not fix
Consensus commitment makes served data impossible to fake, not behaviour invisible: real dust sent to you, and watching who fetches what, uses perfectly honest data. Wallets keep their behavioural defences at every stage. The ladder shrinks receiving trust to zero; it does not promise magic.
Orthogonal shortcut, at every stage: sender notifications can make scanning the fallback rather than the daily path. An optimisation, never a replacement.
§ 04 · Why this kills the address
Names finish what the ladder starts
A reusable address safe for anyone to receive on, trusting no one, beats a string you must rotate. Put a human-readable name on top (BIP 353, both rails) and the 42-character address becomes what the IP address became: still underneath, never typed again. That is the whole bet of this site.
§ 05 · The receipts
Where each claim lives
- The roadmap: the working ladder, item by item.
- The lookout: stage 1’s honesty contract, running today.
- One payment, followed: stage 1 proven with real sats, every value published.
- The measurements: the numbers the 2024 standards debate stalled without, and the converged protocol draft for stage 2.
- SPCOMMIT: the fingerprint chain, specified with test vectors, transport-agnostic on purpose so stages 3 and 4 can inherit it.
Written down 2 September 2026, the day stage 1 opened to the public over Tor. When a stage advances, this page changes and the change log records it.