How Polygon PoS checkpoints anchor withdrawals in 2026

Polygon PoS checkpoints anchor withdrawals by recording commitments to ranges of Polygon blocks on Ethereum. That gives a withdrawal a way to prove that its token burn happened before the bridge releases the corresponding asset on Ethereum.

Polygon PoS runs its own blocks on Bor, while Heimdall coordinates validator activity and checkpoints. The checkpoint is a compact record of a range of Bor blocks, not a copy of every transaction on Ethereum. For the broader bridge flow and route choices, see Polygon Bridge. The key point is that a withdrawal must wait until a checkpoint covers its burn block.

What does a Polygon PoS checkpoint record?

A checkpoint records a cryptographic summary of a span of Bor blocks and its start and end block numbers. The summary is a Merkle root: a single hash that can be used with a short proof to show that a particular block belongs to the committed range. Heimdall validators agree on the checkpoint, and it is submitted to a contract on Ethereum.

This gives Ethereum contracts a reference point for checking a withdrawal. A checkpoint does not post all Polygon transactions to Ethereum or make Ethereum re-run them. Polygon PoS is a sidechain with its own validator set, so the checkpoint reflects that system’s consensus. It should not be confused with a rollup that posts transaction data and validity proofs to Ethereum.

How does a checkpoint let you withdraw?

A standard withdrawal from Polygon PoS to Ethereum has two main stages: burn on Polygon, then exit on Ethereum. The burn removes the bridged tokens from circulation on Polygon. The exit submits proof of that burn so the Ethereum bridge contract can release the matching tokens.

• Start the withdrawal on Polygon PoS. This burns the bridged tokens and creates the transaction record.
• Wait for a checkpoint that covers the block containing that transaction. Until then, the Ethereum side cannot confirm the burn against a checkpoint.
• Submit the exit on Ethereum with a proof linking the burn transaction to the checkpointed block range.
• After the contract accepts the proof, it releases the tokens on Ethereum. The exit requires an Ethereum transaction and gas.

The proof is more than a transaction hash: it includes the information needed to show the burn sits inside a block that sits inside the checkpoint. In practice, the bridge interface or a proof service prepares this data. A delay while waiting for a checkpoint is part of this withdrawal design; it is not the same as a failed burn.

What should users expect from checkpoints in 2026?

Checkpoints are the bridge’s on-chain anchor, but they do not make withdrawals instant. Timing depends on when the relevant range is checkpointed and on Ethereum transaction processing. A checkpoint delay can therefore leave a withdrawal waiting even after the Polygon burn is visible.

For users, the practical choice is straightforward: use the Polygon PoS withdrawal flow when you want the bridge’s Ethereum release process and can wait for its checkpoint and exit steps. Before confirming the burn, check that you have selected the right destination and can pay Ethereum gas for the final claim. Polygon’s support guidance says an initiated withdrawal cannot be cancelled or reversed, though the final exit can be completed later.

In short, a checkpoint does not move tokens by itself. It lets the Ethereum bridge verify that a Polygon burn belongs to an agreed block range, which is the evidence needed to release the bridged asset.