How to Stake Tezos (XTZ)

How to stake XTZ in 2026: native delegation vs liquid staking vs exchange staking, validator selection, reward mechanics, and step-by-step delegation. Beginner-friendly.

What you'll need (prerequisites)

• XTZ held in a self-custodial wallet
• Wallet that supports tezos staking
• A small native-token reserve for transaction fees
• A shortlist of validators (use the chain's official dashboard)

Step-by-step

1. Step 1: Acquire XTZ

   Buy XTZ on a major exchange (Coinbase, Kraken, Binance) or via a DEX. Withdraw to a self-custodial wallet that supports Tezos.

2. Step 2: Choose a staking method

   Native staking: delegate directly from your wallet to a validator. Liquid staking: deposit into a liquid-staking protocol and receive a yield-bearing receipt token. Exchange staking: easiest UX but custodial. Pick based on your custody and yield preferences.

3. Step 3: Pick a validator / operator on Tezos

   For native staking, research validator uptime, commission rate (5-10% is typical), self-stake, and reliability history. Avoid concentrating in the largest validators — distribute to support decentralisation.

4. Step 4: Delegate

   In your wallet's staking tab (or the chain's official dashboard), select the validator and enter the amount. Confirm the transaction. There is usually a small network fee.

5. Step 5: Confirm and monitor rewards

   Rewards typically accrue per epoch (5 mins to 24 hrs depending on chain). Check your validator's performance weekly — if uptime drops, redelegate.

6. Step 6: Unstake when needed

   Plain delegation has no cooldown — delegated XTZ stays liquid. Funds you actively stake must be unstaked and then finalized: under current parameters that is about a 4-day wait (three cycles plus the remainder of the current one, cycles having dropped to roughly a day since the Rio upgrade).

Tezos has two different things called "staking" — pick the right one

Since the Paris-era protocol upgrades, Tezos offers two distinct roles for XTZ holders, and confusing them is the single biggest source of mistakes. Delegating points your tez at a baker's voting and baking power while leaving the tokens fully liquid: as the Tezos documentation puts it, there is "no risk to you; you retain full control of the tez, you can spend it at any time." Staking goes further — your tez is frozen in your own account, unspendable, and becomes part of the baker's security deposit. Staked funds count three times as much as delegated funds toward a delegate's baking power, which is why they are rewarded more and why they carry the baker's penalties.

The trade-off is explicit in the docs: delegation is risk-free but earns roughly a third of what staking earns; staking earns materially more and exposes you to slashing. Both roles require you to first choose a baker (delegate) — staking is layered on top of delegation, not an alternative to it. Note also that only accounts with a baking power of at least 6,000 tez can bake blocks, which is why almost everyone delegates or stakes with a professional baker rather than running one.

Unstaking: request, wait, finalize

Exiting a delegation requires nothing — the tez was never locked. Exiting a stake is a three-step process that trips people up. You submit an unstake request; the amount is removed from the staked balance but remains frozen and unfinalizable; after the protocol delay you submit a finalize unstake operation to return the tez to your spendable balance.

The delay is defined in cycles — the unstake finalization delay plus the remainder of the current cycle. Tezos documentation describes this as roughly a four-day wait (three cycles plus the time left in the current cycle) under current parameters. That short figure is the result of the Rio upgrade, which cut the cycle length from around three days to about one day; before Rio the same delay worked out to roughly ten days, which is why older guides quote much longer numbers. The Seoul upgrade then made finalize_unstake callable by any account rather than only the owner, which allows finalization to be automated by third-party bots — convenient, but do not assume someone will do it for you. Check your account and finalize manually if nothing has happened after the delay elapses.

Slashing: what a staker actually risks

Staked tez is slashable. The documentation is blunt: "your staked tez is subject to the same penalties as the baker's staked tez… in the rare event that your baker is punished ('slashed') for misbehaving, your tez is also slashed." External stakers are slashed in proportion to their contribution to the delegate's staking balance. Delegators — as opposed to stakers — are not slashed.

There are two punishable offences and they are penalised very differently. Double-baking carries a penalty of 5% of the delegate's stake, replacing the old fixed 640-tez penalty with a proportional one. Double-attestation is governed by Adaptive Slashing, introduced in the Paris protocol, which sizes the penalty by how much consensus weight was double-signed in that block: the slashed percentage follows a convex function that stays tiny for isolated accidents and saturates at 100% when a critical fraction — around a third of consensus weight — is implicated. The design goal is to distinguish a misconfigured baker from a coordinated attack, so a single baker's accidental double-attestation is a minor event while a correlated one is catastrophic.

