Network

Stake-Weighted QoS (SWQoS)

A Quality of Service system introduced in Solana that allocates TPU packet bandwidth to staked validators proportionally to their stake weight, preventing unstaked or lightly staked nodes from flooding leaders with transactions at the expense of stake-backed traffic. Validators that have delegated stake can forward transactions and receive preferential access to leader bandwidth, making it economically meaningful to route transactions through staked RPC or validator nodes. SWQoS is a key defense against spam and denial-of-service attacks that plagued Solana during high-traffic periods.

IDstake-weighted-qosAliasSWQoS

Plain meaning

Start with the shortest useful explanation before going deeper.

A Quality of Service system introduced in Solana that allocates TPU packet bandwidth to staked validators proportionally to their stake weight, preventing unstaked or lightly staked nodes from flooding leaders with transactions at the expense of stake-backed traffic. Validators that have delegated stake can forward transactions and receive preferential access to leader bandwidth, making it economically meaningful to route transactions through staked RPC or validator nodes. SWQoS is a key defense against spam and denial-of-service attacks that plagued Solana during high-traffic periods.

Mental model

Use the quick analogy first so the term is easier to reason about when you meet it in code, docs, or prompts.

Think of it as a building block that connects one definition to the larger Solana system around it.

Technical context

Place the term inside its Solana layer so the definition is easier to reason about.

Clusters, nodes, MEV actors, routing, and operating environments.

Why builders care

Turn the term from vocabulary into something operational for product and engineering work.

This term unlocks adjacent concepts quickly, so it works best when you treat it as a junction instead of an isolated definition.

AI handoff

AI handoff

Use this compact block when you want to give an agent or assistant grounded context without dumping the entire page.

Stake-Weighted QoS (SWQoS) (stake-weighted-qos)
Category: Network
Definition: A Quality of Service system introduced in Solana that allocates TPU packet bandwidth to staked validators proportionally to their stake weight, preventing unstaked or lightly staked nodes from flooding leaders with transactions at the expense of stake-backed traffic. Validators that have delegated stake can forward transactions and receive preferential access to leader bandwidth, making it economically meaningful to route transactions through staked RPC or validator nodes. SWQoS is a key defense against spam and denial-of-service attacks that plagued Solana during high-traffic periods.
Aliases: SWQoS
Related: Stake, Validator, TPU (Transaction Processing Unit)
Glossary Copilot

Ask grounded Solana questions without leaving the glossary.

Use glossary context, relationships, mental models, and builder paths to get structured answers instead of generic chat output.

Explain this code

Optional: paste Anchor, Solana, or Rust code so the Copilot can map primitives back to glossary terms.

Ask a glossary-grounded question

Ask a glossary-grounded question

The Copilot will answer using the current term, related concepts, mental models, and the surrounding glossary graph.

Concept graph

See the term as part of a network, not a dead-end definition.

These branches show which concepts this term touches directly and what sits one layer beyond them.

Branch

Stake

SOL tokens that are delegated to a validator to increase its voting weight and earn staking rewards. Staking is non-custodial—stakers retain ownership of their SOL. Stake activates/deactivates at epoch boundaries with a warmup/cooldown period. Validators with more stake are assigned more leader slots and have proportionally more influence in consensus.

Branch

Validator

A node that participates in the Solana network by validating transactions, voting on blocks, and (when selected as leader) producing new blocks. Validators run the Agave, Firedancer, or Jito client software, require significant hardware (128+ GB RAM, high-core CPU, NVMe SSD), and earn rewards from inflation and transaction fees.

Branch

TPU (Transaction Processing Unit)

Transaction Processing Unit—the pipeline within a leader validator that ingests, verifies, and executes transactions. The TPU has stages: fetch (receive packets via QUIC), sigverify (verify Ed25519 signatures), banking (execute against current bank state), and broadcast (shred and send via Turbine). Non-leader validators forward transactions to the current leader's TPU.

Next concepts to explore

Keep the learning chain moving instead of stopping at one definition.

These are the next concepts worth opening if you want this term to make more sense inside a real Solana workflow.

Core Protocol

Stake

SOL tokens that are delegated to a validator to increase its voting weight and earn staking rewards. Staking is non-custodial—stakers retain ownership of their SOL. Stake activates/deactivates at epoch boundaries with a warmup/cooldown period. Validators with more stake are assigned more leader slots and have proportionally more influence in consensus.

Core Protocol

Validator

A node that participates in the Solana network by validating transactions, voting on blocks, and (when selected as leader) producing new blocks. Validators run the Agave, Firedancer, or Jito client software, require significant hardware (128+ GB RAM, high-core CPU, NVMe SSD), and earn rewards from inflation and transaction fees.

