Home · Learn · Federation corridor

What is a corridor

A corridor is a governed channel between two sovereign domains. Each domain keeps its own chain and its own rulebook, and the hop starts at the sovereign root. JIL Sovereign Technologies Incorporated (Delaware) operates this host. JIL Sovereign Holdings, LLC (Wyoming) owns the software and does not operate the host. This page is not a token sale.

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. The verdict on an act that stays inside the domain is a domestic ruling. The verdict on a hop that leaves the domain is a corridor ruling.

Settlement without surrender

A nation that cannot transact with its neighbor is isolated. A nation that transacts on a shared public chain has rented someone else's rulebook. The JIL Federation is built for the third case: each member keeps a sovereign domain, and a corridor hop starts at the sovereign root. A corridor hop costs a minimum of 5 basis points of settled gross, paid by the initiating root, with 60 percent to JIL and 40 percent to the lessor. Inside a domain the operator sets its own rate. The capacity lease is not published on this site. The toll schedule, who pays, and a worked example are on the fee page. Local control. Shared finality. Proof on every movement.

The instrument that makes that possible is the federation corridor.

A corridor is opened on purpose, dual-signed, and revocable. It is not a bridge left ajar.

What a corridor is

A corridor is a formally opened channel between two cells. Before a unit of value is credited at the destination:

Neither domain surrenders its rulebook. The source does not get to write the destination's arrival policy. The destination does not get to mint the source's currency. Inter-cell settlement is an exchange of cell-native units at a negotiated rate, with KYC and KYB traveling with the transaction. Both sides can reject.

The second path: trust-minimized headers

Alongside governed corridors, the architecture includes trust-minimized inter-cell settlement in the IBC style. The destination verifies, for itself, a header signed by more than two-thirds of the source nation's named validator power, plus a proof that the packet exists in the state that header commits to. Value is escrowed at the source and credited at the destination. A relayer carries headers and proofs. No hub sits in the middle holding trust.

Binding that light client to production ACL (Attested Consensus Layer) signatures, and running true multi-host BFT on each cell, are part of a sovereign domain's go-live. The domain demos show the corridor model. Issuance on a licensed domain begins at the licensing event.

The worked example

The Domain desk is Nubara, with gold and oil annexes under it. The Hub desk is Tirmore. Both are fictional jurisdictions in a demonstration, not licensed national programs. Open demo.jilsovereign.net/demo.

The rules a hop must retrieve

A hop is allowed only when every rule that applies allows it. The buyer brings the root rules, the hub rules, and the annex rules. The seller brings the same three. When the movement uses a layer 1 or a stablecoin, that asset's rules on its Shared Resource site apply as well. A root enables a Shared Resource once, and that covers every hub and every annex under it. The buyer root enables the same asset. 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. Apart from the Ethereum bridge deposit path, nothing on that list is a live connection.

On jil-mainnet-2 the Attested Consensus Layer seals each block for the ten JIL-operated validators: six of ten with a verified enclave quote and a verified state-transition proof, or eight of ten without them. A payment request, on that separate rule, needs a yes from every active validator; one objection fails that request and the chain continues. The eight-region fleet is a later plan: four regions are shown and four are shadow, and a corridor profile on that plan names ten processes and spans at most two shown regions. The seller ATCE elects where a model may run; the buyer list does not, and an empty seller list allows no model. Open the Nubara desk rules to see the worked example. The desk does not call a model and does not poll a chain.

This Layer-1 host

Corridors, named validators, the Digital Currency Platform, and Proof DEX are Layer-1 products on jilsovereign.net, operated by JIL Sovereign Technologies Incorporated. Payment integrity is the same company, JIL Sovereign Technologies Incorporated, at jilsovereign.com and is a different product. The wallet is a separate host at getjil.com.

Read the Federation for the constellation, and the runbook for how a new cell joins it.