SPONSORED PARTNERMEXCExplore global spot and futures marketsEXPLORE MEXC →
CHARTING PARTNERTradingViewAdvanced charts, indicators and market analysisOPEN CHARTS →
TRADING PARTNERGMX via NetNapz TradeTrade decentralised perpetual marketsSTART TRADING →POLKADOT · INFRASTRUCTURE · ORIGINAL NETNAPZ REPORTING
Polkadot Metanode Plan Proposes 320 Validators; Initial Per-Validator Reward Unchanged
A proposed consolidation of node services raises questions about operator workloads, incentives and resilience.
Polkadot’s Metanode transition proposal outlines a November reduction from 600 active validators to 320, passing through 500 and 400 over three weeks.
The 16 October post is by Jan-Jan, whose public profile identifies a technical programme and developer role at Parity.
Reward clarification
On 21 October, the author said the individual validator reward would initially stay unchanged, with the pool shrinking to 320 × 21,000 DOT. Additional compensation would come later for operators also running Asset Hub and People Chain collators. The discussion leaves the destination of the remaining allocation unresolved.
After a successful reduction, operators would be offered those additional duties. Hardware requirements, setup instructions and accessibility checks are promised.
Why consolidate services?
The 18 September design discussion describes separately funded RPC providers, collators and bootnodes as difficult to coordinate and scale. It proposes reusing validator operators to supply more services, with compensation for extra hardware.
That earlier discussion links Asset Hub to assets and contracts, People Chain to identity and messaging, and Bulletin Chain to application content. It says hardware measurements were unfinished and the changes were not mandatory at that stage.
NetNapz assessment
Combining services may simplify responsibility for availability, but it also couples more user-facing infrastructure to the same operators. Evaluating that trade-off requires measured capacity, failure recovery arrangements and evidence of operator diversity. Validator count alone cannot establish how independent the underlying organisations, hosting providers or locations are.
Operators considering the change need clear workload benchmarks and compensation terms before committing resources. For nominators, published implementation details and election outcomes would be more informative than an assumed increase in returns.
Verification limits
NetNapz checked both forum discussions and the author profile on 21 October. No executed governance decision, live validator-set reduction or completed rollout was independently verified in these checks. The November timetable remains the author’s proposed sequence. This report makes no claim about a DOT price effect.
Related reporting: Polkadot crawler changes and the limits of peer-count comparisons.