Home · Learn · Who runs the validators

Who runs the validators?

Measured 2026-11-12, ten hosts are operated by JIL and eight are in the signing set Sovereign Technologies Incorporated. The set is permissioned. A zone name is a label, not a location. The eight-region fleet is a separate plan and is not this set. No regulator runs a node.

What the fleet is asked to be

A diagram shows ten cities and ten independent operators. A security review asks which regulator signs blocks. A status page is read as nine of ten because a demo used that ratio. Someone looks for a public validator set they can join. Measured 2026-11-12, ten hosts are operated by JIL and eight are in the signing set Sovereign Technologies Incorporated. Agreement is set per action, and the rule is below.

Those are the signs.

The live fleet is 10 validators. All of them are operated by JIL Sovereign Technologies Incorporated. The set is permissioned. Operators are known at genesis. This is not anonymous mining. A validator named for a compliance zone is labeled for that zone. The label does not mean the machine is located in that zone. One hosting provider runs the fleet. No regulator operates a node. No regulator endorses a node. No regulator has reviewed a node. The named validators reading is the page this answer sits on top of, and it should be read with this one rather than instead of it.

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. A validator that contradicts the others is recorded, not outvoted. That is not Byzantine fault tolerance. It is not a design in which some number of anonymous operators can be outvoted and the chain still finalizes. The sovereign domain, federation, and original Layer-1 readings record the worked example in a second sentence that should be kept beside the first: measured 2026-11-12, ten hosts are operated by JIL and eight are in the signing set. Both sentences name the same operator. Neither sentence is a purchase, and neither sentence moves the machines to a ministry.

The eight-region fleet is a later plan and is not this 10-validator set. Four regions are shown and four are shadow, and this page does not name the shadow regions. Measured 2026-11-12, jil-mainnet-2 seals blocks with jil-abci-node under a third-party consensus engine. Eight hosts are in the signing set. Ten hosts are operated by JIL. The Attested Consensus Layer rule is a separate binary and is not this process. A quote or proof that fails inspection does not count. Validators on the later plan stay named and operated by JIL.

Named, on this system, means three concrete things. 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. And a place in a known set, so that settlement is agreement inside that set rather than a race. Rotation is a ceremony. Adding or removing a validator is a governed event, recorded and re-certified. It is not an anonymous join. On the fleet that is actually running, the operator named in that set is JIL. One machine is a demonstration, not a national chain. The architecture is the same under Domain and Hub. The class changes the fee, not the engine, and it does not by itself change who operates the recorded set.

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.

Who does not run these validators is part of the same answer. Payment integrity at jilsovereign.com, JIL Sovereign Technologies Incorporated, does not run this set. The retail wallet at getjil.com and wallet.getjil.com does not run this set. This page does not add that host to the operation claim. A Domain or Hub license does not, by itself, move the recorded set off JIL, and it does not move custody of the cell's banking to JIL. JIL does not custody that banking.

The federation reading describes the architecture a national deployment is aimed at: each cell with a validator set the operator can point to, and no foreign anonymous community governing the settlement. The named-validator reading and the company brief describe the fleet that exists today. Both can be true only if they are not collapsed. A country does not acquire the live 10 by opening the domain demo. The demo is simulated. From the runbook's validator gate onward, the written test is that the nation, not JIL, operates the machines that finalize that cell's blocks. Until that gate is actually closed for a licensee, saying the nation runs the validators is ahead of the record. This page will not say it about the live fleet.

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.

Public copy sometimes reaches for a larger anonymous set, or for a count this host does not use. Do not use one. The number on the company brief is 10, all operated by JIL. The recorded showcase measurement is 10 in the set, 9 signing, same operator. The rule is set per action: a block seal at six or eight of ten, a payment request at every active validator, a bridge withdrawal at every responding validator. ACL is the name of the consensus layer because it attests the act, not only the order. Identity, policy, and jurisdiction are evaluated in the same pass as ordering, by validators that are named rather than anonymous. That property is the design. The live operator of the set that exists is still JIL Sovereign Technologies.

If the question is how a country would ever stand up its own set, the next page is the runbook path, not a claim that the path has already been walked. If the question is what the seals on a record will still mean later, stay on the post-quantum reading: hybrid seals today, post-quantum validator signing later, and no claim that the archive is already signed with a post-quantum validator key. Validator identity is the root of later proofs, including corridor headers and reserve attestations. Describing that identity as already post-quantum at the signing step would be ahead of the post-quantum page.

Questions

Are any of the 10 validators run by a central bank or a regulator?

No. All 10 are operated by JIL Sovereign Technologies Incorporated. No regulator operates, endorses, or has reviewed a node. A compliance-zone name is a label, not a location.

Is the chain Byzantine fault tolerant?

No. Every validator is operated by JIL, so the agreement rules bound accident and partial compromise, not a malicious operator. 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. The set is permissioned and named. It is not anonymous mining.

Why do some pages say 9 signing?

Measured 2026-11-12, ten hosts are operated by JIL and eight are in the signing set. It is a dated measurement, not the agreement rule, not a second operator, and not a purchase. The rule is set per action, as stated above.

Does a Domain license mean the country runs the machines?

Not on the fleet that is live today. The runbook's validator gate is the written point at which a state's own set would be stood up. The recorded set is still operated by JIL. A license also does not move custody of the domain's banking to JIL.

Does a wallet hold a shard of a validator key?

No. Validator keys are Ed25519 software keys on each validator, held by JIL. The default service key is a separate 2-of-3 key whose shares JIL also holds.

Read with this

Named validators, Post-quantum, An original Layer-1, What is a Sovereign Domain, Three-shard custody, The licensing model, The deployment runbook, The federation.