Connecting…
Validator set & credible neutrality
Khromosome (chain 777001) is a public beta on a testnet-grade genesis. This page reads the beacon chain directly and shows who actually controls the validators. It is not a summary written to look good. Today the honest answer is one operator. The point of publishing it is to show the number change.
Network
Head block
—
rpc.khromosome.xyz
Finalized block
—
Finalized epoch
—
beacon checkpoint
Beacon peers
—
connected (queried node)
Validator set
Active validators
—
Distinct operators
—
with ≥1 active validator
Largest operator
—
share of active stake
Nakamoto coefficient
—
operators needed to halt finality (>⅓)
Loading…
By operator
| Operator | Indices | Active | Share of active stake | Independent of founder |
|---|---|---|---|---|
| Loading… | ||||
All validators
| Index | Status | Effective balance | Operator |
|---|---|---|---|
| Loading… | |||
How to read this
- Operator ≠ validator. One operator can run many validator keys. Decentralization is measured per operator, using operators.json (index ranges → operator). Operators under common control are listed as one.
- Nakamoto coefficient is the smallest number of operators whose combined active stake is above ⅓. That much is enough to stop finality. Above ⅔ an operator set can finalize by itself.
- Exited validators are permanent. Indices 8–15 exited after the July 2026 network split and can never be re-activated. New operators join with new keys and a new deposit.
- Target before mainnet: at least 3 independent operators, the founder below 50%, and no operator at ⅓ or more (decentralization spec C, D-C1/D-C2). Want to help? Read the operator guide.