What exists, what was checked, and what you can inspect.
Availability, verification and public access answer different questions. This index keeps the dated foundations, the local native delivery and the newer design work distinct.
Choose a subject before judging its evidence.
A public page makes an explanation accessible. It does not establish an operated service or an independently reproduced result.
| Subject and availability | Recorded verification | Public action and limit |
|---|---|---|
| Sealed foundations · 2026-09-28 Implemented local foundations; dated assurance closure. | Internal acceptance and separate review; 50/50 hosted jobs on two runs of dev 11c96351 · assurance closure. The figures concern that source and date. | Read the reconstruction scope note Explanatory material; no external security audit or public rerun established by this page. |
| Native profiles · 13 October 2026 Implemented locally; formal acceptance pending. | Reported local service, numerical and common-activation qualification, with synthetic payments and the interruptions exercised. Reconstruction shares parts of the development environment. | Inspect capability scope and delivery record Human observation, formal acceptance and source publication remain open. |
| Continuity design · 21 October 2026 Design and implementation direction, with a separate FxPay research note. | Published reasoning about evidence, obligations and lifetime resource accounting. Actual caller integration and end-to-end M1 verification remain objectives. | Read the engineering update Publication of the design does not close M1 acceptance or establish a payment service. |
The first native capabilities now work together.
Native services, a qualified numerical application and their common activation have been demonstrated in defined local profiles.
Documented local delivery; formal acceptance remains open.
Useful execution, with the commitments it must preserve.
Built, sealed, and on the record
Historical snapshot 2026-09-28: 7 sealed eras (D0-D6), 372 accepted crossings and 50/50 hosted jobs at the assurance closure. These are recorded counts, rather than current availability or standing CI status.
A deterministic local kernel
Eight organs, from FxWire to FxBlock: a claim is received, judged, ordered, executed with a receipt, committed and sealed - on the local development line.
Explore the architectureA sealed history
Seven eras sealed (D0-D6): bytes frozen, powers fixed. Work continues inside a sealed era by additive movements - the persistence era's third closed on 2 August 2026; a fourth is not opened.
Read the historySeparate reconstruction paths
A bounded preserved history rebuilt through oracle and engine paths, then compared without giving either path decision authority. The public note describes internal review, not an external audit.
Read the reconstruction evidenceOne preserved artifact
The genesis snapshot, preserved and verified against its frozen anchor, under a ratified storage constitution.
Read the preservation scopeAn acceptance discipline
Falsifiers, negative controls and hostile review on every crossing; a witness that was measuring a declaration was repaired before sealing.
Read the acceptance methodA closed assurance act
Sovereign Assurance & Attestation closed on 28 September 2026. At the closure, its closing commit was qualified locally, reviewed separately and green on two hosted runs.
Read the assurance closure
What this portal does not offer
- A public network: no devnet, testnet or mainnet; no validators, consensus or finality.
- A token, a sale or an investment product.
- A financial service: the planned wallet, market, banking and payment products are not offered for use through this portal.
- A released public SDK, deployed RPC endpoint or executable API quickstart. The public architecture dossiers are available.
- A public execution package linked from this portal: the available notes are explanations, rather than a verifier download or an SDK quickstart.
- An external audit: the records are internal, and say so.
The next gates
- Source-bound human observations of the actual native behaviour.
- Distinct formal acceptance acts against the exact applicable packages.
- Controlled source publication after the required authority and continuous-integration capacity are verified.
- The next native increment whose dependencies and authority are established.
Adoption zero is a separate later gate
Adoption zero is a planned command-line and browser verifier for a sealed history, receipts and commitments against declared rules and expected anchors. This portal provides explanatory notes today; it does not offer a released verifier package.
Adoption zero on the Developers pageWhat an external reader can inspect now
Read the architecture and the scope note, follow the dated source references and challenge the stated assumptions. The public reconstruction illustration uses synthetic data and does not execute the FxChain core. A private test result, a published explanation and a reproduction by an external reader are different kinds of evidence.
The claim ledger