Why Polygon PoS Withdrawals Burn Tokens First

Why Polygon PoS Withdrawals Burn Tokens First

A Polygon PoS withdrawal burns the token on Polygon first, then uses proof of that burn to release the matching token on Ethereum. A centralised exchange can move balances inside its own records; a bridge must prove that the Polygon balance has been removed before releasing another one.

That burn is the start of a withdrawal, not a sign that your tokens vanished. If you are comparing routes before moving funds, which Polygon Bridge route fits your token covers that choice; this article explains why the Polygon PoS route burns first.

The burn prevents two spendable balances

A sidechain is a separate blockchain connected to another network. Polygon PoS keeps its own token balances, so a token you hold there is not the same on-chain balance as the matching asset on Ethereum.

For many ERC-20 tokens—a common standard for tokens on Ethereum—the bridge works like a receipt system. A deposit locks the original tokens on Ethereum and creates matching tokens on Polygon. A withdrawal reverses that arrangement: it destroys the Polygon version, then releases the locked Ethereum tokens.

Without the burn, both versions could remain spendable after the bridge released the Ethereum tokens. Burning first gives the bridge a record that the Polygon balance has been removed, so it cannot be used alongside the released balance.

A withdrawal needs a burn, a checkpoint, and an exit

A Polygon PoS withdrawal has three main parts: burn the tokens on Polygon, wait for the relevant block to be checkpointed, then complete the exit on Ethereum. A checkpoint is a record of Polygon blocks submitted to Ethereum by the network’s validators.

The burn transaction is the on-chain instruction that destroys your Polygon tokens. Validators later include its block in a checkpoint. Once that record is available on Ethereum, a cryptographic proof—a piece of data the Ethereum contract can verify—shows that the burn really happened.

The Ethereum bridge contract checks the proof and releases the corresponding tokens from its locked balance. The release needs a separate Ethereum transaction, so your wallet must be able to pay Ethereum’s transaction fee when you complete the exit.

Time and fees come from two different networks

The wait depends on when a checkpoint covers the burn, so it can vary with network activity. The Polygon transaction and the Ethereum exit also have separate fees: the first uses Polygon’s network, while the second uses Ethereum’s.

For example, withdrawing 50 tokens does not mean sending a second batch of 50 across the bridge. The first transaction burns the Polygon balance; the later Ethereum transaction releases the matching amount already held there. Fees pay for those network transactions, not for duplicating the tokens.

Keep the burn record until Ethereum receives the tokens

A common mistake is to see the Polygon balance disappear and assume the withdrawal failed. The fix is to keep the burn transaction hash—the transaction’s public identifier—and use it to track or resume the exit after the checkpoint is available.

Before starting, check that you are withdrawing from Polygon PoS to Ethereum and that your wallet can cover both networks’ fees. A burn cannot be reversed, so verify the token and amount before signing. If the balance has burned but Ethereum has not received the tokens, the exit still needs to be completed.

Why does the bridge burn before releasing tokens?

It removes the Polygon balance before the bridge releases the matching Ethereum balance. This keeps the two network records from representing two spendable copies of the same bridged value. The proof of the burn lets the Ethereum contract verify that removal before it releases the locked tokens.

Does a burn mean my tokens are lost?

No. The burn removes the Polygon version as part of the withdrawal process. The matching tokens remain held on Ethereum until the exit is completed. Keep the burn transaction hash so you can track the transfer and provide its record when needed.

Why are there two transaction fees?

The burn happens on Polygon PoS, and completing the exit happens on Ethereum. Each network processes its own transaction and charges its own fee. Ethereum’s fee is needed for the final release, even though the tokens were burned on Polygon.

What should I do if the Polygon balance is gone?

Check the burn transaction and wait until its block is included in a checkpoint. Then complete the Ethereum exit using the burn record. The tokens do not appear on Ethereum just because the Polygon balance has been burned; the exit transaction must release them.

Decision rule: treat a Polygon PoS withdrawal as complete only when the Ethereum exit has released the tokens.

Comments

Post a Comment

Popular posts from this blog

Syncswap Aqua Pool Fees: Why Imbalance Matters

Image
Syncswap Aqua Pool fees rise as the pool becomes more imbalanced, so volatility affects the fee through inventory pressure rather than through a direct volatility meter. The detail that makes the design click is that a fast market move changes the token balance inside the pool first. Aqua Pool reacts to that imbalance, widening its fee response while its automated liquidity curve adjusts around the moving price. What changes when the market moves Aqua Pool is Syncswap’s two-token market-making model for assets whose prices can move substantially against each other. It is inspired by Curve v2’s twocrypto design: the pool combines constant-product behavior with a more concentrated curve near the current market price. When trading is balanced, the pool can keep more liquidity close to its internal price scale. A one-sided sequence of swaps changes the reserves, however. If traders keep buying one token, that token becomes scarcer in the pool and the reserve ratio moves away from its bala...
Read more

4 Checks for Comparing Multi-Pool Token Activity

Image
Compare each pool on its own first, then combine activity only after you normalize the units and time window. A token with pools against WBNB and a stablecoin has separate prices, reserves, and trades in each pool; one chart can hide those differences. If you need the basics of reading a token chart, see how a first PooCoin chart works . This article focuses on the pair-level data an integration should compare. Pair identity and quote depth determine what the activity means Treat a pool as a specific contract, not as a property of the token. On BNB Smart Chain, the pair address identifies the pool; its two token addresses identify the assets, and the pair’s Swap events record trades. Two pools containing the same token can have different counterparties, liquidity, and users. For a simple example, suppose a token has a pool with 20,000 tokens and 10 WBNB, with WBNB valued at $50. Its reserve-ratio price is $0.025 per token. A second pool has 8,000 tokens and 240 USDT, implying $0.03. I...
Read more

Spendable Monero outputs before a bridge deposit

Image
Send XMR to a bridge only when the specific output you plan to spend is unlocked, and budget roughly 20 minutes after it confirms for Monero’s normal 10-block spendable-age rule. A bridge can detect a deposit earlier, but detection is not the same as being able to process it: the bridge must be able to construct and submit a valid Monero spend. What makes an output spendable? A confirmed incoming transaction creates one or more outputs credited to your wallet, each controlled by a one-time stealth address. Monero’s consensus rules prevent spending a normal output until it has aged 10 blocks; at roughly two minutes per block, that is about 20 minutes after inclusion, with block timing and confirmation variation affecting the wait. The bridge’s Monero wallet has the same constraint as yours. It scans for a payment, identifies the matching output using its wallet keys, then selects that output as an input in a new transaction. That transaction needs a valid key image and ring signature, ...
Read more