# Metanode: 2026 Q4 target **URL:** \ **Category:** Tech Talk\ **Created:** [October 16, 2026, 10:14am UTC](https://forum.polkadot.network/t/metanode-2026-q4-target/19027 "2026-10-16T10:14:44Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Jan-Jan](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/jan-jan/32/6068_2.png) [@Jan-Jan](https://forum.polkadot.network/u/Jan-Jan)\ **Post date:** [October 16, 2026, 10:14am UTC](https://forum.polkadot.network/t/metanode-2026-q4-target/19027/1 "2026-10-16T10:14:44Z")
As as first step in aligning infrastructure operations with the [Polkadot Trinity](https://x.com/Polkadot/status/2067575946119405637) reliability and performance requirements, i.e., the transition to running on [Metanode](https://forum.polkadot.network/t/metanode-early-thinking-on-consolidating-node-services/18689), the target is for validator operators to also run Asset Hub and People Chain collators, including serving light nodes and RPC requests for Polkadot App, by the end of the year. ## Transition proposal As the current validator set of 600 exceeds the needs of Polkadot, it will be proposed to reduce the validator set to 320. This allows an increase in the reward for operators who become Metanode operators (e.g. to cover increased hardware requirements), while being fiscally responsible with Polkadot’s budget. Keep an eye for Jonas’ upcoming article that will go into more details. ### Reducing the validator set To minimise risk we propose to reduce validators count gradually in 3 steps over 3 weeks. This allows adequate time for monitoring and the ability to stop and fix problems if any degradation is noticed. This reduction is planned to happen during next month (Nov 2026): - Week 1: Reduce to 500 validators (and a backing group of size 4). - Week 2: Reduce to 400 validators. - Week 3: Reduce to 320 validators. The smaller set of validators will be chosen according to the existing nominations rules. ### Transitioning to Metanode operators Following the successful reduction of the active validators set, validators will be provided the opportunity to join asset-hub and people-chain as collators and will be rewarded for that. To make the transition for operators as easy as possible, the following will be provided: 1. Minimum hardware requirements. 2. Setup instructions — for either single machines or multiple machines. 3. Quality assurance tools: Setup and node accessibility. ---
**Author:** ![ross](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/ross/32/11267_2.png) [@ross](https://forum.polkadot.network/u/ross)\ **Post date:** [October 17, 2026, 7:30am UTC](https://forum.polkadot.network/t/metanode-2026-q4-target/19027/3 "2026-10-17T07:30:30Z")
Am I correct in thinking “a backing set of 4” concerns parachain block backing as opposed to nomination backing? ---
**Author:** ![ThomasR](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/thomasr/32/1227_2.png) [@ThomasR](https://forum.polkadot.network/u/ThomasR)\ **Post date:** [October 19, 2026, 7:48am UTC](https://forum.polkadot.network/t/metanode-2026-q4-target/19027/4 "2026-10-19T07:48:58Z")
Finally acknowledging the number of validators was over-sized… Finally. ---
**Author:** ![Jan-Jan](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/jan-jan/32/6068_2.png) [@Jan-Jan](https://forum.polkadot.network/u/Jan-Jan)\ **Post date:** [October 20, 2026, 3:06pm UTC](https://forum.polkadot.network/t/metanode-2026-q4-target/19027/5 "2026-10-20T15:06:04Z")
I’ve fixed “backing set of 4” to “backing group of size 4”. Which should clear it up ---
**Author:** ![Northvane](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/northvane/32/11682_2.png) [@Northvane](https://forum.polkadot.network/u/Northvane)\ **Post date:** [October 21, 2026, 1:40am UTC](https://forum.polkadot.network/t/metanode-2026-q4-target/19027/6 "2026-10-21T01:40:48Z")
Since Ref 1909, issuance is split three ways: 32.2% buffer, 45.2% staker rewards, 22.6% validator incentive. Commission is capped at 0. In April the validator incentive was sized as 21,000 DOT a year × 600 validators = 12.6M. At 320, does that pot stay the same, so each validator gets almost double? Or does it shrink to 320 × 21,000, with the rest paying for collating? Either way, does the staker rewards share stay at 45.2%? ---
**Author:** ![Jan-Jan](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/jan-jan/32/6068_2.png) [@Jan-Jan](https://forum.polkadot.network/u/Jan-Jan)\ **Post date:** [October 21, 2026, 8:41am UTC](https://forum.polkadot.network/t/metanode-2026-q4-target/19027/7 "2026-10-21T08:41:46Z")
What a validator receives as a reward stays the same (i.e. it shrinks to 320 x 21’000). In time what the operator receives will increase, to reflect increased hardware costs, when they also operate Asset Hub and People Chain collators in addition to a validator. ---
**Author:** ![Northvane](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/northvane/32/11682_2.png) [@Northvane](https://forum.polkadot.network/u/Northvane)\ **Post date:** [October 21, 2026, 11:40am UTC](https://forum.polkadot.network/t/metanode-2026-q4-target/19027/8 "2026-10-21T11:40:47Z")
Thanks. So validators drop from 22.6% to about 12%. Where does the other 10.6% go: kept in the DAP, or to stakers? And do stakers stay at 45.2%? ---
**Author:** ![ross](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/ross/32/11267_2.png) [@ross](https://forum.polkadot.network/u/ross)\ **Post date:** [November 3, 2026, 8:54am UTC](https://forum.polkadot.network/t/metanode-2026-q4-target/19027/9 "2026-11-03T08:54:33Z")
I’d suggest it doesn’t go anywhere: the total annual issuance should simply be reduced by the corresponding 280 × 21,000 = 5.88 million DOT. But this would mean amending the supply schedule which is probably out of the scope of the effort. So we’ll most likely see the remaining funds go to the buffer, and then re-allocated again once validator collator nodes and light RPC clients are rewarded. ---
**Author:** ![alexggh](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/alexggh/32/11556_2.png) [@alexggh](https://forum.polkadot.network/u/alexggh)\ **Post date:** [November 3, 2026, 1:01pm UTC](https://forum.polkadot.network/t/metanode-2026-q4-target/19027/10 "2026-11-03T13:01:26Z")
Based on our measurements, here are the [minimum hardware requirements](https://docs.polkadot.com/node-infrastructure/run-a-metanode/#hardware-requirements) for running all of the services listed above. On a single machine, you need at least 16 cores, 64 GB of RAM, 2.4 TB+ of NVMe SSD storage and 1 Gbit/s of symmetric bandwidth. The docs also list the requirements for running each service on its own machine. ---
**Author:** ![Northvane](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/northvane/32/11682_2.png) [@Northvane](https://forum.polkadot.network/u/Northvane)\ **Post date:** [November 3, 2026, 11:39pm UTC](https://forum.polkadot.network/t/metanode-2026-q4-target/19027/11 "2026-11-03T23:39:43Z")
You called it. 1966 shrinks the validator pot from 22.6% to 18.8% (22.6 x 500/600), so each validator still gets the same DOT. The rest moves to the buffer and stakers stay at 45.2%. That answers my question, at least for step 1. ---
**Author:** ![pmensik](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/pmensik/32/759_2.png) [@pmensik](https://forum.polkadot.network/u/pmensik)\ **Post date:** [November 5, 2026, 4:02pm UTC](https://forum.polkadot.network/t/metanode-2026-q4-target/19027/13 "2026-11-05T16:02:22Z")
The Metanode direction makes sense to me overall, especially if it helps to consolidate infrastructure currently funded separately. A few questions from the operator side: - how do we plan to measure the quality of RPC and light-client services, beyond simply checking that an endpoint is reachable? Latency, availability, geographical coverage and the ability to handle sustained load can vary quite significantly between operators. - what about rate limiting and request throttling? Any future validator should do this to prevent DDoS. Will there be an official guide on what limits to place on the RPC? - what if a validator fails to provide these additional services? How would you remove such a validator from the set? - what are the main targets for RPCs/light nodes? Polkadot JS, wallets, even 3rd parties? - is there already a plan for a pilot with existing validators, and will service quality eventually influence rewards? Basically, my biggest concern is the order of operations. If we shrink the active set first before implementing Metanodes, we might exclude validators who would otherwise provide excellent service while keeping those who don’t really care, even though they have a higher stake now.