Anonymous chains cannot answer a minister
Public networks recruit whoever brings hash power or stake. The people who finalize a block are, by design, hard to name. That is a feature if the product is censorship resistance for unknown users. It is a defect if the product is a national blockchain. A central bank cannot tell parliament "we do not know who signed last night's settlement."
JIL Sovereign Technologies Incorporated operates a federated Layer-1 in which each sovereign cell runs its own named validator set. The operators are known at genesis. The nation can point to the machines, the keys, and the legal entities that attest each block.
Named validators are how a sovereign cell stays a national chain instead of becoming someone else's network.
What "named" actually means
A validator on a JIL cell is not a pseudonymous address. It is an operator with:
- A legal identity the cell operator can name: a ministry, a licensed institution, or JIL under the Domain or Hub license.
- A cryptographic identity pinned at genesis. Validator signing keys are Ed25519 software keys today. Attestation seals are hybrid post-quantum (Ed25519 plus ML-DSA-65). Post-quantum validator signing is on the roadmap.
- A place in a known set. 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. One machine is a demonstration, not a national chain.
Rotation is a ceremony, not an anonymous join. Adding or removing a validator is a governed event, recorded, and re-certified. That is how a named set stays named as staff and vendors change.
The domain demos
The worked example is https://demo.jilsovereign.net/demo/. It shows a Domain (Nubara), two annexes, and a Hub (Tirmore), all fictional jurisdictions. Measured 2026-11-12, ten hosts are operated by JIL and eight are in the signing set. That is not Byzantine fault tolerance.
Who operates the named set
The architecture is the same under Domain and Hub. Measured 2026-11-12, ten hosts are operated by JIL and eight are in the signing set.
- Domain and Hub license the same core. JIL operates the recorded validator set on this fleet.
- The domain demos are the worked example. They are not a national validator set, and they are not a purchase.
- The default service key is a 2-of-3 threshold with all three shares held server-side by JIL; there is no user-held shard, and authorizing a signature is not holding a key.
Payment integrity at jilsovereign.com does not run this validator set. The wallet at getjil.com does not either.
Why post-quantum identity matters
A settlement record may need to be checked decades from now. Attestation seals are hybrid: a classical Ed25519 signature and a post-quantum ML-DSA-65 signature, and both must verify. Validator signing is classical Ed25519 today. Post-quantum validator signing is on the roadmap.
Read next how those named sets settle with each other: federation corridors and the Federation.
