JIL Sovereign crowned shield logo

White paper. Edition 3, November 1, 2026, revised November 9, 2026. Supersedes the October 16, 2026 edition.

Trust First, Then Value Movement

How sovereigns and institutions can settle across borders under their own rules, with a ruling and a record before value moves.

Published by JIL Sovereign Technologies Incorporated, operator of this Layer-1 host. Author: Jeffrey Anthony Mendonca, Dallas, Texas. Patent pending.

Download the PDF

Summary

JIL Sovereign is an original, fully permissioned Layer-1, engineered from scratch for central banks, commodity consortia, and regulated clearing houses. It is not a fork of Bitcoin, Ethereum, or an older ledger. Each sovereign domain is self-governing: its currency, its bylaws, and its books. Licenses and settled corridor hops fund operations, and the design does not print a token to pay for them. Self-sustaining operation is a design goal reached above a stated volume; it is not a timetable.

Pricing is a license (Domain or Hub, the same published price: a one-time $100,000 setup and a $250,000 annual floor, credited against JIL's share of collected transport fees) and a minimum of 5 basis points of settled gross per settled corridor hop, paid by the initiating root, 60 percent to JIL and 40 percent to the lessor. The license and the toll schedule, including a worked three-leg example, are on Fees. The capacity lease is not published. A block holder does not receive a domain's data and does not receive a governance right. Sanctions are ruled inside consensus on the attested sanctions flag of each party; the screen against current lists runs off chain in the attester, which signs the result into the identity record.

JIL is trust first, then value movement. A movement is ruled before it settles, and the ruling is kept. JIL is an original, permissioned, federated Layer-1. A licensee governs a sovereign domain: a nation, a commodity consortium, an industry network, or a financial institution. It has its own constitution, chartered entities, and local bylaws. The provisioned chain is a sovereign cell. ATCE, the Adaptive Trust, Compliance and Execution Engine, rules every transfer before value moves. A movement that stays inside the domain takes a domestic ruling. A hop that leaves the domain, the cross-border path, takes a corridor ruling. Both counterparties are ruled. JIL does not replace a central bank, a currency, or a legal framework. The licensee governs the domain.

This edition follows a stated structure: context and the problem, the paradigm shift, evaluation criteria, the architecture, evidence and trade-offs, a roadmap with gates, the business model, and formal references.

Every other Layer-1 sits inside one rule set and one jurisdiction. A sovereign domain keeps its own law and shares one institution and its corridors with the other domains, as member states do in a multilateral body. This is an analogy of structure only, and JIL is not affiliated with any multilateral institution.

Context and the problem

Cross-border value movement depends on a few correspondent hubs, and a hub can be closed by a party the originator never chose. Compliance is mostly a report written after value has moved. Two choices follow: rent a public chain, where any validly signed transfer can settle, or build one from scratch at a cost few ministries can bear. The paper sources what it can and says plainly where a number could not be sourced.

The paradigm shift

An act of value is ruled before it exists, and the ruling is kept. A sovereign domain is a gated garden. The verdict on an act that stays inside the domain is a domestic ruling, and a hop that leaves the domain is a corridor ruling, on both counterparties. Before the final ruling an agentic review can hold an act. JIL keeps the record, write once, with a unique hash that the chain references. The chain carries no names, documents or KYC files; those stay in the encrypted WORM record.

Many laws, one institution

Every Layer-1 in wide use today sits inside one rule set and one jurisdiction: the protocol's, its validators', and its foundation's. A group that wants a common ledger can issue a token on someone else's chain and be bound by that chain's rules and jurisdiction, or build its own Layer-1 and be bound to another chain, another jurisdiction, or both, to reach anything outside. A consortium of oil-producing states that wanted a common Layer-1 for oil would face exactly this choice. Public chains such as Bitcoin and Ethereum are generic. Rules are not part of their protocol, which is right for open settlement and is the limit for a member that must apply its own law.

JIL was built the other way. Every domain operates like its own country with its own laws: its own currency, identity requirements, limits, zone rules, regulator, and a ruling by ATCE before anything settles. Each domain's law comes from its own jurisdiction, and JIL does not grant sovereign status to anyone. The domains share one institution and corridors between them, much as member states keep their own law inside a shared multilateral institution.

That comparison is an analogy of structure only. Member states keep their own law inside a shared institution, as they do in the World Bank. JIL is not affiliated with the World Bank or any multilateral institution. JIL is not a multilateral lender and does not lend to or act for any domain.

Who a chain answers to matters as much as what it runs. A common public Layer-1 is its own governing body, and in practice it stays answerable to exchange listings and liquidity, or to a foundation or a consortium it did not choose. A sovereign domain answers to its own jurisdiction. Its law and its listing decisions are its own. The home chain validators are operated by JIL Sovereign Technologies Incorporated. A domain does not operate them.

In the setup portal demonstration a domain defines its own stablecoin in a few steps: the currency, the reserve model, and the limits. The portal is a demonstration. Currency Objects are Live, issuance is disabled, and live issuance begins only after the license. A re-skin of the demonstration cell with a customer's names, language, and domain is measured in hours; that applies to the demonstration only. A pilot cell is designed for technical readiness in about 30 days after its policies are pinned. Licensing and regulatory approvals are separate and are not included. A customer-hosted cell under the Regulated profile of the cell deployment runbook is Designed.

Many laws, one institutionOn a generic Layer-1, or a token on one, every member sits inside one rule set and one jurisdiction. In JIL, each domain keeps its own currency, regulator, identity rules, limits and zone rules, and the domains share one institution and corridors between them. The comparison to a multilateral institution is an analogy of structure only.Generic Layer-1, or a token on oneOne rule set, one jurisdictionSet by the protocol and its validatorsMember AMember BMember CJIL: many laws, one institutionDomain AOwn currencyOwn regulatorOwn identity lawOwn limits, zonesDomain BOwn currencyOwn regulatorOwn identity lawOwn limits, zonesCorridorruled twiceShared institutionOne engine and one record standard.Corridors between any number of domains.Corridors: live in reference domainsAnalogy of structure only.Not affiliated with any multilateral institution.
Figure 1. Many laws, one institution. On a generic Layer-1, or a token on one, every member sits inside one rule set. A sovereign domain keeps its own law and shares one institution with the others. An analogy of structure only.
Generic public Layer-1Token on another chainOwn Layer-1 aloneJIL domain
Whose law governsThe protocol's rules and its validators' jurisdictions.The host chain's rules and jurisdiction.Its owner's, plus the law of any chain it joins.The domain's own jurisdiction. A corridor adds the other domain's rules.
Who sets the rulesThe protocol and its governance.The host chain. The issuer sets only the token.The chain's owner.The domain, in its own ATCE profile.
Who the chain answers toIts own governance, shaped in practice by exchange listings and liquidity, or by a foundation or consortium.The host chain's governance, and the venues that list the token.Its owner, and the chains and venues it needs to reach.The domain's own jurisdiction. Its law and its listing decisions are its own. The home chain validators are operated by JIL Sovereign Technologies Incorporated
Can a member refuse a transferNo. Any valid signature settles.Only inside the token contract.Yes on its own chain. Not on chains it reaches.Yes. ATCE rules both sides before settlement.
How it reaches other chains and railsBridges, which are separate systems.Bridges, which are separate systems.It builds each bridge itself.Corridors between JIL domains: Live on reference domains. Ethereum deposit path: Live. Ethereum withdrawal: Designed. Other chains and rails through InterOp: Designed.
Who keeps the recordThe public ledger.The host chain's ledger.The chain's owner.The chain holds a hash. JIL holds the record, write once. Writer: Live. Production store: Designed.

Evaluation criteria

Any solution for sovereigns and institutions should be measured against the same twelve criteria. The paper then scores JIL against each, with a status marker.

  1. Sovereign rulebook
  2. Ruling before movement
  3. Both counterparties ruled
  4. Decision as evidence
  5. Named attribution
  6. Record retention
  7. Cross-border settlement without a single hub
  8. Fit with incumbents
  9. Cryptographic durability
  10. Honest status
  11. Cost within reach
  12. Operability

Who it is for

Who it is not for

Anyone who needs a permissionless or open-validator chain, Ethereum tooling, a token to buy, custody of reserves, a replacement for a central bank, a decentralization claim, or a live customer reference. No token sale is running, and JIL.ai tokens have already been given to participants.

The blueprint

Four diagrams show the architecture. The full paper explains each one and states what is built.

The domain tier modelA Tier 1 sovereign root holds hubs at no license charge, and each hub holds annexes at no license charge. Depth is root, hub, annex. A Shared Resource is the only Tier 2: one stablecoin, with no hubs and no annexes. Only the root sends on the corridor.Tier 1 sovereign rootDomain or Hub license. Only the root sends.Hubno license chargeHubno license chargeMore hubsno license chargeAnnexno license chargeAnnexno license chargeAnnexes areunlimitedDepth: root, hub, annex. No hub under a hub.Beside the treeShared ResourceTier 2, one stablecoin.Registered once.Another rootReached by corridor.Live in reference domains. No licensed domain yet.The provisioned chain is a sovereign cell.
Figure 2. The domain tier model. The Domain license and the Hub license were called Class A and Class B in earlier papers.
The two ATCE layersA sovereign domain is a gated garden. Inside the domain, the ATCE verdict is a domestic ruling on each movement between the root and its hubs and annexes. A hop that leaves the domain is a corridor ruling, ruled on departure and again on arrival.Sovereign domain ARootAnnexDomestic ruling inside the domainSovereign domain BRootAnnexDomestic ruling inside the domainCorridor rulingruled on departureand again on arrivalLive on jil-mainnet-2No legacy transfer moves value outside an ATCE ruling.
Figure 3. The two ATCE layers: a domestic ruling inside the domain, and a corridor ruling between domains, on every transfer.
A transfer from act to recordAn account-to-account transfer starts at the customer site. The attester supplies signed identity records for both accounts. ATCE rules the act on both counterparties and the per-asset limit; a denial ends the path and the denial is recorded. Before the final ruling the agentic review may hold the act but cannot rescue a denial. The final ruling has a unique hash. JIL holds the full record and the chain references the hash.1 Customer siteAccount A sends to account B.2 AttesterSigned records for A and B.Live3 ATCE rulingBoth parties and the limit.LiveBoth allow?NoDeniedNothing moves.Hash H recorded.Yes4 Agentic reviewCan hold, not rescue a denial.LiveHold?YesHeldA person decides.No5 ATCE final rulingUnique hash H over the record.Live6 JIL record writerFull ruling and review.Writer: LiveStore: Designed7 Layer-1 chainHolds hash H only.LiveValue moves only on an allow ruling.
Figure 4. A transfer from act to record, one party per step. The attester, the agentic review, and the record writer were not confirmed on the validator image created 2026-08-21. The production record store is Designed.
A multi-hop path, shown as an illustrationOIL01, a consortium of oil-producing states, cannot pay in USDC directly because its profile refuses it. The InterOp router finds legal paths, and the agentic selector chooses among them. The path runs through RICE01, which holds USDC, to the USDC rail. Each hop gets its own ATCE ruling and hash, and JIL holds one parent record that lists the hop hashes.Illustration. Domains and rails are examples.1 OIL01Wants to pay in USDC.Direct path ok?YesSettles directlyOne hop.No: OIL01 profile, USDC limit 02 InterOp routerPlans paths between domains.Designed3 Agentic selectorChooses among legal paths.Can drop one. Cannot add one.DesignedOIL01originRICE01holds USDCUSDC railnot connectedDesignedHop 1ruling + hash H1Hop 2ruling + hash H2Also legal: the same path through CORN02.H1, H24 Parent path record (JIL)Write once. Lists H1 and H2.No names or KYC files on chain.Writer: Live. Store: Designed.Fee: 5 bps per settled JIL hop.Rates are agreed in the license.
Figure 5. A multi-hop path through two domains, shown as an illustration. Designed, not built.

Status on 2026-11-09

Three markers, used on every page of this site: Live runs on jil-mainnet-2 today, Built is merged and tested and is not the process sealing blocks, Designed is written down and not built. The full ledger is on the status page.

The agreement rule is stated per action. Measured 2026-11-12, a tip block sealed with six of the eight validators in the signing set. The process is jil-abci-node under a third-party consensus engine. The six-of-ten and eight-of-ten Attested Consensus Layer rule is a separate binary and is not this process. A payment request, on that separate rule, needs a yes from every active validator, one that answered in that round; one objection fails that request and the chain continues. A bridge withdrawal needs agreement from every responding validator. This is not Byzantine fault tolerance against the operator. Keys, halt and upgrade authority are on Control and custody.

Johanson Group LLP is examining SOC 2 Type 1. Trust Services Criteria in that examination are Security only. No report has been issued. SOC 2 Type 2 and the HIPAA examination are not started. HITRUST r1 has no external assessor and no report. Section 10 of the paper lists the claims JIL does not make.

Read the paper

This page follows the language chosen on the site. The PDF download is the English edition, revised 2026-11-09. A briefing covers the license, the security as-built, and a pilot cell design.