Start typing to search this publication.
crypto.news logo crypto.news
Open menu
crypto.news logo

Subscribe to crypto.news

Get new posts delivered straight to your inbox.

How to bridge NFTs with Polygon bridge and verify arrival

crypto.news avatar crypto.news
2 min read

With an NFT in your Ethereum wallet, Polygon bridge can move it to Polygon PoS if the collection is mapped: approve the NFT predicate, deposit the token, and wait for state sync. The NFT keeps its token ID, but appears under a different contract address on Polygon.

How do you move a mapped NFT with Polygon bridge?

Start by confirming the collection’s Ethereum contract has a mapped child contract on Polygon PoS. You need ETH in your wallet for the Ethereum transactions and the Polygon PoS network added to MetaMask so you can see the result.

For a mapped collection, this bridge from Ethereum to Polygon locks the original NFT while its counterpart appears on Polygon. Use the Polygon bridge to bridge assets to Polygon once you have confirmed the collection’s mapping.

  1. Confirm the mapping. Compare your NFT’s Ethereum contract address with the collection’s published Polygon child contract address. The addresses differ, so the collection name alone is not enough to identify the right token. Only mapped collections can use this deposit route. If yours is unmapped, ask the project whether it provides its own bridge.

  2. Approve the token you own. For one ERC-721, approve the ERC721Predicate for that token ID on the Ethereum NFT contract. The contract call is approve(predicate address, token ID). This gives the predicate permission to take that NFT when you deposit it. I would choose this single-token approval for a one-NFT transfer. setApprovalForAll instead authorizes the predicate for the entire collection, including tokens you may acquire later. If you use collection-wide approval, revoke it on Ethereum after depositing; that revocation also costs gas. ERC-1155 uses ERC1155Predicate and collection-wide operator approval because the standard has no equivalent single-token approval.

  3. Submit the deposit. Confirm the recipient address and token ID before signing. The deposit goes through RootChainManager, which directs the NFT to its predicate. ERC721Predicate or ERC1155Predicate locks the Ethereum token according to its standard. You pay Ethereum gas for approval and deposit; the amount depends on network gas prices when each transaction executes.

  4. Wait for state sync. An Ethereum deposit receipt confirms the source transaction, while state sync brings the deposit message to Polygon PoS. Arrival depends on Ethereum confirmation and that sync. If the NFT has left your Ethereum wallet but has not appeared on Polygon, inspect the deposit transaction first and allow the sync to complete before trying another deposit.

  5. Verify the result. Search your recipient address on Polygonscan and find the token ID under ERC-721 transfers. Match its Polygon contract address to the mapped child contract. That transfer is the practical confirmation that the NFT reached your Polygon address; MetaMask can then show it under the Polygon network.

Why doesn't my bridged NFT show on a marketplace?

A marketplace may take time to index the Polygon child contract or its metadata. First confirm the token ID and your address on Polygonscan. If that transfer is present, check that the marketplace is viewing Polygon PoS and the child contract rather than the Ethereum original.

How do I bring an NFT back to Ethereum?

Returning a mapped NFT starts by withdrawing its Polygon token, which burns that counterpart. After the withdrawal reaches an Ethereum checkpoint, complete the exit on Ethereum to release the locked original. Plan for Polygon gas to start the withdrawal and ETH gas to finish the exit.

Subscribe to crypto.news