Stake Account

Overview

A stake account separates staked value and delegation metadata from an ordinary spending balance. On Solana, it can hold delegated SOL and identify separate authorities for staking decisions and withdrawals. Delegation activates and deactivates according to epoch-based rules rather than becoming fully effective immediately. Rewards depend on network inflation, validator performance, commission, and active stake. The validator does not receive custody of the delegated principal through ordinary delegation.

Users must protect both authority roles, verify the selected validator identity, and understand lockups and warmup or cooldown timing. Splitting and merging accounts can support operations, but incorrect authority changes may permanently remove control. A wallet’s displayed stake balance may include inactive, activating, active, deactivating, and reward amounts with different liquidity.

Stake Account is an identifier or spendable object, not proof of legal ownership and not a secret credential. Authorization depends on keys, scripts, contracts, or protocol rules, while custodial systems may expose an identifier without giving the user direct control of the underlying account. Normalization, case conversion, truncation, and alias resolution need protocol-aware rules, because a visually similar value can represent a different destination or fail checksum validation. Systems storing Stake Account should preserve the exact value together with chain identifiers and type metadata.

Testing for Stake Account should include valid and invalid examples, wrong-network values, boundary encodings, contract destinations, and any memo or tag requirements. Higher-value transfers benefit from an independent destination check rather than reliance on shortened display text. Technical takeaway: A stake account records delegated value and authority, while activation state and withdrawal control determine when funds are usable.