Short answer
The Attested Consensus Layer seals a block when six of the ten named validators present a verified enclave quote and a verified state-transition proof. When those proofs are absent, eight of the ten must vote yes. A quote or proof that fails inspection does not count. Seven does not pass. A payment request still needs a yes from every active validator; one objection fails that request and the chain continues. JIL Sovereign Technologies Incorporated operates every validator. The chain is jil-mainnet-2. Validators are operated by JIL Sovereign Technologies Incorporated. This is not Byzantine fault tolerance.
ATCE, the Adaptive Trust, Compliance and Execution Engine, is the other half of the same pass. It rules on the act before value moves. The ruling is allow or deny, with a reason code and a SHA-256 commitment. That ruling happens before value moves. It rules the act before value moves. ATCE is patent pending.
What a reviewer already has in the room
A fixed headcount treats a silent validator and a bad proof as the same event. A slide that says the network never stops because three nodes are offline is not a rule you can underwrite. A payment that clears on a minority is not the same thing as a block that sealed. And a latency number with no measurement date is not a commitment.
This page separates those cases. Silence is not a yes. A failed inspection does not count. A payment request is still unanimous. Silence is not a yes. Seven does not pass.
Two jobs, one pass
ACL, the Attested Consensus Layer, answers whether the named validators agree on the block and whether the evidence on those votes holds. ATCE answers whether this act may exist under the published policy: identity, jurisdiction, zone, sanctions, limits, and the record. Ordering and admissibility are produced together. A transfer is not settled first and reviewed later.
JIL Sovereign Technologies Incorporated (Delaware) operates this Layer-1 at jilsovereign.net under license from JIL Sovereign Holdings, LLC (Wyoming). Payment integrity at jilsovereign.com is the same company and a different product. The retail wallet is a separate host. JIL does not publish its customer base. Strict NDA requirements apply, and CBDC customers prefer anonymity. This page does not name a customer. No country is named here.
The full ATCE guide is the ATCE section. The one-page overview is ATCE before settlement. The engineering record behind the seal is decision D-22. The gated write-up is ACL and ATCE on the docs portal. Ignition on a corridor hop is a separate question. That page opens with the gas toll problem, then the published toll, on the Ignition Switch page.
How a block seals
A block seals on evidence, not on a static slogan. For the recorded fleet of ten named validators, the rule has three arms. Identity weight is one per voting validator. The set is permissioned and single-operator, so there is no coin-stake axis. A latency class may be recorded on a vote. It does not lower the count.
| Arm | When it applies | Ten validators | Status, 2026-11-09 |
|---|---|---|---|
| Optimistic | Each counted vote carries a verified enclave quote and a verified state-transition proof. The votes already in hand agree on the block, the state root, and the outcome. This validator's own vote is in the set. Five of ten is refused, because two sets of five need not overlap. | Six of ten | Six of ten when each counted vote carries a verified enclave quote and a verified state-transition proof. |
| Fallback | No inspection has failed, and the evidence is absent. This arm applies when those proofs are absent. | Eight of ten | Live on jil-mainnet-2. JIL operates every validator. |
| Deep | Any quote or proof failed inspection. Those votes do not count. The rest must still clear the floor. | Nine of ten | Eight keys whose quotes or proofs fail inspection do not seal a block. |
Seven does not pass on any arm. On the proof path, silence of up to four validators does not by itself block a seal, and only when the six who answer present verified evidence and already agree. Silence is still not a yes.
What a payment still requires
A payment request passes only when every active voting validator votes yes. One objection fails that request. The chain continues. Silence is not a yes on a request. Bridge withdrawals stay at agreement from every responding validator. The block seal does not relax either rule.
A state-root disagreement is still checked before a floor seal. The optimistic arm is the exception, and only when the votes already in hand agree. A contradicting root that arrives after an optimistic seal halts. It does not unwind the block.
What ATCE rules, and what is deployed
ATCE runs inside consensus. No transfer moves value outside an ATCE ruling. The verdict on an act that stays inside a sovereign domain is a domestic ruling. The verdict on a hop that leaves the domain is a corridor ruling. Both accounts in an account-to-account move are ruled. An unzoned account counts as no zone. A release with no ATCE context is refused.
The published policy belongs to the licensee. ATCE does not write it. An agentic review can hold an act that passed every written rule. It cannot release an act ATCE denied. A hold is a deny: a person decides what happens next, and the sender submits a new act.
Status, 2026-11-09. Enforcement on every transfer, the attester, the reviewer bridge, the agentic review, and the record writer are Live. JIL operates the ten validators on jil-mainnet-2. The production record store is designed. JIL commits to keep each transaction record for 10 years from creation, and the capacity for that store is allocated when a license is signed. JIL does not publish its customer base. The consensus engine is self-written and Johanson Group LLP is examining SOC 2 Type 1, SOC 2 Type 2, and HIPAA; no report has been issued yet. A separate firm is being engaged for HITRUST.
The reason codes, the two layers, the record, and the questions are in the ATCE section. Patent claims are filed and pending. Nothing on this page is a granted patent.
What this page will not claim
- It will not say the network never stops because three nodes are offline. That slogan drops the conditions. A payment request is still unanimous among active validators.
- It will not publish a latency number. Targets in a design note are not measurements.
- It will not name a hardware enclave product. The seal is six of ten with a verified enclave quote and a verified state-transition proof, or eight of ten when those proofs are absent.
- It will not call this Byzantine fault tolerance. Every validator is operated by JIL. The rule bounds accident and partial compromise. It does not bound a malicious operator.
- It will not say you keep your keys on the default service key. That key is reconstructed on the server. A user-held shard is not the live path.
- It will not say a dispersal code is on the network path. A dispersal implementation is tested. It is not wired into gossip.
What is live, built, and designed
| Marker | What it covers |
|---|---|
| Live | jil-mainnet-2, ten validators, all operated by JIL Sovereign Technologies Incorporated. JIL operates every validator. The chain is jil-mainnet-2. |
| Live, ATCE and ACL | The three-arm seal. ATCE enforcement, the attester, the reviewer bridge, the agentic review, and the record writer. |
| Built | Reed-Solomon dispersal, implemented and tested, not on the gossip path. |
| Designed | Hardware counters, dispersal on the gossip path, the production record store, and the InterOp router. |
Questions a briefing usually starts with
Does six of ten mean the chain is live that way?
Six of ten applies when each counted vote carries a verified quote and a verified proof. When those proofs are absent, eight of the ten must vote yes. JIL operates every validator on jil-mainnet-2.
Can one validator stop a payment?
Yes. A payment request needs a yes from every active validator. One objection fails that request. The chain continues.
Is ATCE the same thing as ACL?
No. ACL seals the block. ATCE rules the act. A sealed block that contains a refused act does not move the value. JIL operates every validator on jil-mainnet-2.
Who operates the validators?
JIL Sovereign Technologies Incorporated. The validators are named and permissioned. This is not an anonymous set, and it is not Byzantine fault tolerance.
Next step
Read the ATCE section if you need the ruling, the record, and the reason codes. Request a briefing if you are evaluating a sovereign domain.