A Polygon PoS withdrawal has two on-chain stages: burn the child-chain representation, then prove that burn against a checkpoint before the Ethereum contract releases the root asset. An integrator should track those stages separately, because a confirmed burn is not yet an Ethereum payment. Treat the exit as complete only after the release transaction succeeds.
What does a PoS withdrawal prove?
It proves that a specific child-chain receipt contains a valid withdrawal event and that the block containing it belongs to a checkpoint accepted on Ethereum. The burn starts the process; it does not itself transfer tokens back to Ethereum. For the treasury-level route and lifecycle, read how Polygon Bridge serves treasury flows; this article focuses on implementing the withdrawal state machine.
For an ERC-20, the child token’s withdrawal method burns the requested amount and emits a log. A Polygon PoS checkpoint later commits a range of child-chain block headers to Ethereum. The exit payload ties the burn receipt to that commitment: it carries the checkpoint header number, child block number and time, transaction and receipt roots, the receipt, its Merkle Patricia proof, a branch mask, and the log index.
On Ethereum, RootChainManager’s exit() validates the receipt proof against the receipt root, then checks the block’s membership in the checkpoint. It resolves the emitting child token to its mapped root token and invokes that token’s predicate to release the asset. The processed-exit key includes the block number, normalized branch mask, and receipt log index, preventing a valid exit from being replayed.
How should an integrator track the exit?
Model at least three states: burn confirmed, checkpointed and provable, and exited on Ethereum. Persist the child burn transaction hash and receipt log index. Once a checkpoint covers the burn’s block, obtain or construct the exit payload, submit it on Ethereum, and mark the withdrawal complete only when that transaction is successful.
For example, a treasury service paying a vendor from Polygon may record a withdrawal request when its operator burns the ERC-20. Its accounting system should reserve the amount as in transit until the Ethereum exit succeeds; otherwise, a dashboard can report funds as delivered while they remain locked in the bridge process. Budget for an Ethereum transaction from the account that submits the exit.
Do not encode a fixed checkpoint wait as a protocol guarantee. The wait depends on when validators submit a checkpoint covering the burn block, and proof availability is a separate operational dependency. Poll checkpoint coverage or use a reliable proof source, but validate the returned payload against the burn receipt and expected token before submitting it.
Common failures have distinct remedies: an uncovered block means wait; an invalid receipt proof usually points to stale or mismatched payload data; a wrong log index can select a different event; and an already-processed exit means check Ethereum state before retrying. The Polygon PoS Portal contracts define the proof checks and replay guard; Ethereum’s Yellow Paper describes the receipt-trie basis for inclusion proofs. Keep retries keyed to the original burn and inspect the destination transaction outcome.
Can a confirmed burn be reversed?
A confirmed burn has no ordinary cancel operation that restores the child tokens. The withdrawal proceeds through checkpoint inclusion and the Ethereum exit transaction. If the exit has not happened, treat the amount as in transit and investigate proof availability or transaction status; do not create a replacement withdrawal unless your accounting and reconciliation logic can handle both requests.
When is the withdrawal complete?
It is complete when the Ethereum exit transaction succeeds and the intended root-token recipient has received the released amount. Check the transaction receipt and relevant token transfer, not merely checkpoint inclusion or a submitted exit transaction. A reverted Ethereum transaction leaves the release unfinished, even though the original Polygon burn remains recorded.