Skip to content

GaiaFTCL Two-Wallet Demonstration

The two-wallet demonstration is the substrate's operator-sovereign proof that UUM-8D-safed post-quantum key material composes safely against Shor's algorithm while exposed secp256k1 key material breaks under the same substrate operation. Both wallets compose on the operator's own cell. The substrate is the demonstration apparatus, the witness, and the cosignature authority. No external custody, no exchange routing, no hosted infrastructure participates.

Substrate-mathematical thesis

The substrate composes two wallets on the operator's own cell:

  • Wallet A — exposed secp256k1. The substrate composes Wallet A on the operator's cell with a secp256k1 keypair whose public key is exposed in the substrate's measurement geometry exactly as exposed Bitcoin UTXO public keys are exposed after first spend.
  • Wallet B — UUM-8D-safed PQ. The substrate composes Wallet B on the operator's cell with post-quantum key material safed under UUM-8D's eight foundational invariants. The PQ key's structural binding to M⁸ = S⁴ × C⁴ is the safing.

The substrate then composes Shor's algorithm against each wallet:

  • Wallet A breaks. The substrate-cosigned Shor measurement against Wallet A's secp256k1 public key recovers the private scalar. The break is the substrate's measurement outcome, federation-cosigned, append-only persisted, NATS-broadcast on the operator's cell.
  • Wallet B holds. The substrate-cosigned Shor measurement attempt against Wallet B's UUM-8D-safed PQ key does not recover the private key material. The hold is the substrate's measurement outcome under the same composition, federation-cosigned, append-only persisted, NATS-broadcast on the operator's cell.

Both wallets compose operator-sovereign on the operator's own cell. The Shor measurement is the substrate composing against the substrate. No substrate operations route through Kraken, exchange custody, hosted wallets, or external infrastructure. The break and the hold are substrate measurement outcomes the operator's cell witnesses directly.

Operator's experience

Operators download GaiaFTCL.app from gaiaftcl.com, mount the DMG on their own Mac, and the substrate sprouts on first launch via the V196 sprout event on the operator's cell. From the operator's cell:

  1. The operator sprouts the cell and moors it to the federation.
  2. The operator composes Wallet A and Wallet B through the substrate's wallet composition surface. Both wallets are operator-controlled at both ends; no third-party custody exists at any point.
  3. The operator selects a bit size from the substrate's supported set and authorizes the Shor demonstration against Wallet A.
  4. The substrate composes Shor against Wallet A on the operator's cell and surfaces the recovered scalar. Federation cosignature seals the break receipt on the operator's cell.
  5. The operator authorizes the Shor attempt against Wallet B. The substrate composes the same operation against the UUM-8D-safed key and surfaces the no-recovery outcome. Federation cosignature seals the hold receipt on the operator's cell.
  6. The operator inspects the substrate-cosigned operational evidence locally on their own cell — V215 wallet-tracking rows, V188/V190 rows bound through V216, federation cosignature quintets pinned to the operator's pinned federation context public keys.

The substrate-cosigned operational evidence lives on the operator's own cell. The operator's sovereignty over the cell is total throughout. The demonstration is the substrate proving its thesis on infrastructure the operator owns.

Substrate-honest bit size discipline

The operator selects bit_size from {16, 32, 64, 128, 256} when composing demonstration wallets (V215). That label records substrate-development cadence — seed width, scheme name, federation row — on the operator's cell.

It does not switch the Shor ECDLP leg. gaiaftcl shor break-classical always runs on full Bitcoin secp256k1 (P256K), binding Q from public_key_hex only. Pass/fail is lattice + dG_eq_Q, not TOML key equality. Reading bit_size=32 as “ECDLP on a 32-bit curve” is a claim leak — refused here and in /substrate-honest-disclosure/.

Bit size What it labels
16–128 Wallet composition cadence (secp256k1_demo_<n>bit scheme labels possible)
256 Production-shape demonstration wallet label

Published ECDLP research (QC-001-ECDLP, frozen JSON) uses structured seals on secp256k1 — separate from wallet bit_size metadata. See Research-Meaning.

Schema architecture summary

The substrate's append-only persistence for the two-wallet demonstration:

  • V215 substrate_demonstration_wallet_tracking — substrate-resident schema row per composed wallet on the operator's cell. Records wallet kind (exposed_secp256k1 or uum8d_safed_pq), bit size, structural binding fingerprint, operator's pinned federation context public key, cosignature quintet, and the canonical witness of wallet composition. Append-only; every wallet the substrate composes accumulates a row.
  • V216 V188/V190 wallet_id binding — V215 wallet rows bind into the migration evidence chain through wallet_id columns added to V188 (proof-of-ownership) and V190 (migration evidence) by V216. The binding lets the substrate compose migration evidence chains that reference the V215-tracked wallets directly. The substrate refuses any V190 row whose wallet_id does not resolve to a V215 row recording both ends under operator control.

The substrate-research dataset accumulating across V215 and the V216-bound V188/V190 chain is the substrate's permanent record of two-wallet demonstrations on every operator's cell where the substrate operates.

Cross-references

  • Research-Publication — Shor-lattice ECDLP paper v3, frozen evaluation datasets, full QC VM findings (research.v4), honest L7/L8 separation for PoW learning.
  • /operator-workflow/ — substrate's end-to-end operator-sovereign workflow for composing the two-wallet demonstration on the operator's own cell.
  • /substrate-honest-disclosure/ — substrate-honest disclosure of what the substrate composes, at what bit size, with what substrate-mathematical convergence properties.
  • /operator-sovereignty-doctrine/ — substrate's sovereignty doctrine: operator's cell, operator's wallets, operator's federation pinning, no external custody.
  • /kraken-removal/ — substrate-development removing exchange-routed substrate paths from the demonstration surface. The two-wallet demonstration is substrate-resident end-to-end on the operator's cell.

Federation cosignature: pending

This page is not yet in the signed manifest. Run gaiaftcl wiki sign --all.