Table of contents
A blockchain cannot function until thousands of independent computers agree on what happened and in what order.
Proof of stake is one way to reach that agreement. Instead of asking miners to compete with specialized machines and electricity, a proof-of-stake network assigns influence to validators according to cryptocurrency committed to the protocol. The details vary by network, but the basic idea is consistent: validators put capital behind their votes, and the protocol rewards correct participation while penalizing certain failures or attacks.
For SOL holders, prospective delegators, and anyone comparing blockchain designs, the important questions are practical. Who proposes blocks, who checks them, what can go wrong, and what does staking actually mean for the person holding the tokens?
How Proof of Stake Reaches Agreement
A proof-of-stake network maintains a set of validators that participate in consensus. Depending on the protocol, one validator may be selected to propose a block while other validators vote on that proposal, or validators may use a related stake-weighted process to choose between competing versions of the ledger. Stake matters because it determines how much weight the protocol gives a validator’s participation, although randomness, scheduling rules, and other safeguards may also affect proposer selection.
Validators do not get to rewrite the network’s rules. Other nodes still verify signatures, transaction formats, account balances, and the rest of the protocol before accepting a block. A validator with substantial stake may have more influence over consensus, but that influence does not make an invalid transaction valid.
Rewards usually come from token issuance, transaction fees, or both, while penalties depend on the network. Solana’s current staking documentation states that in-protocol slashing has not been implemented, so native SOL delegators do not currently lose stake when a validator performs poorly or breaks consensus rules. Poor voting performance can still reduce the rewards a validator and its delegators earn.
What Validators and Delegators Actually Do
Running a Solana validator is an operating business, not a passive investment. An operator maintains high-performance hardware and software, stays synchronized with the network, submits votes, protects signing keys, and responds to upgrades or incidents. Validators also pay ongoing vote-transaction costs, which means an operator needs enough stake and revenue to cover expenses over time.
Delegation lets token holders participate without operating that infrastructure. On Solana, a holder can place SOL in a stake account and delegate it to a validator. The delegation increases that validator’s stake weight, but it does not transfer ownership or control of the SOL to the operator, as the staking guide makes clear.
Delegators earn a portion of the staking rewards credited to their chosen validator, after the validator’s commission. Returns are not fixed. They change with network issuance, the amount of SOL actively staked, validator voting performance, and commission. Solana calculates and distributes staking rewards once per epoch, and an epoch is a fixed 432,000 slots — a little over a day and a half at current slot times.
Native stake is not instantly liquid. Activation and deactivation are completed at epoch boundaries, and a network-wide limit on stake entering or leaving the active set can extend the process. The usual wait may be around one epoch, but the timing rules explain why no exact withdrawal time is guaranteed.
Proof of Stake and Proof of Work
Proof of work and proof of stake protect a ledger with different scarce resources. Bitcoin miners repeatedly hash candidate block headers, and producing that work requires specialized hardware and electricity. Proof-of-stake validators commit capital and participate through protocol-defined votes. In both systems, independent nodes verify whether a proposed block follows the rules.
Proof of work and proof of stake use different security models, and neither is automatically more secure. In Bitcoin, an attacker with a majority of the network’s hash power could reorganize recent blocks, censor transactions, or attempt double-spends. The attacker still could not create coins from nothing or make other nodes accept transactions that violate Bitcoin’s consensus rules. Proof of work makes ledger revisions progressively more expensive as new blocks accumulate, which is the mechanism described in Bitcoin’s technical guide.
In proof of stake, an attacker generally needs control over a large share of active stake to disrupt consensus or reverse finalized history, with the precise threshold determined by the protocol. Some networks can destroy an attacker’s stake, which gives them a direct economic exposure that proof-of-work miners do not carry in the same form.
Energy use is one practical difference. Solana validators do not compete through continuous proof-of-work hashing, so the network does not require the mining process that secures Bitcoin. That does not make validator operations costless, since Solana still depends on high-performance servers, networking, and data-center infrastructure.
Speed is less straightforward. Bitcoin targets a block roughly every ten minutes, while Solana schedules leaders in much shorter slots. Those timings come from each network’s design choices; proof of stake does not automatically make a blockchain fast, and proof of work does not by itself require ten-minute blocks. Throughput and finality also depend on networking, execution, validator requirements, block capacity, and the rules used to confirm transactions.
How Solana Uses Proof of Stake
Solana combines stake-weighted consensus with Proof of History, a sequential chain of SHA-256 hashes that functions as a verifiable clock. Block producers can insert transaction data into that sequence, creating evidence that events occurred in a particular order. This shared time source reduces some of the coordination that validators would otherwise need when ordering transactions.
Proof of History is not a substitute for consensus. Validators still replay transactions and submit stake-weighted votes, and the network uses those votes when choosing between forks. Proof of History helps establish timing and order, while proof of stake determines how validator votes contribute to agreement.
Solana’s slot duration has also changed over time. It was commonly described as 400 milliseconds, but the network began reducing mainnet slots in stages during 2026: the target fell to 350 milliseconds at epoch 1020 and to 300 milliseconds at epoch 1024, with further steps toward 200 milliseconds planned. A slot is an opportunity for a scheduled leader to produce a block, not a guarantee that a block will appear, so “slot time” is the accurate term.
Stake affects both consensus and validator economics. More delegated stake gives a validator greater voting weight and a greater share of inflationary rewards, provided the validator earns vote credits. Infrastructure still matters because unreliable hardware, poor networking, or operational mistakes can reduce voting performance and rewards. Strong infrastructure does not change the protocol’s reward formula, but it helps a validator perform the work that formula measures.
Frequently asked questions
Can I Lose SOL Through Native Staking?
Solana does not currently implement in-protocol slashing, so a validator cannot presently cause delegated SOL to be destroyed through native slashing. Delegators can still earn less when a validator performs poorly, and token prices can fall while SOL is staked. Liquid staking introduces separate smart-contract and market risks that do not apply in the same way to native delegation.
How Much Can I Earn From Staking SOL?
There is no fixed rate. Rewards vary by epoch based on Solana’s issuance schedule, total active stake, validator vote credits, and commission. A quoted annual percentage is an estimate rather than a guaranteed return.
Do I Need to Run a Validator to Stake?
No. A SOL holder can delegate through a compatible wallet without running validator hardware. The validator receives stake weight, while the holder retains control of the stake account and its withdrawal authority.
How Long Does Unstaking Take on Solana?
Deactivation completes at an epoch boundary, and a Solana epoch currently runs a little over a day and a half. The exact wait depends on when the request is submitted and how much stake is changing state across the network, so one to three days may be a useful estimate but is not a guarantee.
Is Proof of Stake More Secure Than Proof of Work?
There is no universal ranking because the systems fail in different ways. Proof of work depends on hash power, energy, hardware, and mining economics, while proof of stake depends on stake distribution, validator behavior, protocol penalties, and finality rules. Security should be judged from the design and operating record of a specific network rather than its consensus label.


