Evaluate FxChain
Read the architecture, inspect the evidence, and understand the current integration boundaries. Public execution tools follow their own release gates.
Start with the foundations
Assurance closure: 2026-09-28. Native delivery: 13 October 2026, formal acceptance pending. These dated records support different subjects and do not certify a public SDK.
Read the native architecture
FxChain is a native blockchain protocol. Its public dossiers explain the intended responsibilities and the bounded local foundations already examined; the dated evidence records their checks.
Inspect a precise evidence scope
Read what was examined, by which method and with which limits. Separate reconstruction paths support a local comparison; they do not establish an external audit or your own reproduction.
Evaluate an integration boundary
Compare your required inputs, effects and recovery cases with the qualified local profiles. Connector integration and a usable public SDK need their own evidence.
A planned route to offline verification
The first planned developer tool is a self-contained verifier. The architecture programme’s adoption-zero stage connects offline verification, portable denials, causal accountability and evidence packages, intended to let builders examine published material on their own machines.
Concretely: a small offline verifier, as a command-line tool and a browser build, that checks a capsule, a receipt, a portable denial and the committed inputs of a verdict against declared rules and expected commitments on your machine. Later rungs - an institutional evidence SDK, private supervisory nodes, sovereign execution only where necessity is measured - come after it, each behind its own gate.
This page offers the explanation and scope notes, rather than a runnable verifier or an installation command. A released package would need a version, trusted reference commitments, usable instructions and its own reproduction evidence.
What opens with the developer preview
These planned interfaces are directions, rather than active links or a public integration offer.
docs.fxchain.network
Documentation and specifications
SDK and client libraries
Typed access to FxChain deployments
Testnet, faucet and explorer
Public experimentation surfaces
api / rpc endpoints
Programmatic access to networks
These reserved surfaces follow the developer-preview path. Explore their architectural foundations through the dossiers and the organ anatomy.
Bring one workflow and one failure case.
Describe the inputs you control, the effects you need to bound and the recovery cases you want to evaluate against your existing procedure.