The core
A single hardened Layer-1, written from scratch for regulated finance.
The JIL L1 provides shared finality, interoperability, and the cryptographic foundation every cell runs on. JIL Sovereign Technologies Incorporated operates this Layer-1 host.
This is not a fork of Bitcoin, Litecoin, Ethereum, or any other existing ledger.
Sovereign domains
A locally governed economy. Chartered entities inside it keep local bylaws. The provisioned chain is a sovereign cell. The domain is connected to the federation and is not subordinate to it.
- Its own currency object, or several
- Local issuance and policy control
- Local compliance posture
- Connection to the federation for settlement between domains
A domain does not surrender its rulebook. It gains a common settlement and proof layer.
Settlement between domains
Movement inside a hub follows that sovereign's rules. Within a domain the operator sets the rate.
A corridor hop starts only from the initiating root. Four steps settle it:
- Escrow. The sending cell debits the sender into its corridor escrow, a reserved system account on that cell's ledger (
jil1ibcescrow). JIL holds no fiat and no customer funds in that step. The escrow is ledger state, moved only by protocol rules. - Verify. The sending cell's ATCE profile rules the departure: origin, identity of both parties, the refusal list, the per-asset limit, and the cross-rate against local bands.
- Finalize. Finalize carries two signatures: the sending hub's federation key signs a canonical release authorization, and the receiving cell's validators commit the release after verifying that signature against the hub key pinned in their own genesis and ruling the arrival under their own profile. A replay slot makes the release exactly once.
- Receipt. The receiver is credited out of the receiving cell's escrow float, and the ruling hash is recorded. A denied hop releases the escrow back to the sender and settles no fee.
The fee for a hop is a minimum of 5 basis points of settled gross, paid by the initiating root, 60 percent to JIL and 40 percent to the lessor. The full schedule, including the gas-block schedule inside a domain and a worked three-leg example, is on Fees.
Sanctions. The transfer control is the ATCE ruling. It denies inside consensus on the sanctions flag carried in each party's attested identity record. Consensus never calls a live sanctions list, by design, so every decision rests on facts the validators already agree on. The screen against current lists runs off chain in the attester service, and its result is signed into the identity record. The gas-block supervisor is a different control: it decides whether a gas block may benefit from fees (registration, KYC or KYB, a sanctions screen no older than seven days, approved regions, and no benefit in a sanctioned region). It runs at the gas-block service gate and in the demonstration meter, before any approval or payout. The ledger runs the supervisor too: a car registers with screening facts signed by the pinned attester key, the supervisor checks it before the lease and again at every block, and a car that fails takes no load and earns no toll. The capacity lease is not published on this site.
Proof is produced before value moves, not after. That ordering is the difference between an audit trail and a control.
License
Domain and Hub. The same core underneath both.
| Class | Who it is for |
|---|---|
| Domain | A Domain license, formerly Class A, for a nation, a central bank, or a commodity consortium |
| Hub | A Hub license, formerly Class B, for a regional hub or an institution, connected to a Domain |
| Hubs | JIL does not charge for adding hubs, spokes, or annexes. An eleventh hub is not a second license. See Fees. |
| Annex | A leaf. It contains nothing under it. |
Domain and Hub are the two licenses, with the same published price. They were called Class A and Class B in earlier papers. The structure words are Domain, Hub, and Annex, defined in the glossary.
A new hub under a hub is rejected. Depth is sovereign, hub, annex. The corridor credential stays on the root sovereign. KYB and KYC come before corridor keys.
ATCE
The Adaptive Trust, Compliance and Execution Engine.
ATCE evaluates identity, policy, and risk before settlement is allowed. The verdict on an act that stays inside the domain is a domestic ruling. The verdict on a hop that leaves the domain is a corridor ruling. JIL is trust first, then value movement. Compliance is not a report produced after the fact. It is a condition of movement.
On a corridor hop, ATCE addresses every layer. The buyer brings the root rules, the hub rules, and the annex rules. The seller brings the same three. When the movement uses a layer 1 or a stablecoin, that asset's rules on its Shared Resource apply as well. A transfer can take several hops. One oil-to-USDC route is oil, then ETH, then USDC, and each leg is its own hop and its own fee. A missing rule or a refusal stops the hop, and the refusal is still written down.
Each stablecoin stands once as a Shared Resource, a site for that one asset with no hubs and no annexes. It is the only thing this site calls Tier 2. A root registers once to use it, and that registration covers every hub and annex under that root. It does not enroll another root. A leaf may store a local allow and local limits. It does not rewrite the asset rule and it does not open a corridor. Only the root sends on the corridor. The list is Known networks and stablecoins.
ATCE applies in two layers. Anything that leaves the domain goes through ATCE and a corridor: that verdict is a corridor ruling. Inside the domain, between the root and its hubs and annexes, the verdict is a domestic ruling. No transfer moves value outside an ATCE ruling.
Before ATCE issues its final ruling it takes the result of an agentic review, which can hold a transaction even when every deterministic check is green. It cannot approve one the rules refuse. Its result is signed and recorded with the ruling.
JIL keeps the transaction record for 10 years from creation. It holds the ATCE rules that applied, the review result, the buyer and seller details including the KYB and KYC checks, and the ruling. It is write once, read many (WORM). JIL holds the record, not the chain. Each record has a unique hash, and the Layer-1 references the transaction by that hash. The chain carries no names, documents or KYC files. Each record is encrypted with its own key, so a lawful erasure destroys the key and leaves the hash: the body becomes unreadable and the chain reference stays valid. Anyone given the record can recompute the hash and compare it with the one the Layer-1 references. Storage for each domain is allocated when its license is signed.
The written procedure is shared with the licensee. A demonstration is not a live national deployment.
JIL sits above the chains and rails customers already use. It does not replace them. When a domain's rules do not allow a direct move, for example a site whose ATCE profile does not allow USDC, InterOp is designed to route the transaction through other sites whose rules do allow it. Every hop is ruled by ATCE and has its own reference hash, and the whole path is held as one write-once record.
The InterOp router is Designed. 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. Status for every capability is on the status ledger, and fees per hop are on Fees.
See what this looks like for your organization
Briefings are scoped to your jurisdiction, your license class, and the corridors you actually need.
