Validating
Validators do not operate the robots. They independently score miner outputs against the task instruction and PoPW policy, with no operational stake in any single operator’s P&L. That independence is what lets downstream parties (auditors, insurers, counterparties) treat onchain records as more than self-attestation.
Responsibilities
Run subnet-specific checkers: replay, benchmarks, sensor-signature verification, or held-out ground truth, as defined for the workload.
Post ScoreRoots (or equivalent commitments) that the chain and explorer surface.
Meet staking requirements: the design calls for a dual tranche — KNX for protocol security and stablecoins for settlement assurance on mainnet; the public testnet may expose a subset of that until mainnet.
Slashing and economics (design)
Malicious or negligent validation, collusion, or approval of tampered evidence is intended to be prohibitively expensive relative to honest behavior, via slashing and economic isolation. See Protocol architecture and Proof-of-Physical-Work.
Next steps
Validator metascore (design) — how the chain scores validators who score miners
Last updated