Two familiar choices, both unworthy of a sovereign
A nation or a regulated institution that wishes to settle value on a blockchain has, until now, been offered only two paths - and each asks it to surrender something it cannot afford to give up.
The first is to rent a public chain. A public network such as Ethereum grants programmability and a large developer ecosystem, but it is governed by an anonymous, global community, subject to no jurisdiction, and deliberately blind to policy: it will settle any validly signed transfer between any two addresses. Compliance - identity, sanctions, transfer limits - can only be layered on top, in an application or an off-chain gatekeeper, where it can be bypassed, forked, or simply ignored. A regulator can never obtain, from the protocol itself, the assurance that a prohibited transfer is impossible, because the protocol holds no concept of prohibition.
The second is to build a chain from scratch. This restores control, but at a price few ministries or central banks can bear: a consensus engine, a virtual machine, a compliance layer, currency issuance, cross-border settlement, upgrade tooling, key custody, and a continuous operations fabric - each a specialist discipline, together a program of roughly forty to one hundred million dollars over three to four years, with a high failure rate and no ecosystem to inherit.
The sovereign domain is the answer to an institution that concludes, rightly, "we need our own economy and our own chain, and we cannot build the chain."
The third path: your own chain on a shared core
A sovereign domain collapses the multi-year build into a provisioning exercise. The chain underneath it is a sovereign cell: a distinct, self-governing blockchain - its own chain identity, its own genesis, its own validators, its own currency, its own rulebook - provisioned upon the shared JIL Core. "Shared core" means the same proven engine, never the same chain: every cell runs the identical software, yet each is a separate network under the exclusive command of its operator.
That engine pairs two well-understood technologies. ACL (Attested Consensus Layer) provides attested consensus consensus - standard, production-class agreement, not novel cryptography a state must accept on faith. Above it sits a deterministic Rust application that executes transactions and commits state so that every node agrees on a single hash at every block. The current source adds no general-purpose virtual machine: the native operation set covers transfers, currency issuance, corridors, and evidence.

Compliance native to consensus
The single property that sets a Sovereign Domain apart from any public chain is that the rulebook lives inside the protocol, not above it. Identity and KYC level, jurisdiction zone, sanctions status, per-transaction limits, and reserve policy are evaluated within consensus as a condition of finality. The compliance engine fails closed: an action that breaches policy is not settled, and its rejection carries an explicit, auditable reason - identity below the required level, over limit, sanctions match, missing attestation.
Movement across jurisdiction zones is denied by default. The result is a rulebook that lives inside the protocol, so the state's rules are never optional.
The essence of a domain
A sovereign domain keeps its currency, its rulebook, and its rate. The recorded validator set on this fleet is operated by JIL. Enforcement is written into consensus, on a core that JIL keeps hardened.
Currency issued under the rulebook
On its sovereign cell, an authorized issuer may bring a regulated digital currency into being - a stablecoin or a CBDC-adjacent instrument - defined by a currency object that names its issuer, its authorities, its maximum supply, and the very policy that governs it. Every mint is issuer-signed; every transfer passes the same in-consensus compliance gate. The instrument therefore cannot move to an ineligible or sanctioned holder, because the protocol itself refuses the transfer. A reserve reference may be pinned on-chain, so that backing is a matter of record rather than assertion.
Domains that trade
A sovereign domain need not stand alone. Two domains, whether nations, commodity desks, or industry networks, may settle between them across governed inter-state corridors. Neither surrenders its rulebook to a shared intermediary: incoming value is re-examined against the destination's own arrival policy before it is credited, and cryptographic proof of the source's finality is verified rather than trusted. Each state keeps its rules; value still crosses the border.
The license, and a core JIL keeps hardened
Standing up a sovereign root is a Domain or Hub licensing engagement. The October 2026 white paper states the architecture. The November 7, 2026 operator paper states the commercial framework. 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 domain demos are the worked example at https://demo.jilsovereign.net/demo/. The desks are set in fictional jurisdictions and are not a purchase claim. Measured 2026-11-12, ten hosts are operated by JIL and eight are in the signing set. That is not Byzantine fault tolerance.
