Not a shared chain. A nation of your own.
The instinct, on first hearing "one platform for many nations," is to picture a shared network -- a common ledger onto which each participant is admitted as a tenant. The Federation is the opposite of that arrangement, and the distinction is the whole point.
Each nation in the Federation runs its own chain. Its own currency. Its own validator set, on infrastructure it owns. Its own law, enforced inside consensus rather than promised above it. Its own treasury and its own cryptographic proof. What the nations share is not a ledger but an engine -- a single, hardened core, the same battle-tested BFT consensus and the same compliance-native execution running beneath every cell. Same engine; entirely separate sovereign networks. No foreign community governs your settlement, no shared operator can freeze your funds, and no neighbouring nation can see inside your books.
Same engine, separate sovereigns. You hold the keys, the currency, the validators, and the right to refuse -- the Federation grants you reach, never a landlord.
How sovereigns settle without a trusted middleman
Sovereignty that cannot transact is merely isolation. The harder achievement is letting two independent nations move value between them without either one surrendering its rules -- and without a shared intermediary that both must trust. The Federation offers two paths to this, and both re-check the destination's own compliance policy on arrival, so a nation never accepts inbound value that fails its own law.
Governed corridors
A federation corridor is a formally opened channel between two cells. The destination pins the source's identity and the exact arrival policy that inbound value must satisfy; releases are dual-signed, protected against replay by settlement identifier, and credited only after passing the destination's own in-consensus compliance gate, which anchors its decision for the record. A corridor is a diplomatic instrument rendered in cryptography: deliberate, auditable, and revocable.
Trust-minimized inter-cell settlement
The second path removes the intermediary altogether. In the IBC-style model, a destination cell accepts a cross-border packet only after it has verified, for itself, a header signed by more than two-thirds of the source nation's validator power, together with a mathematical proof that the packet truly exists in the state that header commits to. Value is escrowed at the source and credited at the destination; replays are refused by on-chain receipts; a relayer carries the headers and proofs automatically. No hub sits in the middle holding trust. Each nation verifies the other by mathematics, then applies its own arrival policy before crediting a single unit.
Two reference cells, already live and federated
The Federation is not a diagram. Two reference cells run today, each issuing its own regulated currency and federated to the other:
- The Nation 1 cell -- designed to a national virtual-asset regulatory framework, issuing the currency JN1, on chain jil-cell-demo-1. It runs the Managed tier (Tier I): JIL operates the cell on the nation's behalf, to its policy.
- The Nation 2 cell -- designed to a national monetary-authority regulatory framework, issuing the currency JN2, on chain jil-cell-demo2-1. It runs the Regulated tier (Tier II): local governance and local keys, with JIL maintaining the core.
Every validator in each cell carries a post-quantum identity -- ML-DSA-65 (Dilithium, FIPS 204) pinned at genesis -- a posture chosen for infrastructure meant to outlast the cryptography of its founding decade. The regulatory framings are illustrative reference postures for demonstration; they are not statements of a signed national programme.
Stated plainly, in candour
Prestige is worth nothing without honesty, so the line is drawn precisely. The two reference cells are single-node today. Binding the inter-cell light client to real CometBFT consensus signatures -- and running true multi-host Byzantine fault tolerance in production -- are on the hardening roadmap, to be closed for each nation's deployment before go-live. What is demonstrated is demonstrated; what is roadmap is named as roadmap. A sovereign engagement is, in practice, the disciplined work of closing that short list on top of a proven base.
Three ways to hold the crown
How much of the machinery a nation operates itself is a matter of tier, not of capability. Every tier licenses the same engine, the same in-consensus compliance, the same currency platform, and the same federation transport; what shifts is who runs the infrastructure and how much regulatory scaffolding is included.
- Managed -- JIL operates the cell on the sovereign's behalf. The fastest path to a working, federated chain; suited to pilots and to institutions without a standing blockchain operations team.
- Regulated -- a co-operated, regulator-facing configuration. The sovereign owns its policy and its keys; JIL supports operations. The natural fit for a central bank or authority that requires its own custody and a full audit posture.
- Full Sovereign -- the nation runs its own validators, holds its own keys, and conducts its own operations on infrastructure it owns. JIL licenses and supports. Complete operational independence, for a nation that will accept nothing less.
An invitation to the constellation
The Federation begins with two. The two reference cells are live, issuing currency, and settling with one another across a governed corridor today -- a working proof that a nation can keep every one of its rules and still transact with its neighbour. The architecture is designed for the third nation, and the tenth, and the fiftieth: each a sovereign of its own economy, none a tenant of anyone else's.
Standing up a new nation's cell -- genesis ceremony, post-quantum identities, currency object, compliance policy, certification, and federation -- is a matter of provisioning, not of a multi-year build. Two reference cells are live. Your sovereign cell is about two weeks from deployment.