docs: define the decentralized Network Validator protocol (ADR-011) - #40
Merged
Conversation
Proposes ADR-011 answering issue #28: validator identity/registration/ stake/lifecycle, randomized per-dimension challenges over the existing SolveChallenge RPC, signed bounded evidence envelopes reusing the availability pallet's basis-points/replay pattern, a threat table (collusion, Sybil, self-validation, bribery, withholding, replay), and integer-only multi-validator trimmed-mean aggregation with confidence, disputes, and reward incentives. Moves availability/reputation call origins from the Control Plane's single EnsureRoot bridge to signed, registry-checked Network Validator accounts. No code changes; #29 implements this once accepted. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This was referenced Aug 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Proposes ADR-011, answering #28: an accepted ADR is required before the Network Validator executable/component boundary can be added, and this is that ADR.
Grounded in the current code, not the aspirational docs:
EnsureRootonavailability::submit_proof/reputation::update_vector/record_availability(blockchain/runtime/src/lib.rs:185,202-203), verifying provider signatures itself before relaying.ProviderInspectorcross-pallet trait shape, the basis-points/sequence/replay pattern already proven inpallets/availability, and the already-definedSolveChallengeRPC (agent.proto) as the Validator↔Agent challenge channel.Decision highlights
pallet-network-validator: signed accounts, bonded stake,Candidate → Active → Suspended/Exitedlifecycle,NetworkValidatorInspector::is_active.availability/reputationorigins move from the Control Plane's singleEnsureRootbridge toensure_signed+ registry-checked validator accounts.SolveChallengesurface; Control Plane stays the Agent's cert introducer/allowlist pusher.EvidenceSummaryenvelopes (integerscore_bps, sequence/replay protection,payload_hash— detailed evidence stays off-chain).submissions_received / committee_size), a bounded dispute window, and Reward Points incentives for non-outlier submissions.architecture.mdclaims BABE/GRANDPA; the dev chain actually runs Aura/GRANDPA (ADR-009) — the validator-selection design in this ADR is built around that reality.Scope
Documentation only — no code changes. #29 implements this protocol once accepted.
🤖 Generated with Claude Code