What original means
The ledger, the compliance engine, the currency platform, and the proof layer are original engineering. The current source of the Layer-1 has no general-purpose virtual machine. The fleet is ten validators, all operated by JIL. Agreement is set 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 objection fails that request and the chain continues. A bridge withdrawal needs agreement from every responding validator. That is not Byzantine fault tolerance. Attestation seals are hybrid post-quantum (Ed25519 plus ML-DSA-65). Post-quantum validator signing is on the roadmap.
Why not a fork
A fork inherits old design limits: anonymity-first ledgers, bolted-on compliance, or a global policy you do not control. JIL was written for regulated finance, local monetary autonomy, and cross-border settlement with accountability.
What you license
You license the core. You govern the domain. The provisioned chain is a sovereign cell. Issuance, policy, and day-to-day operations stay local.
In practice
- ~2.8M lines of source
- 350+ services
- Not a fork of Bitcoin, Litecoin, Ethereum, or any other chain
- The same core under Domain and Hub
Questions people actually ask
Where does the ~2.8M figure come from?
Public copy uses ~2.8M lines of source and 350+ services. It counts authored source rather than generated output or vendored dependencies.
Can I run my own validators?
Measured 2026-11-12, ten hosts are operated by JIL and eight are in the signing set. A Domain or Hub license does not move custody of the domain banking to JIL.
Keep reading
The white paper and a briefing are the next step if you are evaluating a domain.
