How to Stake Polygon (POL)

How to stake POL in 2026: native delegation vs liquid staking vs exchange staking, validator selection, slashing risk, and step-by-step delegation. Beginner-friendly.

What you'll need (prerequisites)

• POL held in a self-custodial wallet
• Wallet that supports polygon 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 POL

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

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 Polygon

   For native staking, research validator uptime, commission rate (5-10% is typical), self-stake, and slashing 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

   Unbonding POL is measured in checkpoints — Polygon's docs describe an 80-checkpoint lock (~30 minutes each) and Polygon support cites 82 checkpoints, roughly 3-4 days. When it expires you must submit a separate claim transaction on Ethereum.

How POL staking actually works — on Ethereum, not on Polygon

The single most counter-intuitive fact about staking Polygon is that you do not do it on Polygon. As Polygon's developer documentation states, "all staking transactions of Polygon Chain take place on Ethereum for security reasons." The validator registry, the delegation accounting and the checkpoint logic live in contracts on Ethereum mainnet. Delegating, claiming rewards, restaking and unbonding are all Ethereum transactions, signed from an Ethereum-network wallet and paid for in ETH gas. If you have POL sitting on the Polygon PoS chain, it is in the wrong place: staking requires POL on Ethereum mainnet.

POL is the token that replaced MATIC as Polygon's native gas and staking asset in the migration that began on 4 September 2024 at a 1:1 ratio; guides written before then refer to "staking MATIC," which is the same mechanism under the old ticker. Validators periodically submit checkpoints — signed attestations of Polygon block ranges — to Ethereum, and rewards are distributed per successful checkpoint signature. This is why validator uptime translates so directly into your yield on Polygon: a validator that misses checkpoints forfeits the reward share attached to them, and so do its delegators.

Unbonding: checkpoints, not days

Polygon's lock-up is denominated in checkpoints rather than clock time. The delegation documentation describes withdrawn stake being locked for 80 checkpoints, with each checkpoint taking roughly 30 minutes; Polygon's support material describes the unbonding period as 82 checkpoints, commonly quoted as about three to four days. Both are correct in the sense that checkpoint cadence is not fixed — it depends on validator submissions and on Ethereum conditions — so the honest answer is: plan for three to four days, and understand that congestion on Ethereum can stretch it.

Two important asymmetries follow. Moving stake between validators (redelegation) does not incur the checkpoint lock — the transfer completes with an Ethereum confirmation, so fixing a bad validator choice is fast and cheap in time, if not in gas. And unbonding is a two-step process: after the lock expires you must submit a separate claim/withdraw transaction on Ethereum. POL sitting in the unbonded-but-unclaimed state earns nothing.

Slashing on Polygon: contracts exist, enforcement does not

Polygon's staking contracts contain slashing functionality, and slashing is referenced in the protocol design, but automated stake confiscation is not currently applied to delegators on Polygon PoS. Discipline is instead enforced economically: validators that miss checkpoints or run poorly forfeit the reward share tied to those signatures, and sustained underperformance can cost an operator its place in the capped active validator set. Polygon's own delegation guide is silent on delegator slashing precisely because there is no live mechanism to describe.

Do not turn that into "Polygon staking is safe." It changes the shape of the risk rather than removing it. Your losses on Polygon come from missed rewards, from commission, from ETH gas paid on every interaction, and from three-to-four days of price exposure you cannot exit — not from a slash event. It also means the market mechanism that disciplines validators is slow: unbonding and redelegating away from a bad operator takes time and gas, so bad operators can underperform for a while before capital leaves.

Minimums, gas and the economics of small positions

Polygon imposes no protocol minimum on delegation — the docs say there is no minimum stake amount and suggest simply starting with 1 POL — but the economic minimum is significant, and it is set by Ethereum gas rather than by Polygon. Every action (delegate, claim rewards, restake, unbond, withdraw) is an Ethereum mainnet transaction. Polygon's documentation recommends keeping roughly 0.05–0.1 ETH available for gas, and notes that restaking or claiming rewards requires a minimum of 2 POL of accrued rewards to execute.

