Jump to content
Block Press

Protocol, chain and market reporting

Polygon PoS bridge vs zkEVM bridge: which fits?

Polygon PoS bridge vs zkEVM bridge comes down to the destination: PoS funds use the PoS route; Polygon zkEVM Mainnet Beta is sunset and no longer active.

The Block Press Editors5 min read

Polygon PoS bridge vs zkEVM bridge: which fits?

After choosing a destination, the Polygon PoS bridge vs zkEVM bridge decision is straightforward: use the PoS bridge for Polygon PoS; Polygon zkEVM Mainnet Beta is sunset and no longer an active destination for new transfers.

  • Choose by chain: Each canonical bridge connects Ethereum to one specific network.
  • Budget for the exit: PoS withdrawals wait for a checkpoint and a claim; zkEVM withdrawals historically relied on proof verification and a claim.
  • Check current status: Polygon’s current support information says zkEVM Mainnet Beta has been sunset. Confirm network status before relying on older bridge descriptions.

Polygon PoS and Polygon zkEVM are separate chains. A wallet showing a Polygon-branded network does not make the bridge routes interchangeable; the destination chain determines where the assets arrive and which applications can use them.

The destination chain determines the bridge and gas token

The Polygon PoS bridge serves Polygon PoS, while the Polygon zkEVM Bridge was built for the separate zkEVM rollup. For a live PoS transfer, the destination balance needs POL for Polygon transactions; on zkEVM, the historical gas token was ETH. The bridge route and the destination network’s status both matter before you sign.

Take two otherwise identical transfers of the same supported asset from Ethereum. In the first case, the funds are for a Polygon PoS app: choose the PoS bridge and plan to pay POL for later transactions on that chain. In the second, the funds are intended for a zkEVM app: historically, the zkEVM bridge was the matching route and ETH paid its network gas. The only changed factor is the destination, so the matching bridge changes too. Today, however, zkEVM Mainnet Beta is sunset; that second case is not a live new-transfer choice.

The broader Polygon bridge context identifies the Ethereum-to-Polygon PoS route and helps distinguish it from other Polygon networks. It does not make a PoS deposit arrive on zkEVM: each canonical bridge connects Ethereum to its own chain.

Security and exit timing follow each bridge’s settlement model

The PoS bridge relies on its validator set signing checkpoints, while the zkEVM bridge relied on validity proofs verified on Ethereum. Those different settlement mechanisms shape the return trip and the wait before assets can be claimed on Ethereum.

For a Polygon PoS withdrawal, Heimdall coordinates checkpoints that record Polygon activity on Ethereum; Bor produces blocks on the PoS chain. The withdrawal must be included in a checkpoint before the Ethereum-side claim can be made. That means two stages: wait for the checkpoint, then submit a claim transaction on Ethereum.

For a zkEVM withdrawal, the validity proof attests to the rollup’s state transition and is checked on Ethereum. Once the proof is verified, the withdrawal can be claimed on Ethereum. It does not use the Plasma Bridge’s seven-day challenge period. Plasma exits have that separate challenge window; it should not be mistaken for the validity-proof finalization path.

Neither route removes the need to budget for the destination-side claim. PoS uses POL for gas on the PoS chain, while its Ethereum claim needs ETH. The historical zkEVM route used ETH for gas there and for its Ethereum-side claim. For any transfer, check which transaction happens on which network before estimating the full cost.

The practical limit is now decisive: Polygon’s current support information says zkEVM Mainnet Beta has been sunset, its sequencer has stopped, and Polygon Portal no longer supports bridging to or from it. The zkEVM bridge’s former proof-based withdrawal design explains how that route worked; it does not mean the network is available for a new transfer today. The current Polygon bridge route for a new transfer is the one to Polygon PoS.

Crossing from PoS to zkEVM requires Ethereum in between

The canonical PoS and zkEVM bridges each connect only to Ethereum, so a move from Polygon PoS to zkEVM is not a direct bridge transfer. The funds must first exit PoS to Ethereum, then be deposited from Ethereum to the other chain. That route takes two Ethereum transactions: the PoS withdrawal claim and the new deposit.

That extra leg affects both cost and timing. The PoS exit needs its checkpoint and claim; then the Ethereum deposit needs its own transaction and confirmation before the destination balance is available. If zkEVM is sunset, the second leg is not a viable new deposit at all. For stranded assets, use Polygon’s current recovery information rather than treating the old canonical bridge flow as active.

Who each bridge suits

The PoS bridge suits transfers intended for Polygon PoS apps and balances, provided the asset has a supported route. The historical zkEVM bridge suited transfers intended for zkEVM apps, with proof-based exits and ETH gas, but Polygon zkEVM Mainnet Beta’s current sunset status rules it out for new transfers.

Before choosing, confirm the destination network in the app and Polygon’s current network information, then check that the asset has a supported route. For a live Polygon PoS destination, select the PoS bridge and keep POL for activity there plus ETH for an eventual Ethereum claim. For a different or retired destination, do not infer availability from an old bridge description.

Is Polygon zkEVM the same network as Polygon PoS?

No. Polygon PoS and Polygon zkEVM were separate networks with separate canonical bridges, security models, and gas tokens. A transfer to one does not arrive on the other.

Why does a zkEVM withdrawal finish without a 7-day wait?

Its historical exit path depended on a validity proof verified on Ethereum, followed by a claim. The seven-day challenge period belongs to Plasma exits, a different mechanism. Polygon zkEVM Mainnet Beta is now sunset, so this describes the former bridge design, not an available new route.

Which tokens can each bridge carry?

Only assets with a supported route on the relevant bridge can be transferred. Check the current route and network status before sending; the available token set cannot be assumed to match between bridges.