The number of epochs after stake delegation during which the delegated SOL progressively becomes active and eligible for earning rewards. During warmup, the stake gradually increases its effective weight over one or more epoch boundaries rather than activating instantly, preventing sudden large stake shifts that could destabilize the leader schedule and consensus.
Start with the shortest useful explanation before going deeper.
The number of epochs after stake delegation during which the delegated SOL progressively becomes active and eligible for earning rewards. During warmup, the stake gradually increases its effective weight over one or more epoch boundaries rather than activating instantly, preventing sudden large stake shifts that could destabilize the leader schedule and consensus.
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.
Place the term inside its Solana layer so the definition is easier to reason about.
Clusters, nodes, MEV actors, routing, and operating environments.
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.
Use this compact block when you want to give an agent or assistant grounded context without dumping the entire page.
Warmup Period (warmup-period) Category: Network Definition: The number of epochs after stake delegation during which the delegated SOL progressively becomes active and eligible for earning rewards. During warmup, the stake gradually increases its effective weight over one or more epoch boundaries rather than activating instantly, preventing sudden large stake shifts that could destabilize the leader schedule and consensus. Related: Stake, Epoch, Cooldown Period
Use glossary context, relationships, mental models, and builder paths to get structured answers instead of generic chat output.
Optional: paste Anchor, Solana, or Rust code so the Copilot can map primitives back to glossary terms.
The Copilot will answer using the current term, related concepts, mental models, and the surrounding glossary graph.
These branches show which concepts this term touches directly and what sits one layer beyond them.
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.
A period of 432,000 slots (approximately 2-3 days) that defines a staking cycle. At each epoch boundary, the leader schedule is recalculated based on stake weights, stake activations/deactivations take effect, and inflation rewards are distributed to validators and delegators.
The number of epochs after stake deactivation during which the staked SOL remains locked and cannot be withdrawn. During cooldown, the stake progressively becomes available for withdrawal over one or more epoch boundaries. The cooldown mechanism prevents rapid unstaking that could destabilize consensus by suddenly reducing the validator's stake weight.
These are the next concepts worth opening if you want this term to make more sense inside a real Solana workflow.
These entries are easy to mix up when you are reading quickly, prompting an LLM, or onboarding into a new layer of Solana.
The number of epochs after stake deactivation during which the staked SOL remains locked and cannot be withdrawn. During cooldown, the stake progressively becomes available for withdrawal over one or more epoch boundaries. The cooldown mechanism prevents rapid unstaking that could destabilize consensus by suddenly reducing the validator's stake weight.
Glossary entries become useful when they are connected. These links are the shortest path to adjacent ideas.
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.
A period of 432,000 slots (approximately 2-3 days) that defines a staking cycle. At each epoch boundary, the leader schedule is recalculated based on stake weights, stake activations/deactivations take effect, and inflation rewards are distributed to validators and delegators.
The number of epochs after stake deactivation during which the staked SOL remains locked and cannot be withdrawn. During cooldown, the stake progressively becomes available for withdrawal over one or more epoch boundaries. The cooldown mechanism prevents rapid unstaking that could destabilize consensus by suddenly reducing the validator's stake weight.
These entries live beside the current term and help the page feel like part of a larger knowledge graph instead of a dead end.
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.
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.
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.
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.