Run the arithmetic before you stake. If a delegation is small enough that a year of rewards is worth less than the gas required to enter, compound and exit, native staking is value-destructive no matter how attractive the advertised APR looks. Batch your claims — quarterly or annually rather than weekly — and time transactions for low-gas periods. This gas overhead, not slashing, is the defining risk of Polygon staking for retail-sized positions.

Choosing a validator

Polygon's active validator set is capped, which makes the selection list short enough to actually read. Judge candidates on: checkpoint signing performance (the direct driver of rewards — look at signed versus missed checkpoints, not marketing uptime), commission and how often the operator has changed it, self-stake, and the operator's public identity and track record across other networks. Because there is no delegator slashing, the marginal value of picking a "safe" operator is lower than on Cosmos chains and the marginal value of picking a reliable one is higher: on Polygon, validator quality shows up almost entirely as reward yield.

Where the yield comes from

Polygon staking rewards have historically been funded from a dedicated emission pool plus a share of network fees, distributed per checkpoint to validators and their delegators after commission. The rate you actually receive is the gross rate minus the validator's commission, minus the drag of Ethereum gas across your claim cycle, spread over the periods your stake was actually active. Because the reward pool is shared across all staked POL, the per-token rate falls as more POL is bonded. Treat any quoted APR as a snapshot from the staking portal at that moment, and compute your own realised yield after gas at the end of the year — for most small delegators the two numbers diverge substantially.

Liquid staking on Polygon has contracted — check before you rely on it

This is the section where Polygon differs most from other proof-of-stake networks, and where outdated guides are actively harmful. The two flagship liquid staking tokens for Polygon are gone or going. Lido ended its Polygon deployment, sunsetting stMATIC in 2025 to refocus on Ethereum. Stader has announced the discontinuation of MaticX, halting new deposits and moving the token into a claim-only redemption phase with a published wind-down schedule, after which redemptions must be made directly against the smart contract.

The practical guidance is therefore: do not assume a Polygon LST you read about in a 2023 or 2024 article is still accepting deposits. If you hold stMATIC or MaticX today, your task is redemption within the published windows, not yield optimisation. If you want liquid exposure to staked POL, verify on the issuer's own site that the product is live and open before depositing, and check DeFi Llama for current TVL rather than trusting an aggregator listing. Native delegation via the official staking portal remains the reliable path, with the three-to-four day exit as the cost.

Risks worth pricing in

• Gas risk. Ethereum fees are the dominant cost for small delegators and can exceed a year of rewards.
• Wrong-network risk. POL on Polygon PoS cannot be staked; it must be bridged to Ethereum mainnet first.
• Two-step exit. Unbonding does not return funds automatically; a separate withdrawal transaction is required after the checkpoint lock.
• Missed-checkpoint risk. Validator downtime shows up as lost rewards rather than a slash, and it is easy not to notice.
• Deprecated-LST risk. Major Polygon liquid staking tokens are winding down; verify status before depositing and mind redemption deadlines.
• Approval hygiene. Staking involves ERC-20 approvals on Ethereum — review and clean them up periodically (see how to revoke token approvals).

Sources

• Polygon Docs — Delegate tokens (staking happens on Ethereum; 80-checkpoint lock; 2 POL claim minimum; 0.05–0.1 ETH gas)
• Polygon Support — What is the unbonding period? (82 checkpoints, ~3–4 days)
• Polygon — MATIC to POL migration (POL as native gas and staking token, 1:1, from 4 Sept 2024)
• Polygon Docs — Delegation via validator shares
• Stader — MaticX status and redemption

Common errors and fixes

• Validator missed blocks. Redelegate to a higher-uptime validator. Use your chain explorer to inspect validator performance metrics before redelegating.
• Slashing event. Native slashing is irreversible. Double-check the validator slashing history before delegating; for liquid staking, the protocol absorbs slashing across the pool.
• 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