Core Protocol

TPU (Transaction Processing Unit)

Transaction Processing Unit—the pipeline within a leader validator that ingests, verifies, and executes transactions. The TPU has stages: fetch (receive packets via QUIC), sigverify (verify Ed25519 signatures), banking (execute against current bank state), and broadcast (shred and send via Turbine). Non-leader validators forward transactions to the current leader's TPU.

Network

Staking Rewards

SOL earned by validators and their delegators each epoch as compensation for participating in consensus and securing the network, funded by protocol inflation rather than solely transaction fees. Rewards are proportional to a validator's active stake and are credited at the end of each epoch to stake accounts automatically; the effective APY depends on the current inflation rate, the percentage of total SOL staked, and the validator's commission rate. Validators set a commission (0–100%) representing the fraction of rewards they keep before passing the remainder to delegators.

Commonly confused with

Terms nearby in vocabulary, acronym, or conceptual neighborhood.

These entries are easy to mix up when you are reading quickly, prompting an LLM, or onboarding into a new layer of Solana.

Networkstake-activation

Stake Activation

The process by which newly delegated stake becomes active and begins earning staking rewards. After a user delegates SOL to a validator, the stake enters a warmup phase and becomes fully active at the next epoch boundary (within one epoch, approximately 2-3 days). During activation, the stake does not contribute to the validator's voting weight or earn rewards. This delay prevents rapid stake shifts that could destabilize consensus.

Networkstake-deactivation

Stake Deactivation

The process of unstaking SOL from a validator, which requires a cooldown period of one epoch before the SOL can be withdrawn. After initiating deactivation, the stake stops earning rewards at the next epoch boundary and enters a cooling-down state. Once the cooldown epoch completes, the SOL becomes available for withdrawal back to the stake authority's wallet. This delay mirrors stake activation and prevents sudden large stake removals from disrupting network stability.

Related terms

Follow the concepts that give this term its actual context.

Glossary entries become useful when they are connected. These links are the shortest path to adjacent ideas.

Core Protocolstake

Stake

SOL tokens that are delegated to a validator to increase its voting weight and earn staking rewards. Staking is non-custodial—stakers retain ownership of their SOL. Stake activates/deactivates at epoch boundaries with a warmup/cooldown period. Validators with more stake are assigned more leader slots and have proportionally more influence in consensus.

Core Protocolvalidator

Validator

A node that participates in the Solana network by validating transactions, voting on blocks, and (when selected as leader) producing new blocks. Validators run the Agave, Firedancer, or Jito client software, require significant hardware (128+ GB RAM, high-core CPU, NVMe SSD), and earn rewards from inflation and transaction fees.

Core Protocoltpu

TPU (Transaction Processing Unit)

Transaction Processing Unit—the pipeline within a leader validator that ingests, verifies, and executes transactions. The TPU has stages: fetch (receive packets via QUIC), sigverify (verify Ed25519 signatures), banking (execute against current bank state), and broadcast (shred and send via Turbine). Non-leader validators forward transactions to the current leader's TPU.

More in category

Stay in the same layer and keep building context.

These entries live beside the current term and help the page feel like part of a larger knowledge graph instead of a dead end.

Network

Mainnet Beta

Solana's primary production cluster where real SOL and real economic activity occur; the "beta" designation reflects the network's ongoing protocol development despite being fully live since March 2020. It uses the same architecture as other clusters but with real validator stakes, live staking rewards, and permanent on-chain state. All production dApps, tokens, and NFTs exist on Mainnet Beta.

Network

Devnet

A persistent public Solana cluster intended for application development and testing, running the same software version as Mainnet Beta but with no real economic value. Devnet SOL can be freely airdropped via the CLI or faucet APIs, and the ledger may be reset periodically by Solana Labs. Developers use Devnet to test programs and integrations before deploying to Mainnet Beta.

Network

Testnet

A public Solana cluster used primarily by the Solana core team and validators to test new software releases, performance benchmarks, and network upgrades under real network conditions before they reach Mainnet Beta. Testnet SOL has no monetary value, and the ledger is reset more frequently than Devnet; it is less suitable for application development and more suited for validator operators validating their infrastructure.

Network

TPS (Transactions Per Second)

The rate at which a Solana cluster processes and commits transactions; Solana's theoretical maximum exceeds 65,000 TPS due to its parallel execution model, though real-world sustained throughput on Mainnet Beta typically ranges from 2,000–5,000 non-vote TPS under normal load. Vote transactions (used for consensus) make up a significant portion of all on-chain activity and are counted separately. High TPS is enabled by Proof of History timestamps, Sealevel parallel execution, and Gulf Stream mempool-less forwarding.