The POS Bridge is no longer suitable for new mappings, as Polygon has discontinued support for token mapping on the POS bridge. Polygon has introduced a new process, you will no longer have to wait for their team to map your tokens. Polygon is now using the fx-portal bridge for greater efficiency and decentralization. You can find more details at https://polygon.olvy.co/introducing-a-new-process-for-mapping-tokens-on-polygon.
If you have a default ERC20, ERC721, or ERC1155 token, you can submit a mapping request here: https://mapper.polygon.technology/map
Guide to map tokens: https://wiki.polygon.technology/docs/develop/ethereum-polygon/submit-mapping-request/
However, if you have a custom ERC20 token, you will need to create a custom FxTunnel implementation for the mapping process
To implement your custom FxTunnel, you would need to follow the documentation- https://wiki.polygon.technology/docs/develop/l1-l2-communication/fx-portal#do-i-need-a-custom-fxtunnel-implementation-
Here is the example repo for reference: https://github.com/fx-portal/contracts/tree/main/contracts/examples
Fx-Portal has two main parts, one for the root chain (Goerli in this case), and one for the child chain (Mumbai). The Goerli contract is responsible for mapping tokens from the root chain to the child chain and sending deposits to the child chain. The Mumbai contract is responsible for handling incoming messages from the Goerli contract, minting child tokens, and processing child-to-root withdrawals.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article