The practical lesson is that baker selection matters far more for stakers than for delegators, and that spreading a staked position across bakers that do not share infrastructure protects you from the correlated case that Adaptive Slashing punishes hardest. One further parameter worth knowing: a delegate sets limit_of_staking_over_baking, capped globally at 9, which limits how much external stake it will accept relative to its own; stake beyond that limit is treated as ordinary delegation instead, which quietly moves you back to the lower reward tier.

Choosing a baker

Evaluate bakers on: reliability — missed attestations and any history of double-baking or double-attestation incidents, which are public on Tezos explorers; fee, since bakers set their own cut of rewards and can change it; whether the baker accepts external staking at all, and its limit_of_staking_over_baking setting, which determines whether your stake is treated as stake or demoted to delegation; capacity and self-stake; and operational transparency, including published key-management practice, since the offences that trigger slashing are almost always failover misconfigurations rather than malice. Established bakers that publish incident post-mortems are worth a slightly higher fee.

Where the yield comes from

Tezos rewards come from protocol issuance paid to bakers for baking and attesting, shared with delegators and stakers according to their contribution — with staked balances weighted three times delegated balances in the delegate's power calculation, and correspondingly rewarded more. Tezos's issuance is adaptive rather than fixed, adjusting with the staked ratio, so quoted rates move over time and across upgrades. Compare bakers on the rate net of fees, and remember that if you take the delegation route your gross rate is roughly a third of the staking rate — the difference is the price of not being slashable and not being locked.

Liquid staking on Tezos

Liquid staking arrived on Tezos later than on most chains and is still evolving, so verify status before committing. Third-party stXTZ implementations exist — youves documents an stXTZ liquid staked tez, and the team behind Stacy.fi launched an stXTZ on Etherlink, the EVM-compatible Tezos layer 2 — giving holders a transferable receipt token that accrues staking rewards while remaining usable in DeFi.

Separately, Tezos has pursued protocol-native liquid staking: a canonical LST design (referred to as sTEZ) that would aggregate stake at the protocol level rather than in an application contract, with mechanics shipped in the Ushuaia upgrade behind a feature flag. Because feature-flagged protocol functionality can be enabled, deferred or altered by governance, do not assume protocol-native liquid staking is live and usable simply because it has been announced — check current protocol documentation and the issuing application before depositing. As always with receipt tokens, you add smart-contract risk, a fee on rewards, and market-discount risk to whatever staking risk you already hold.

Risks worth pricing in

• Role confusion. Delegating is liquid and unslashable; staking is frozen and slashable. Know which one you clicked.
• Slashing. 5% of stake for double-baking; up to 100% for double-attestation at critical consensus weight under Adaptive Slashing.
• Unfinalized unstakes. Tez sits frozen and idle until finalize unstake is submitted.
• Overstaking demotion. Stake above a baker's limit_of_staking_over_baking is treated as delegation and earns the lower rate.
• Parameter churn. Tezos upgrades roughly twice a year and has changed cycle length, slashing and staking mechanics recently; treat any guide older than one protocol cycle as suspect, including the numbers here.
• LST maturity. Tezos liquid staking is younger and thinner than Ethereum's or Solana's; check TVL, audits and redemption mechanics first.

Sources

• Tezos Docs — Staking (delegating vs staking, ~4-day unstake delay, staker slashing, 6,000 tez baking power)
• Octez Docs — Staking mechanism (staked funds count 3x, 5% double-baking penalty, proportional staker slashing, limit_of_staking_over_baking capped at 9)
• Octez Docs — Adaptive Slashing (double-attestation penalty scales with consensus weight, saturating at 100%)
• Octez Docs — Protocol Rio (cycle length reduced to ~1 day; shorter unstake finalization)
• Octez Docs — Protocol Seoul (finalize_unstake callable by any account)
• youves Docs — stXTZ liquid staked Tezos

Common errors and fixes

• Validator missed blocks. Redelegate to a higher-uptime validator. Use your chain explorer to inspect validator performance metrics before redelegating.
• Delegation vs. slashing. If you simply delegate XTZ to a baker, your funds stay liquid and are never slashed — only double-baking or double-endorsing (equivocation) is penalized, and that falls on the baker's own bond and on funds you actively stake, not on ordinary delegators. Tezos does not slash for downtime; an offline baker just misses rewards. Pick a baker with a long, reliable uptime record.
• Tokens stuck in unstaking. Unstaking has a fixed protocol-level cooldown. Use liquid-staking receipt tokens (e.g. stETH, mSOL, jitoSOL) for instant exit liquidity via DEXes.
• Rewards not accruing. Confirm the delegation transaction succeeded on-chain. Some chains require a separate "claim rewards" transaction; check the chain docs.
• High commission eating yields. Validator commissions can be raised retroactively. Move to a lower-commission operator (typically 3-7%).

FAQ