Home · Learn · Federated Layer-1

What is a federated Layer-1?

Many sovereign cells, one shared engine. Each cell keeps its own chain, currency, and rulebook. Value crosses only on a governed corridor, and the live validator set is operated by JIL.

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 cell.

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, Inc. operates that engine at jilsovereign.net under the license from JIL Sovereign Holdings, LLC (WY). A sovereign cell on it is a nation's or an institution's own chain: 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 cell 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 cell.

The company brief names what was built, and the original Layer-1 reading says it in one place. The ledger, the virtual machine, the compliance engine, the currency platform, and the proof layer are original engineering. No existing blockchain was forked. Consensus is the Attested Consensus Layer, ACL, with Ring 0 pure core determinism. The agreement rule is 100% among responding validators, and the chain halts if those responses diverge. The live fleet is 10 validators. All of them are operated by JIL. The set is permissioned. Operators are known at genesis. This is not anonymous mining, and it is not Byzantine fault tolerance.

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. Eight of the named ten must vote yes. Seven does not pass. Silence is not a yes. That bar does not replace agreement among responding validators on the recorded set. 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, Inc. A validator named for a compliance zone is labelled 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 cell, 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 cell keeps is stated on the sovereign-cell 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. It is honest about scope: the engine is built and tested, arming it in live consensus is opt-in per cell, and it is not already switched on for every deployment. 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 on a 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, Inc., at jilsovereign.com, and a different product.

Cells 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. Movement inside a hub is 0 basis points. A settled hop is 5 basis points of settled gross, paid by the initiating sovereign. 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 Class A or Class B, set out on the licensing model and license classes readings. Class A is $2,500,000 to join and $400,000 a year. Class B is $1,500,000 to join and $250,000 a year. Up to 10 hubs are included. A hub past that is $25,000 a year on the sovereign, and that fee is not a second license. An annex license is $0. Depth is sovereign, then hub, then annex. A hub under a hub is rejected. The paper names Class A for global commodities and tier 1 nations, and Class B for regional hubs and philanthropic desks. The public desks that illustrate those classes are not purchase claims.

The alternative the sovereign-cell reading 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, a virtual machine, compliance, issuance, cross-border settlement, upgrades, key custody, and operations, on the order of forty to one hundred million dollars over three to four years. A sovereign cell is the provisioning path between those two. It is still a license and a deployment runbook, not a slide. A demonstration can come up in hours from an input sheet. Issuance ships disabled. A demo is not a national currency, and a design target on a demo page is not regulatory approval. how money moves is the plain-language companion if the question is why a cross-border payment takes days when each nation keeps its own ledger. The Federation Thesis is the long engineering argument, including what is not built yet.

JIL maintains the shared core. JIL does not custody the cell's banking and does not set the rate. The rate stays on the sovereign's book. JIL Sovereign Holdings, LLC (Wyoming) owns the intellectual property and licenses it. Holdings does not operate this site. 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, Inc. operates jilsovereign.net under the license from JIL Sovereign Holdings, LLC (WY). Holdings licenses the IP and does not operate the site. The retail wallet is a separate host.

How do two cells settle?

A corridor hop starts at the sovereign root. The destination re-checks its own arrival policy. Movement inside a hub is 0 basis points. A settled hop is 5 basis points of settled gross, paid by the initiating sovereign.

What is the agreement rule?

100% agreement among responding validators, and a halt if they diverge. The live fleet is 10 validators, all operated by JIL, permissioned and named. That is not Byzantine fault tolerance. A corridor profile is a separate plan. Eight of the named ten must vote yes. Seven does not pass. Silence is not a yes. 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. That bar does not replace agreement among responding validators on the recorded set. The corridor uses the ACL. The claims are filed and patent pending.

Is the cell demo a country that has joined?

No. The desks at demo.jilsovereign.net/demo are a worked example. UAE-S, GLD-S, OIL-S, and INR-S are demonstration units. They are not purchase claims, and issuance on a licensed cell stays off until a licensing event.

Read with this

What is a sovereign cell, The federation, What is a corridor, An original Layer-1, Named validators, Digital Currency Platform, Proof DEX, How money moves.