What shows up before the word federated is used
Two countries are told they will share one token and one rulebook. A corridor is drawn as an open bridge. A validator map uses city names as if a regulator in that city runs the node. A tenant row on someone else's ledger is labeled a sovereign domain.
Those are the signs.
A federated Layer-1 is not one global ledger with many tenants on it. It is one hardened engine and many separate chains. JIL Sovereign Technologies Incorporated operates that engine at jilsovereign.net. A sovereign domain on it is the economy a licensee governs: a nation, a commodity desk such as oil or gold, an industry network, or a financial institution. The provisioned chain is a sovereign cell: its own chain-id, its own genesis, its own currency, and its own compliance policy. The cells share the software. They do not share a book, and neither domain writes the other's rulebook. The federation reading states the same split in the language of a constellation: same engine, separate sovereigns. Reach is shared. The right to refuse stays with the domain.
A corridor profile is a separate rule, and it is a plan. The eight-region fleet is not in service. Four regions are shown and four are shadow. The shadow regions are not named on this page. A profile names ten processes and spans at most two shown regions. A payment request on the recorded set still needs a yes from every active validator. The corridor uses the ACL. The claims are filed and patent pending.
That distinction is the difference between a national chain and a public lottery, which is the point of the named validators reading. Public networks recruit whoever brings hash power or stake. A minister cannot tell parliament that the people who finalized last night's settlement are unknown. A named validator is a legal identity the cell operator can name, a cryptographic identity pinned at genesis, and a place in a known set. On this fleet the operator of the recorded set is JIL Sovereign Technologies Incorporated. A validator named for a compliance zone is labeled for that zone. The label is not a claim that the machine sits in that zone. One hosting provider runs the fleet. No regulator operates a node, endorses a node, or has reviewed a node. The sovereign domain, federation, and original-layer readings record the worked example beside that fact: 10 in the set, 9 signing, all operated by JIL. The showcase at demo.jilsovereign.net/demo is a worked example. It is not a purchase, and it is not a handoff of the machines to a state.
What a domain keeps is stated on the sovereign domain reading. It keeps its currency, its rulebook, and its rate. Enforcement is written into consensus, on a core that JIL keeps hardened. Identity and KYC level, jurisdiction zone, sanctions status, per-transaction limits, and reserve policy are conditions of finality, not a report written after the transfer. The compliance engine fails closed. A missing fact, a sanctions match, a breached limit, or a missing attestation is a refusal with a reason. The ATCE reading is the longer account. The engine is built and tested. Measured 2026-11-12, the every-transfer rule is not in the validator image created 2026-08-21. That image can deny a crossing. Arming the later rule in another cell is done with that cell's operator. JIL does not author the rulebook. The cell operator publishes the policy. ATCE's job is to make the published policy the policy that executed.
Currency in a domain, on its sovereign cell, is a Digital Currency Platform instrument, not a stray contract. The platform treats a currency as a managed object: issuer, reserves, mint and burn, policy, and proof-of-reserve. Proof DEX is the launch and liquidity venue on the same Layer-1: ring-fenced pools, quarantined proceeds, staged release, and ProofGuard at the door. Proof comes before liquidity. Neither product is healthcare payment integrity. That work is the same company, JIL Sovereign Technologies Incorporated, at jilsovereign.com, and a different product.
Domains that need to pay each other do not merge their ledgers. A hop starts at the sovereign root. The corridor and corridor settlement readings give the fee and the checks. 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. The license is separate. The named payer pays the fee. A refusal settles no fee. Destination policy is re-checked on arrival. Releases on a governed corridor are dual-signed and protected against replay by a settlement identifier. A denied trade releases the escrow and settles no fee. Hubs and annexes cannot bypass their sovereign to trade externally. The oil annex on the worked example cannot open a corridor. The corridor reading also describes a second path, written in the style of an inter-chain packet: the destination would verify a header signed by more than two-thirds of the source validator power, plus a proof that the packet exists in the committed state. The federation reading says binding that light client to real ACL signatures is on the hardening roadmap, to be closed before a nation carries real value. That fraction is the written check of a path that is not yet bound to production signatures. It is not the live fleet's agreement rule. The live rule remains 100% of responding validators, and a halt if they diverge.
The commercial license for a sovereign root is Domain or Hub, set out on the licensing model and licenses readings. The November 7, 2026 operator paper sets a one-time setup license of $100,000 and an annual floor of $250,000, credited against JIL's share of collected transport fees. That paper is not an offer, a forecast, or a guarantee. Hubs and annexes have no extra charge. Depth is root, then hub, then annex. A hub under a hub is rejected. The Domain license, formerly Class A, is for a nation, a central bank, or a commodity consortium that holds its own root. The Hub license, formerly Class B, is for a regional hub or an institution, connected to a Domain. The public desks that illustrate those classes are not purchase claims.
The alternative a sovereign domain refuses is the pair of choices a ministry is usually offered. Rent a public chain, and the protocol will settle any valid signature, with compliance bolted on where it can be bypassed. Or build a chain from scratch: consensus, compliance, issuance, cross-border settlement, upgrades, key custody, and operations, estimated at forty to one hundred million dollars over three to four years. A sovereign domain is the licensed path between those two. A demonstration can be re-skinned in hours; issuance ships disabled until a licensing event, and a design target on a demo page is not regulatory approval.
JIL maintains the shared core. JIL does not custody the domain's banking. Within a domain the operator sets the rate. Between domains, JIL sets the rate. The retail wallet at getjil.com and wallet.getjil.com is a separate host. This page does not add it to the operation claim. Local licensed entities carry regulated activity in their own jurisdictions. Nothing in that structure is an offer of securities or virtual assets. The public canon in the company brief is 177 patent claims filed, patent pending and not granted, 9 trademarks filed and not registered, about 2.8 million lines of source, 350 or more production services, and 332 platform attestation checks.
Questions
Is a federated Layer-1 one chain that many countries share?
No. Each sovereign cell is its own chain, with its own chain-id, currency, and rulebook. What the cells share is the engine, not the ledger.
Who operates this one?
JIL Sovereign Technologies Incorporated (Delaware) operates jilsovereign.net under a license from JIL Sovereign Holdings, LLC (Wyoming). Holdings owns the software and does not operate the host. Technologies does not own the software. The wallet is not this page's product.
How do two domains settle?
A corridor hop starts at the sovereign root. The destination re-checks its own arrival policy. The fee is on the fee page. The license is separate. The named payer pays the fee. A refusal settles no fee.
What is the agreement rule?
Measured 2026-11-12, jil-mainnet-2 seals blocks with jil-abci-node under a third-party consensus engine. The image was created 2026-08-21. The signing set is eight, and a tip block sealed with six of those eight. The Attested Consensus Layer rule belongs to a separate binary that is not this process: six of ten with a verified enclave quote and a verified state-transition proof, eight of ten when those proofs are absent, and nine of ten when an inspection fails. Seven does not pass on that rule. A payment request, on that separate rule, still needs a yes from every active validator; one objection fails that request and the chain continues. JIL Sovereign Technologies Incorporated operates every validator. The chain is jil-mainnet-2. Measured 2026-11-12, ten hosts are operated by JIL and eight are in the signing set, permissioned and named. That is not Byzantine fault tolerance. A corridor profile is a separate plan. The eight-region fleet is not in service. Four regions are shown and four are shadow. The shadow regions are not named on this page. A payment request on the recorded set still needs a yes from every active validator. The corridor uses the ACL. The claims are filed and patent pending.
Is the domain demo a country that has joined?
No. The desks at demo.jilsovereign.net/demo are a worked example. NBR-S, GLD-S, OIL-S, and TMR-S are demonstration units in the fictional jurisdictions of Nubara and Tirmore. They are not purchase claims, and issuance on a licensed domain stays off until a licensing event.
Read with this
What is a Sovereign Domain, The federation, What is a corridor, An original Layer-1, Named validators, Digital Currency Platform, Proof DEX, How money moves.
