A governed corridor
The corridor is a governed path between sovereign roots. The destination checks source identity and arrival policy. The release is dual-signed. A replay does not settle a second time.
Four steps
Escrow holds the gross and the fee. Verify checks origin proof, identity, the refusal list, and the cross-rate against the rate bands in the domain policy. Finalize requires both signatures: the sending hub's signature over the release, verified by the receiving cell against the hub key pinned in its own genesis. The receipt is the record. A denied trade releases the escrow and settles no fee.
The escrow is a reserved system account on the sending cell's ledger, not a bank account and not an account a person can spend from. The protocol moves it only on a verified send, release, or refund. JIL holds no fiat and no customer bank funds for a hop. Settlement is gross, leg by leg: there is no netting and no intraday liquidity facility. The rate source for the cross-rate is named in each domain's policy; JIL does not publish a market rate.
Who may send
The corridor credential stays on the root sovereign, and only after go-live. A hub or an annex cannot send on the corridor. Hubs and annexes cannot bypass their root to trade externally.
The fee
- 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.
- KYB and KYC come before corridor keys. Identity checks plug into the sovereign's national ID scheme or its approved KYC provider.
The rules, then the fee
A transfer can take several hops, and each settled JIL hop is billed at the corridor rate. An oil annex that needs USDC does not open the corridor itself; its root sends. A route of oil to ETH to USDC is three legs, and each JIL leg is billed separately, so the fee is at least 15 basis points across the route. That route depends on the InterOp router, which is Designed. The toll is not a substitute for the rules. ATCE rules each hop on the buyer root, hub, and annex, the seller root, hub, and annex, and the currency-site rule for each asset on the path. Both roots must have enabled each asset they use. A refusal stops the hop and is still written down.
The corridor journal is the full listing: policy text, when the entry was created, who bought what, who sold, the source of funds or of the commodity, the history of that source, and the buyer and seller ATCE accreditations. The ATCE log keeps only the policy number. The fee on this page is unchanged. The companion paper is The Corridor Journal.
Ignition is the other gate on a hop that leaves the domain. The demonstration proof refuses that hop unless the ignition switch is present. The published toll on this page is unchanged. The Ignition Switch page opens with the problem: a treasury cannot budget a toll that is sold to the highest bidder. The account is on the Ignition Switch page.
Questions people actually ask
Who sets the rate?
Within a domain the operator sets the rate. Between domains, JIL sets the rate under the published minimum. JIL records the hop and the proof. JIL does not custody the domain's banking.
Where can I see a hop?
The worked example at demo.jilsovereign.net/demo replays a recorded corridor send. That replay does not create a new settlement.
Keep reading
The white paper and a briefing are the next step if you are evaluating a sovereign.
