Skip to content
JIL Sovereign crestJIL SOVEREIGNSovereign Layer-1 · Institutional Rail
Architecture

Written from scratch for regulated finance.

One original Layer-1 core, with sovereign domains above it. Not a fork of Bitcoin, Litecoin, Ethereum or any other ledger, because accountability cannot be bolted onto an inherited foundation.

Request an executive briefing
The federation

One core. Many sovereigns.

The core provides shared finality, interoperability and the cryptographic foundation for every cell. Sovereign domains sit on top of it, each with its own rulebook.

TIER 1

Sovereign root

A nation, central bank, commodity consortium, industry network or financial institution. Only the root holds the corridor credential.

LEVEL 2

Hub

A regional hub or institution connected to a domain, holding annexes beneath it. A hub under a hub is rejected.

LEVEL 3

Annex

A leaf under a hub or root: a commercial bank, a gold vault, an oil terminal. Annexes are unlimited.

TIER 2

Shared Resource

One site per stablecoin or external Layer-1, with no hubs or annexes. A root registers once for all of its domain.

Sovereign cells

Same engine. Separate ledgers.

A domain's provisioned chain is its sovereign cell, with its own genesis and its own ledger, running the same engine as every other cell. A domain stays connected to the federation without being subordinate to it.

Currency Objects are native managed instruments, not smart contracts. The ledger has no general-purpose virtual machine, which removes an entire class of contract exploits.

  • Own genesis and ledger per domainCELL
  • Native Currency Objects, no general-purpose VMINSTRUMENTS
  • Original Rust implementationENGINE
  • Fixed three-level hierarchySTRUCTURE
Corridor settlement

Four steps, exactly once.

I

Escrow

The sending cell debits the sender into a reserved system account. Escrow is ledger state, changed only by protocol rules.

II

Verify

The sending cell's ATCE profile checks origin, both parties' identity, the refusal list, the per-asset limit and the cross-rate against local bands.

III

Finalize

The sending hub's federation key signs a canonical release. Receiving validators verify it against the hub key pinned in their own genesis. A replay slot ensures it executes once.

IV

Receipt

The receiver is credited from escrow float and the ruling hash is recorded. A denied hop returns the escrow, and no fee is charged.

Evidence by design

The chain holds the proof. Not the personal data.

Each ruling produces a unique SHA-256 hash that binds the profile, both parties' records, the review result and the outcome. The Layer-1 holds only the hash. Names, documents and KYC files stay in an encrypted record, each with its own key.

A lawful erasure destroys that record's key and leaves the hash intact, so privacy law and evidentiary integrity no longer conflict. Anyone holding a record can recompute its hash and compare it to the ledger.

SHA-256ruling hash on the Layer-1
1 keyper record, destroyable on lawful erasure
10 yearswrite-once record retention
0names or KYC files on chain
Begin with a briefing

See the architecture in a technical briefing.

For CTOs and architects: consensus, cells, corridors, records and the migration path to post-quantum validator signing.

Request an executive briefing