A sovereign domain is a gated garden. Anything leaving it goes through ATCE and a corridor. ATCE also runs inside the domain, between the root and its hubs and annexes.
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 ACL 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 neighboring nation can see inside your books.
Same engine, separate sovereigns. The Federation grants reach. Currency, rulebook, and the right to refuse stay with the domain. The commercial license is Domain or Hub.

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.
The domain demos
The Federation is not a diagram. The worked example is the domain demo showcase. Open it when you want to see a domain. These desks are simulated. They are not a purchase, and issuance on a licensed domain stays off until a licensing event.
- Ignition Switch is the capacity demonstration. The capacity lease is not published. demo.jilsovereign.net/demo/gas-exchange.html
- Nubara domain, currency NBR-S, is the Domain desk, in a fictional jurisdiction. Open the Nubara desk.
- Gold annex (GLD-S) and Oil annex (OIL-S) are annex desks. Gold. Oil. A corridor send from the oil site is refused.
- Tirmore domain, currency TMR-S, is the banking Hub desk, in a fictional jurisdiction. Open the Tirmore desk.
- L1 application and L1 record. Application. Record.
The menu for all of them is demo.jilsovereign.net/demo/. Regulatory-framework mentions on those desks are design targets, not licensure.
Status of the domain demos
The domain demos are a worked example, not a production national deployment. Binding the inter-cell light client to production ACL (Attested Consensus Layer) signatures is on the roadmap and is part of each sovereign domain's go-live. Measured 2026-11-12, ten hosts are operated by JIL and eight are in the signing set. Agreement is set per action. Measured 2026-11-12, a tip block sealed with six of the eight validators in the signing set. The process is jil-abci-node under a third-party consensus engine. The six-of-ten and eight-of-ten Attested Consensus Layer rule is a separate binary and is not this process. A payment request, on that separate rule, needs a yes from every active validator; one objection fails that request and the chain continues. A bridge withdrawal needs agreement from every responding validator. That is not Byzantine fault tolerance.
Domain, Hub, and Annex
The commercial license is a class, not a second engine. Domain and Hub license the same core. What differs is who the license is for. The published price is the same.
- Domain. The Domain license, formerly Class A, is for a nation, a central bank, or a commodity consortium that holds its own root. Setup is a one-time $100,000 and the annual floor is $250,000, credited against JIL's share of collected transport fees, the same for Domain and Hub, under the November 7, 2026 operator paper. That paper is not an offer, a forecast, or a guarantee. The corridor credential stays on the root.
- Hub. The Hub license, formerly Class B, is for a regional hub or an institution, connected to a Domain. Tirmore on the showcase is the worked example.
- Hubs and annexes. JIL does not charge for adding hubs or annexes. That price rule is not a validator count. A new hub under a hub is rejected.
How a foreign currency joins
Each stablecoin stands once as a Shared Resource, the only thing this site calls a Tier 2, with no hubs and no annexes, and each layer 1 has its own rules of engagement. Hosting scope is covered by the setup license and the annual floor in the November 7, 2026 operator paper; external interoperability and custom integration beyond approved provisioning are quoted separately, and those quotes are not per-hub fees. A root requests one layer 1 or one stablecoin once, and every hub and every annex under that root may then use it. The buyer root registers and enables the same asset; one root's setup does not enroll the other. An annex does not send on the corridor. The root does. A transfer can take several hops, and each settled JIL hop is billed at the corridor rate on the fee page. The list is Known networks and stablecoins. Ethereum bridge: the deposit path is Live and has run in production; the withdrawal path is Designed and awaits a key ceremony. No other chain or payment rail is connected.
ATCE retrieves the buyer stack, the seller stack, and the currency rules. A missing rule or a refusal stops the hop. The policy word is the policy name. The ATCE log stores the number. The policy table stores the version chains, write once, and the corridor journal stores the policy text and the transaction; both are Designed. A policy number is not a live foreign-network connection. Read The Corridor Journal.
An invitation to the constellation
The Federation is demonstrated on the domain demo showcase. A nation can keep its rules and still transact with its neighbor. 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 sovereign root is a licensing and provisioning engagement. The October 2026 white paper states the architecture and the license. The worked example is at https://demo.jilsovereign.net/demo/.
