
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 PDFSummary
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.
| Generic public Layer-1 | Token on another chain | Own Layer-1 alone | JIL domain | |
|---|---|---|---|---|
| Whose law governs | The 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 rules | The 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 to | Its 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 transfer | No. 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 rails | Bridges, 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 record | The 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.
- Sovereign rulebook
- Ruling before movement
- Both counterparties ruled
- Decision as evidence
- Named attribution
- Record retention
- Cross-border settlement without a single hub
- Fit with incumbents
- Cryptographic durability
- Honest status
- Cost within reach
- Operability
Who it is for
- Nations and central banks that want their own digital economy under their own law.
- Banks and regulated institutions that need policy enforced before settlement and a record that survives its authors.
- Trade and commodity consortia whose members trade among themselves in many assets.
- Technical evaluators and capital partners who need to know exactly what is built.
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.
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.
- Live. jil-mainnet-2, ten validators operated by JIL Sovereign Technologies Incorporated, and is producing blocks. Measured 2026-11-12, eight validators are in the signing set and a tip block sealed with six of those eight. The process is jil-abci-node under a third-party consensus engine from the image created 2026-08-21. The rule that ATCE rules every transfer was committed on 2026-11-01 and is not in the validator image created 2026-08-21. That image can deny a crossing.
- Live. Hybrid Ed25519 and ML-DSA-65 attestation seals; both must verify. Validator signing is classical today, and post-quantum validator signing is on the roadmap.
- Live, in part. Ethereum bridge: the deposit path is Live and has run in production; the withdrawal path is Designed and awaits a key ceremony. No other chain or payment rail is connected.
- Built. Proof DEX, with nothing listed, and on-chain governance.
- Designed. The production record store, the InterOp router, pre-negotiated per-hop rates, sovereign-hosted validators, and a hardware security module for validator keys.
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.
