pixel-chain-story

Path to a respected L1 / bridge / sovereignty regime

Stance: keep the honest lab frame and build until the frame is obsolete.
Respect is not requested in copy. It is earned when a skeptical engineer can clone, break, and still find the invariants holding.

This document is the north star. ROADMAP.md is the checklist. Normative behavior is whatever SPEC.md + CI enforce.


0. How respect is earned (non-negotiable)

Skeptic move Our answer
“Cute metaphor” Point at bun run test:all + SPEC invariants
“Vapor bridge” Point at a non-stub foreign verifier + frozen fixture
“Not an L1” Point at multi-host tip extension, stall recovery, headers sync
“Sovereignty theater” Point at ≥7 live diverse providers failing cloud-majority sets on the wire
“QR marketing” Point at OTS leaf enforcement + live PIX-ML-DSA-65 (bun run test:mldsa) + QUANTUM.md
“Optical scam” Point at real camera capture + two-device Kindling that fails remote

Public voice rule: claim only what the highest passing gate allows. Vocabulary (Kindling, Worldlight, PoLS) stays — claims escalate with gates.

Guide: art guided by science it need not name (One.Creed.guide). Light verbs compress the physics of being; they do not excuse missing invariants.

Never: hide gaps behind thesis strings. Thesis strings describe intent; gates prove delivery.


1. Where we are (Gates A–C, E, F lab)

Runnable, tested, and framed as a lab prototype with real crypto:

Allowed claim: “Executable post-quantum-class UTXO lab; multi-host tip extension; ULA verify + phone-capable light path (lab).”
Forbidden claim: “Production L1 / production bridge / AWS-proof network / BFT mainnet.”


2. The regime we are building (destination)

Pillar Done means
L1 Independent hosts extend one tip; stalled sequencers recoverable; light clients sync headers; published benches
Bridge Lock on A → verify on B with real crypto; no stub lightProofValid; testnet value moved end-to-end
Sovereignty Live ≥7-provider set; diversity enforced on join; no required CDN/API hostname for ledger use
Custody / Kindling Personal Source + two-device optical (or proven proximity) path; SMS still never spends
Crypto Critical. Versioned schemes; ML-DSA-65 shipped; production default ML-DSA; OTS retained for constrained devices

Invention stays (INVENT.md). Uptake bridges stay optional.


3. Gates (build in order — skip = lose respect)

Each gate has evidence (repo artifact) and claim unlock. Do not advertise the next claim early.

Gate B — Network that doesn’t flake

Build

Evidence: docs/demos/two-node.md + bun run test:net + test:four-node
Claim unlock: “Multi-host Pixel network (prototype tip extension).” — not fault-tolerant consensus yet.

Gate C — Consensus that survives fault

Build

Evidence: SPEC §4.1 + bun run test:fault
Claim unlock: “Fault-tolerant PoLS (lab).” Still not “BFT mainnet.”

Gate D — Quantum security (critical priority — parallel with B)

Build

Evidence: bun run test:mldsa + bun run test:vectors green; QUANTUM.md
Claim unlock: “Crypto-agile PQ signatures — ML-DSA-65 default birth, hash-OTS retained.”

Gate E — Bridge that verifies

Build

Evidence: green Foundry + docs/BRIDGE-STATUS.md + docs/ULA-MLDSA.md (public tx links pending)
Claim unlock (partial): “ULA verify real on EVM/CosmWasm twins (lab); native ML-DSA ULAs; PQ commit gate; local lock→shineIn; foreign verify ≠ vault release.” Full “Testnet ULA bridge” when public links land. Do not claim “on-chain Dilithium.”

Gate F — Light clients & gossip that scale past 3 peers

Build

Evidence: bun run test:light + docs/BENCH.md from test:bench
Claim unlock: “Phone-capable light client path (lab).” — stateRoot at tip today; per-pixel historical state commits still open.

Gate G — Sovereignty as protocol law on a live set

Build

Evidence: live report snapshot + policy rejection demo (cloud-majority join fails)
Claim unlock: “Diversity-enforced sequencer set (pilot network).”

Gate H — Kindling / optical that is not theater

Build

Evidence: test:optical + kindling optical-capture path green
Claim unlock: “Optical capture path shipped (pilot); presence-bound Kindling when channel=optical-capture.”

Gate I — External scrutiny

Build

Evidence: docs/AUDIT.md (PREPARING until report link)
Claim unlock (now): “Scoped audit package prepared; external review pending.”
Claim unlock (after report + fixes): “Audited components (scoped).” Full “trusted L1” only after broader ops maturity.

Gate J — Regime (public network)

Build

Evidence: public peers, chaos drill writeup, sovereignty report continuous
Claim unlock: “Pixel public pilot / mainnet-candidate.”


4. Workstreams (parallel after Gate B)

Stream Owner shape Depends on
Node / consensus Systems B → C → F
Crypto Cryptography D (can start now)
Bridge / Solidity Eth + relayer E (can start stub→real now)
Sovereignty ops Operators G (needs B+)
Kindling / mobile Client H (needs D for safe keys)
Field access BD/KS pilots Access + Kindling invite; never blocks L1

Coders pick a stream via CONTRIBUTING.md. Non-coders: field pilots and provider ops still move Gate G/H.


5. Communication doctrine (so “non-coder toy” never sticks)

  1. Lead with the runnable artifact — CLI, tests, SPEC — then name the invention.
  2. Gate badges in README / pix_protocolInfo.status — e.g. gates: ["A","B"].
  3. Compare carefully — Bitcoin scarcity math and Ethereum sequencer analogies are fine; “we replace X” is not, until the gate for X is green.
  4. Keep metaphors subordinate — Lumen/Kindling explain UX; they do not excuse missing fork-choice.
  5. Invite hostile review — link THREAT-MODEL gaps; reward people who find landmines (we already closed verifyLight).

6. Immediate next actions (this repo)

  1. Commission external Gate I review from AUDIT.md scope; publish report link
  2. Public testnet ULA links (Sepolia) + deepen on-chain ML-DSA beyond commit gate when gas path exists
  3. Opt-in ML-KEM sealed gossip (PIXEL_TRANSPORT_KEM=1, test:kem-wire) — default still plaintext
  4. Continuity merchant handshake (one-button join) + map fee / till-on-origin-dark bookkeeping — agentic booth runners still held
  5. Lab chaos drill + till ledger accrual (test:chaos-drill) — not Gate J public evidence
  6. FieldWitness invent — sphere combination lock: peer indices, distance, opacity ∈ {opaque, translucent, lit}; tip PoLS binds fieldDigest; acceptBlock recomputes and rejects mismatch (bun run test:field, SPEC § FieldWitness). PATH note: invent gate evidence — not a rename of prevHash. Verification, continuity of the scene, custody of the tip.
  7. Keep pix_protocolInfo gates honest as evidence lands

Gate D is in. Gate I package is preparing. Continuity desk can drill origin-dark → till accrue in lab — still a pilot, not a costume. FieldWitness is invent evidence for tip custody as a sphere lock — not simile alone.