Native SOL staking: delegate, earn, deactivate and withdraw

What your delegation does

Solana's proof-of-stake system uses stake in consensus participation. Native delegation assigns stake from a stake account to a validator's vote account. The operator runs the validator infrastructure; your stake account records your position.

Rewards depend on the network's reward conditions and the validator's participation and commission. A quoted annual rate is a summary using a source's method. It is different from a fixed payment contract or the actual amount credited in a particular epoch.

For a practical example, suppose Alice intends to stake 10 SOL while keeping a separate ordinary-account balance for transaction fees. Her wallet creates or manages a stake account, sets its authorities and delegates to the chosen vote address. This uses staking instructions, not an ordinary payment to an operator.

The stake account has its own address, so Alice can inspect the same position through an explorer or another compatible tool. It is useful to save that address alongside the validator's vote address from the start.

Understand the account before confirming

A stake account contains a staking authority and a withdrawal authority. The staking authority manages operations such as delegation, deactivation and supported splits or merges. The withdrawal authority controls eligible withdrawals and can change the staking authority under the stake rules.

In a self-managed setup, your signing arrangement can hold both roles. They can also be separate addresses. A managed staking product can ask for a particular management authority while leaving withdrawal control with you. Read the actual transaction and resulting state.

Account lockups introduce another condition: the custodian and lockup rules can affect when certain actions are permitted. An account that you can inspect publicly is not necessarily withdrawable at the current moment.

Creation and account storage need their own funding, and later actions need a transaction fee payer. Check how your wallet describes its entered stake amount and minimum required balance. Avoid treating a balance figure, delegated amount and effective stake as interchangeable fields.

Choose a validator using comparable evidence

Find the validator through the wallet's native-staking flow or the operator's published profile. Compare the full vote address. A short name or logo can be copied, while the vote address identifies the target of the delegation.

Inspect current commission and dated participation evidence. A recent yield display should identify the delegator's return, period and provider. Compare like with like rather than combining a validator's total income rate with a delegator APY.

Use a source that explicitly reports delegator yield and documents its period, included streams and fee treatment. A total-validator income metric can include operator revenue and cannot answer the same question.

Selection also has a distribution dimension. Delegating to separate independent operators is different from merely choosing several vote addresses controlled by the same operator. The distribution guide explains those observations.

Staking authority and withdrawal authority

Create and delegate the position

In the supported native-staking flow, select the source wallet account, intended amount and validator. Review stake-account creation or selection, the resulting authorities and target vote account before signing.

After execution, save the transaction signature and stake-account address. Open the account and verify that its delegation points to the expected vote address. Also confirm the authorities; the operator's vote account should not have silently replaced your withdrawal role.

New delegation enters activation under network rules. The account can have a total balance greater than the stake currently effective for participation. Read the actual activation state and relevant epoch rather than assuming the wallet's initial success message means all funds were instantly effective.

If a wallet does not show the account clearly, use its public address to inspect it. A display problem is easier to diagnose when you retained the position identity at creation.

Read effective stake and epoch rewards

An epoch is a protocol period used in staking and other network operations. Activation and deactivation evolve through epoch-related rules and network conditions. A countdown to an epoch boundary is a useful observation, not a universal withdrawal promise.

Check the stake account that earned the reward. Its credited amount can increase the position, while deposits and other operations can also change balance. Use reward records to identify actual reward income rather than attributing every increase to staking.

Additional product or MEV distributions can use separate mechanisms. Keep their records distinct until the method clearly establishes what is included. The epoch-reward guide shows how to build a factual history.

If you compare results over time, retain the period, authority/account changes and effective stake context. A recently activated position and one effective throughout the period are not equivalent observations.

Deactivate, observe and withdraw

To use the ordinary native exit, request deactivation through the supported wallet flow using the required authority. Then inspect the account until the amount you intend to withdraw is in a withdrawable state under the network and lockup rules.

The deactivation request and withdrawal are separate actions. When eligible, submit the withdrawal to the intended destination and save its signature. Reconcile the resulting ordinary SOL receipt and any remaining stake-account balance.

Some products offer a quoted immediate conversion or market exit. That route exchanges the position under a price quote and differs from waiting through normal deactivation. Compare the actual amount received and charges rather than treating every exit button as the same mechanism.

Keep enough accessible SOL for later transaction fees. A position becoming eligible for withdrawal does not by itself provide the fee payer needed for the claim transaction.

Keep one clear record for the whole lifecycle

Alice's 10 SOL example should leave a chain of evidence: creation and delegation signature, stake account, authorities, target validator, observed activation, reward records, deactivation and final withdrawal.

For a partial exit or a second validator, the position can involve supported splits or additional stake accounts. Preserve the relationship between the original and resulting accounts so balances and rewards remain explainable.

Continue with changing validators when the target needs to change, or the staking-method comparison when choosing between account control and a liquid pool token.

Common questions