Staking Through a Validator: Delegation, Warm-Up and Unbonding

Two very different things called staking

“Stake your Solana and earn a yield” describes at least two products with different risk. In one, you hold the key and delegate to a validator; in the other, you transfer the asset to a company that stakes it and owes you a balance. Both show a percentage. Only one of them leaves you holding the coins.

The flows published by Coinbase Cloud, which runs validators for several networks, describe the first kind. They are worth walking step by step because the steps are the product. What a reader learns from them is not the yield; it is the sequence of signatures, waits and fees that stand between a balance and a reward.

Polygon: approve, delegate, wait nine days

The documented Polygon flow has four moving parts:

1. Connect a self-custody wallet — Coinbase Wallet, MetaMask or similar — to the staking interface, and sign to confirm the connection.
2. Choose a validator from the published list.
3. Enter the amount to delegate, and approve.
4. Sign a second transaction that actually performs the delegation.

The two-transaction structure is a token allowance followed by the delegation call, and it is the same pattern that makes token approvals worth reviewing rather than clicking through. The first signature grants a contract permission to move your tokens; the second uses it. Neither hands custody to the validator operator, who runs the node and earns commission but never holds the delegator’s keys.

The exit is where the time cost appears. The unbonding flow lets a delegator choose 25%, 50%, 75% or 100% of the stake, confirm, and sign in the wallet. The confirmation message is “Unbonding Initiated”, and the documentation states that funds are returned after an unbonding period of approximately nine days.

Nine days is not a fee and not a delay the operator can waive. It is the chain’s rule, expressed in the protocol rather than in the operator’s terms. Any product that promises “instant unstaking” on a chain with an unbonding period is either lending you liquidity against the stake or taking the other side of the trade.

Sui: a table worth reading line by line

The Sui guide publishes its parameters as a table, which makes it the clearest of the three to compare:

Three of those four rows change what the product is. A minimum of 1 SUI sets the smallest position that can exist, and therefore the smallest account for which the product is meaningful at all. The warm-up means a delegation does not earn from the moment it is signed; rewards begin in the epoch after. The service fee is a share of rewards, not of principal, and it sits alongside a validator commission paid to whoever manages the validator.

The absence of an unbonding period is the notable row. It means the exit is an epoch boundary rather than a fixed waiting time, and it means the product behaves more like a liquid balance than the Polygon flow does. Two chains, two entirely different time costs, and the same marketing word.

Solana: inflation is the yield, and the fee comes out of it

The Solana FAQ answers three questions that most staking pages leave implicit.

Where the yield comes from. Inflation started at 8% in February 2021 and is described as declining by 15% annually until it reaches a steady state of 1.5%. The reward rate depends on the network’s staking rate, so the same staked amount earns less as more of the supply is staked. A published rate is a snapshot of that ratio, not a fixed coupon.

How the operator is paid. Coinbase charges a percentage service fee on all rewards earned by tokens delegated to its validator, and the FAQ says the fee is paid to Coinbase automatically by the protocol. The delegator withdraws rewards from the protocol directly. That is a materially different arrangement from a fee deducted from a custodial balance: the protocol enforces it, and the delegator can see it.

What can go wrong. The FAQ states that slashing is not currently enabled on Solana but may be enabled in the future. It also carries a disclaimer that reward rates published by Coinbase are estimates based on third-party information, are not verified or guaranteed, and that staked assets may be subject to slashing penalties with possible loss of up to the full principal. For a product whose headline is a percentage, that is the sentence that matters most.

What a provider can and cannot change

The three flows share a structure that is easy to lose behind the differing numbers. The operator can control:

• Which validator the delegation points at, and therefore its uptime and commission.
• The service fee it charges, including any notice it gives before changing it. Coinbase’s Sui guide says the commission may change during the validator’s lifetime to avoid running an outsized share of the network.
• The documentation, which is the only place most delegators will ever see the warm-up and unbonding rules stated plainly.

The operator cannot control the unbonding period, the epoch length, the issuance schedule or whether slashing is enabled. Those are protocol parameters, and treating them as provider promises is the single most common category error in staking.

What a provider page should disclose

Because the waits are protocol facts, a provider that documents them is not being generous — it is being accurate. Five disclosures separate a page that can be read from one that has to be decoded:

1. The warm-up. When rewards start, in the protocol’s own units — the next epoch, as on Sui, rather than “shortly”.
2. The exit. One number, in days or epochs: approximately nine days on Polygon in the guide read here, none on Sui.
3. The fee basis. Whether the percentage applies to rewards or to principal, and who deducts it — the protocol, as Coinbase describes for its Solana validator, or the operator from a balance.
4. The minimum. One SUI on Sui, which is the smallest position the product can represent and therefore the size below which it does not apply at all.
5. The failure mode. Slashing status, and whether the operator can change its commission. Coinbase’s Sui guide says the commission may change during the validator’s lifetime so that one operator does not end up running an outsized share of the network — a legitimate reason, and still a change a delegator should expect.

A page missing any of the five is leaving the delegator to infer a parameter that decides how long their money is unavailable. That inference is the expensive part, not the yield.

The question to ask before delegating

Four questions separate one staking offer from another, and none of them is “what is the APY”.

1. Who signs the delegation transaction? If the answer is “you, from your own wallet”, the asset never leaves your control and the counterparty risk is the validator’s performance. If the answer is “we do”, you hold a claim.
2. What is the unbonding period, in the protocol’s units? Nine days, one epoch, or none — the number is published by the chain and repeated (or not) by the provider.
3. What is the fee charged on, and by whom? Rewards versus principal, deducted by the protocol versus taken from a balance.
4. Can the principal be lost? Slashing status, validator commission changes, and whether the product is insured in any way.

The comparison articles on this site take the same approach from other angles. Liquid staking versus native staking covers the trade-off between a receipt token and a direct delegation; where exchange earn yield comes from separates issuance from balance-sheet promises; and custodial versus non-custodial wallets is the underlying question about who holds the key in every product that pays a yield on a coin you cannot see.

Risk note. Minimums, warm-up and unbonding periods, service fees, inflation parameters and slashing status in this article were read from Coinbase Cloud’s published staking guides on 2026-10-30. Protocol parameters and provider terms change, and rates quoted by any provider are estimates. Nothing here is investment advice.