When Is a Polygon Treasury Withdrawal Complete?

A Polygon PoS treasury withdrawal is complete when the Ethereum exit transaction succeeds, releases the asset to the intended treasury address and reaches the finality standard the treasury uses for accounting. A successful burn on Polygon starts the process; it does not prove that funds have arrived on Ethereum. The record must connect the burn, its checkpoint and the exit that unlocks the corresponding asset.

What does a Polygon PoS withdrawal do?

A PoS bridge withdrawal burns the Polygon-side representation of an asset, then uses proof of that burn to release the corresponding asset on Ethereum. The burn transaction is the start of the withdrawal, not its completion. The Polygon Bridge’s PoS transfer mechanics explain the broader lock, mint, burn and unlock model. For a treasury, the key distinction is that each stage produces a different piece of evidence.

First, the Polygon transaction must succeed and emit the relevant burn or withdrawal event for the token and amount being moved. A wallet prompt, a submitted transaction hash or a pending transaction is not evidence of a completed burn. A failed or reverted transaction cannot support a valid exit. Record the Polygon transaction hash, token contract, amount, sending address and destination Ethereum address so the later stages can be matched to this withdrawal.

The bridge then needs a checkpoint that covers the Polygon block containing the burn. Polygon validators submit checkpoints to Ethereum; the checkpoint commits to Polygon block data, allowing an exit proof to establish that the burn occurred in a committed block. A checkpoint for a later block is not enough unless it covers the burn’s block. Until the necessary checkpoint is available, the withdrawal may be pending even though the Polygon transaction succeeded.

This describes the PoS bridge path for supported, mapped assets. A treasury should identify the route and asset before applying these checks: native POL and Plasma withdrawals use a different exit path, while other Polygon networks and bridge systems can have their own claim mechanics. A status label from one flow should not be treated as proof for another.

Which on-chain records prove the exit?

The Ethereum exit transaction proves that the withdrawal was executed on the destination chain if its receipt reports success and the contract effects match the intended transfer. A checkpoint proves that the burn can be verified; it does not itself release the asset. The exit call submits the burn proof to the relevant Ethereum bridge contracts, which process the withdrawal and unlock the asset.

Verify the whole chain of evidence, not just the interface’s status. The Ethereum exit should refer to the Polygon burn through the proof and bridge state, and its successful execution should produce the expected release to the treasury. For an ERC-20 withdrawal, check the token contract and recipient in the Ethereum transfer event, then compare the amount with the bridge’s withdrawal record. A generic “transaction successful” indicator is insufficient if the transfer went to another address or involved a different token contract.

• Polygon burn receipt: successful execution and the expected token and amount.
• Checkpoint: Ethereum record showing a checkpoint that covers the burn’s Polygon block.
• Ethereum exit receipt: successful execution of the claim or exit call.
• Release evidence: the expected asset credited to the intended treasury address.

For accounting, retain both transaction hashes and the relevant block references, along with the token contract addresses on each chain. Bridged tokens can have different contract addresses on Polygon and Ethereum, even when they represent the same asset. Match the amount using the token’s units and decimals, and reconcile any difference against the bridge’s documented asset mapping or transfer record. A balance increase on its own is weaker evidence: another transaction could have sent the same token to the treasury.

When should treasury records mark it complete?

Mark the withdrawal complete only after the Ethereum exit succeeds, the expected asset reaches the intended address and the destination block meets the treasury’s confirmation or finality policy. If the exit is still pending, reverted or not yet final under that policy, classify it as in progress. This keeps “burned on Polygon,” “claimable on Ethereum” and “received by treasury” as separate states in the ledger.

Operationally, the treasury should reconcile the bridge event and Ethereum transfer against the original request before closing the entry. Confirm that the recipient is the treasury address, the token contract is the expected one, and the amount matches after accounting for token units. If a multisig controls the treasury, the exit’s recipient must match the address that the proposal authorized; a signer approval or queued proposal is not proof of receipt.

The practical test is compact: the Polygon burn is successful, a covering checkpoint supports its proof, and a successful Ethereum exit has released the expected asset to the authorized treasury address. Only the last step establishes receipt. A dashboard can help locate each stage, but the underlying chain records determine whether the withdrawal is complete.