On-Chain Usage
How Solana Delegations Split Validator Rewards
Delegated stake earns protocol rewards by validator performance and stake weight, minus commission, while native staking keeps withdrawal keys with users.
Staking delegations distribute validation rewards in proportion to active stake after the protocol scores validator performance and deducts commission. On Solana, that mechanism has been live since inflationary rewards switched on at epoch 150 on February 10, 2021; a wallet's “Stake” button is merely a signing surface for accounts and instructions the chain enforces. The validator gains vote weight, not custody of the delegated SOL.
How does a delegation become a reward?
At every epoch, the protocol tallies the vote credits earned by validators for voting on blocks that the network accepts. It combines those credits with the amount of active stake behind each validator, then allocates the epoch's inflationary issuance. A validator's commission is paid first; the remainder goes proportionally to its delegated stake accounts.
- Eligibility: only active stake participates; a newly created delegation must finish activating.
- Performance: missed votes reduce the validator's credits and therefore the reward available to it and its delegators.
- Commission: the advertised percentage is the validator's cut of rewards, not ownership of principal.
- Compounding: issued rewards land in the stake account and become active delegated stake automatically.
This is protocol accounting, not a validator manually sending payouts. An explorer can show the stake account, its delegated validator, epoch rewards and commission, allowing a wallet's display to be checked against on-chain state.
The wallet shows a balance, not a guaranteed yield
Annualized yield is an estimate derived from changing inputs: inflationary issuance, total active stake, validator voting performance and commission. The realized amount is calculated per epoch. A wallet may smooth those observations into an annual percentage, but it cannot make that rate fixed.
There are also costs and timing constraints. Creating and managing stake accounts requires signed transactions and network fees, while the account retains a rent-exempt reserve. Moving to another validator normally means deactivating and then delegating again, with state changes completed at epoch boundaries. That delay can leave some stake temporarily ineligible for rewards.
Who controls delegated stake?
The stake account answers that question through two authorities. The stake authority can delegate, deactivate, split and reassign stake. The withdraw authority can remove inactive SOL and can replace the stake authority, making it the more sensitive key. A validator receives neither authority merely because it receives a delegation.
The same authority check applies when a wallet presents a cross-chain route such as Manta Bridge: the useful question is what account or program receives control after the signature. Native delegation keeps withdrawal power with the user's key; staking through an exchange account does not.
Native delegation beats wrappers on custody
A stake pool offers a different bargain. The user deposits SOL into a program, receives a liquid receipt token, and lets a pool manager distribute stake among validators. That can simplify diversification and preserve tradability, but it adds pool fees, program risk, manager strategy and a market price for the receipt token.
Native delegation is the cleaner self-custody path because rewards and principal remain in chain-native stake accounts under explicit authorities. Its practical limit is operational: one stake account delegates to one validator, so diversification requires multiple accounts. Delegation makes reward sharing verifiable; it does not remove validator selection, commission changes or activation delays.
Filed under
- On-Chain Usage
- Account Security