Public operator roster · on-chain

Who runs Khromosome.

Every validator-node operator on Khromosome is registered on chain with a legal name, an ISO 3166-1 jurisdiction code, and a hash of their off-chain KYC attestation bundle. This page reads that roster live from the OperatorRegistry contract on chain 777001. No middleman, no cache, no trust.

Reading OperatorRegistry…

01 Live roster

Active operators
—
Total ever registered
—
Jurisdictions queried
US · DE · UK · JP · SG · FR · CA
Registry contract
0x0609…8182

02 What "operator" means here

An operator on Khromosome is the legal entity behind a validator node — the party signing blocks, collecting validator rewards, and accepting the regulatory obligations that come with running consensus infrastructure. Operators are not stakers or wallet holders.

The OperatorRegistry contract is purely informational. It does not gate consensus, staking, or rewards — those layers run unchanged standard Ethereum PoS. What it does is publish, on chain and immutably, the answer to a question regulated buyers ask first: "who is the legal entity behind that validator key?"

The KYC attestation hash is a commitment to an off-chain document set (passport, articles of incorporation, beneficial-ownership disclosure, sanctions screen). The bundle itself stays off chain for privacy; the hash on chain proves the bundle hasn't been swapped after registration.

Registry data model

Signing addressEOA the operator signs blocks with
Operator nameHuman-readable legal name
JurisdictionISO 3166-1 alpha-2 (e.g. "US")
KYC attestation hashbytes32 — hash of off-chain bundle
Metadata URIIPFS / HTTPS long-form profile
Registered atblock.timestamp — uint64
Deregistered at0 if active; record is preserved either way

03 How to become an operator

Operator slots are gated through a Timelock owned by Joshua's Trezor. The process is intentionally manual — the registry is a regulatory surface, not an open signup form.

  1. Email [email protected] with your entity name, jurisdiction, and validator-key signing address.
  2. Complete the off-chain KYC bundle (identity, incorporation, beneficial ownership, sanctions screen).
  3. We publish your long-form profile to IPFS and hash the KYC bundle.
  4. The Trezor-controlled Timelock calls registerOperator. Your record appears on this page immediately.
Contact: [email protected] — onboarding queue, KYC questions, and Timelock scheduling.

04 Verify this page yourself

Don't trust the rendering — verify against the contract. Source for OperatorRegistry.sol is published on sourcify.khromosome.network, and every read this page makes is a plain eth_call against rpc.khromosome.xyz.

Registry address0x0609Ab265a53e3807f182460109a9F6428688182
ChainKhromosome — id 777001
RPChttps://rpc.khromosome.xyz
Reads calledactiveOperatorCount · totalOperatorCount · getActiveOperatorsByJurisdiction · getOperator
Chain 777001 · live Block —