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 local bands. Finalize requires both signatures. The receipt is the record. A denied trade releases the escrow and settles no fee.
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 sovereign to trade externally.
The fee
- Movement inside a hub is 0 basis points
- A settled hop is 5 basis points of settled gross, paid by the initiating sovereign
- The fee is escrowed with the gross and routed to the network treasury on finality
- KYB and KYC come before corridor keys. Onfido is supported where the configuration allows it
Questions people actually ask
Who sets the rate?
The sovereign operator sets the rate on that book. JIL records the hop and the proof. JIL does not set the rate and does not custody the banking.
Where can I see a hop?
The worked example at 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.