Validator counts are the most gamed metric in the industry. A network can show fifty validators and be controlled by two people. EmpoorioChain's decentralization gate therefore counts operators, not nodes, and defines what makes an operator independent before a single external validator has joined. This post is that definition and the reasoning behind each condition.
The six conditions
To be counted as an independent external operator in the decentralization report, an operator must:
1. Publish the identity of the responsible entity. A pseudonymous validator can run; it cannot be counted toward decentralization, because independence cannot be verified for an unknown party. The identity can be a company, a foundation, a university lab or a named individual.
2. Expose a private metrics endpoint to the authorised monitoring stack. Port 9615 (Prometheus) reachable from the monitoring network only. Uptime, client version, peer count and finality lag are observed, not self-reported.
3. Hold uptime ≥ 99 % over a rolling 7-day window. That is about 100 minutes of allowed downtime per week — enough for a reboot and a binary upgrade, not enough for a node nobody is watching.
4. Run an approved client version. Every validator on the same, reviewed binary. A single node on an old version is a consensus risk to all of them; the version is read from the node, not from a form.
5. Share no infrastructure or keys with another operator counted as independent. Same cloud account, same physical host, same key custodian — any of these collapses two "operators" into one. The current two validators fail this test against each other by design, since both are Empoorio's; that is why they count as one operator.
6. Accept the incident-response playbook. When a validator is compromised, the playbook says: stop the service, leave the active set where possible, rotate session keys, move funds controlled by exposed keys, preserve logs, redeploy from clean infrastructure. An operator who has not agreed to act this way is a liability during exactly the event when coordination matters.
What the operator receives
The gate is deliberately demanding, and the network gives something back. Operators who meet it appear in the public decentralization report and on EmpooScan's validator view; they receive the same runtime-upgrade manifests and timelocks as the core validators — normal upgrades carry a 12-hour minimum notice on testnet, security and economic ones 48 hours — and they take part in the pre-mainnet rehearsal of upgrade classes, including the emergency drill with rollback.
Staking rewards accrue per era under the gap-decay emission rule, with the nominal APY capped by the protocol at 20 %. There is no published rate, because the protocol does not fix one; anyone promising a number is not speaking for the chain.
Why the bar is where it is
The gate requires four independent external operators and ten validators in total before the mainnet conversation opens, with no single operator in majority control. Four is the smallest number at which a coalition of externals could, in principle, outvote the founding team — which is the property that makes a decentralization claim mean something.
Today the count is zero externals, and the report says so. The conditions above are published so that the first external operator knows exactly what they are signing up for, and so that when the report finally shows four, nobody has to wonder how the number was reached.
Based on DECENTRALIZATION_REPORT.md, VALIDATOR_IN_30_MINUTES.md §8 and RUNTIME_UPGRADE_POLICY.md.