Home › News

A One-Page Checklist for Someone Making Their First Native SOL Delegation

Published: 11.11.2026

Moving Solana tokens off a centralised exchange to participate in network validation is a distinct shift in posture. The holder is no longer an observer relying on an intermediary; they are an active participant choosing a specific node to secure the ledger. This transition, however, introduces mechanical steps and custody responsibilities that exchange interfaces conveniently obscure. Before executing a native delegation, a clear sequence of checks must be satisfied to ensure the tokens are exposed only to the intended validator and that the stake account is structured correctly.

The Decision to Stake Natively

Native delegation differs fundamentally from liquid staking. When a holder delegates natively, the SOL is locked in a stake account and cannot be transferred or traded until deactivated. There is no receipt token to deploy in decentralised finance protocols. The sole return is the yield generated by the chosen validator. This path suits a holder whose priority is maximum security and direct network participation, rather than capital efficiency. If liquidity is required before an epoch boundary, native staking is the wrong mechanism.

Pre-Delegation: Wallet and Funds Preparation

Custody and Wallet Compatibility

The first requirement is a self-custodial wallet that supports the Solana staking interface. Not all wallets do. The chosen software must be capable of creating a stake account, a distinct on-chain entity separate from the main token account. Hardware wallets add a critical layer of verification; any delegation transaction must be signed on the device, ensuring malware on the host machine cannot redirect the delegation to a malicious validator. Before proceeding, confirm the wallet software is updated and the recovery phrase is verified offline.

Sufficient SOL for Rent and Fees

Solana's account model requires accounts to maintain a minimum balance to exist on-chain, a mechanism known as rent-exemption. Creating a stake account requires a deposit of approximately 0.0228 SOL, which covers the rent-exempt reserve and the initial delegated amount. Furthermore, transaction fees—though fractions of a SOL—must be paid from the wallet's main account. A wallet holding exactly 50 SOL cannot delegate all 50 SOL. A small buffer must remain to cover account creation, rent, and future transaction fees. Attempting to delegate the exact total balance will result in a failed transaction.

Understanding the Stake Account Architecture

Native staking does not simply lock the tokens in a primary wallet address. It creates a new, dedicated stake account. This account contains two critical authority keys: the stake authority and the withdraw authority. The stake authority permits the holder to delegate or re-delegate the tokens to a different validator. The withdraw authority permits the holder to move the tokens back to the main wallet or change the lock-up schedule. For maximum security, these authorities can be assigned to separate keys—for instance, keeping the withdraw authority on a hardware wallet while using a hot wallet for the stake authority. Verifying that these authorities are correctly set before funding the account is an essential security check.

Selecting a Validator

Choosing a validator is the most consequential decision in native delegation. The network's health depends on a diverse set of validators; delegating to the largest or most marketed validators increases centralisation. The assessment must go beyond superficial yield promises.

Performance Metrics Beyond APY

A validator's effectiveness is measured primarily by its block production rate and skip rate. A high skip rate indicates the validator is consistently missing its scheduled slots to propose blocks, which directly reduces the yield paid to delegators. Look for validators with a skip rate consistently below 5%. Advertised APY is often a projection based on a perfect 100% uptime and current network inflation; historical performance is a more reliable indicator. Independent block explorers and validator directories provide unredacted performance histories.

Commission Structures

Validators take a commission on the inflation yield before distributing the remainder to delegators. A 10% commission is standard, providing enough revenue for the validator to cover server costs without excessively draining delegator yield. A 0% commission is often a temporary promotional rate that will eventually be raised, while a 100% commission sends all yield to the validator, leaving the delegator with nothing. Check the validator's history for sudden commission hikes, a practice known as commission spoofing, where a validator attracts stake with a low rate and then raises it drastically once a large amount of SOL is locked.

Executing the Delegation

The Transaction Mechanics

Delegating is a two-step process at the protocol level, though most wallet interfaces abstract this into a single click. First, the wallet creates the stake account and funds it. Second, it assigns the stake account to a specific validator's vote account. The critical check here is the vote account address. A validator's identity account and their vote account are different. Delegations are made to the vote account. Verifying the exact vote account address against the validator's official documentation prevents phishing attempts where malicious actors mimic validator identities.

Confirming the Stake Account

Once the transaction is submitted, it requires confirmation on-chain. Do not close the wallet or navigate away until the transaction ID shows as finalised. Due to Solana's speed, this usually takes under a second, but network congestion can cause delays. After confirmation, the stake account should appear in the wallet's staking tab, showing the delegated amount and the status as "activating" or "active".

Post-Delegation: Monitoring and Unstaking

Reward Accrual and Compounding

Native staking rewards do not automatically compound. Yield is paid into a separate rewards account, distinct from the locked stake account. To compound—that is, to add the earned yield to the actively staked balance—the delegator must manually issue a transaction to stake the accrued rewards. This incurs a standard transaction fee. For small stakes, the gas cost of frequent manual compounding may outweigh the marginal yield increase; less frequent compounding is often more efficient.

The Deactivation Waiting Period

Unstaking SOL requires initiating a deactivation command. The tokens do not become liquid immediately. Solana epochs currently last roughly two to three days. If deactivation is requested mid-epoch, the stake remains active for the remainder of that epoch, continuing to earn rewards, and then fully deactivates at the end of the next full epoch. The tokens can only be withdrawn to the main wallet balance once the stake account status reads "inactive". Planning for this delay is essential; native staked SOL cannot serve as emergency liquidity.

Final Verification Checklist

Before signing the delegation transaction, run through these operational checks:

• Self-custody confirmed: The wallet is non-custodial and the recovery phrase is secured offline.
• Buffer maintained: At least 0.05 SOL remains unbudgeted to cover rent-exemption and transaction fees.
• Authorities verified: The stake and withdraw authorities for the new stake account are correctly assigned to the intended keypairs.
• Validator vetted: The chosen validator has a low skip rate, a sustainable commission (typically 5–10%), and no history of commission spoofing.
• Vote account verified: The delegation target is the official vote account address, confirmed against the validator's documented identity.
• Liquidity accepted: The holder accepts that unstaking will take up to two epoch boundaries (approximately four to six days) before the SOL is spendable.

For a separate perspective on this decision, this discussion of native and liquid staking trade-offs. Confirm that the referenced information is current before relying on details such as fees, support or timing.

Completing these checks transforms the first native delegation from a hopeful click into a verified, structurally sound participation in the Solana consensus mechanism.