Submit Mapping Request

Mapping is necessary in order to transfer your assets to and fro the Ethereum and Polygon. We offer two bridges to do the same. More details on the bridge can be understood from here.

The mapping request has to be submitted on https://mapper.matic.today/. You can then click on the "Map New Token" button on the top right corner to create a new mapping request.

Steps

  • The type of bridge has to be selected from the "Choose map type" dropdown.
  • The type of your token can be selected by switching among the three tabs marked as "ERC20", "ERC721" and "ERC1155". For mapping any other token standard, you can reach out to the Polygon team on Discord or create a ticket here and keep "Token Mapping" in the ticket title.
  • "Choose network" will let you select the network on which you need the mapping to be done. For mainnet mappings you can choose Ethereum - Polygon Mainnet and for testnet mappings you can choose Goerli Testnet - Mumbai.
  • Enter your Ethereum/Goerli token address in the "Ethereum token address" field. Ensure that your token contract code is verified on the Ethereum/Goerli blockchain explorers.
  • In case you need a standard ERC20/ERC721/ERC1155 child token, you may leave the "Polygon token address" field empty. But, if you need a custom child token ( standard ERC functions + custom functions ), you can follow this guide to create a custom child token. Once you deploy your custom child token, you can mention the contract address in the "Polygon token address" field. Please ensure that you verify your child token contract code too on Polygon/Mumbai explorer.
  • If your root token is verified, the name, symbol and decimals fields will be automatically filled for you and these fields cannot be edited.
  • You may choose either "Polygon Mintable" or a "Non Polygon Mintable" token from the drop down. More details on the Polygon Mintable tokens can be found here.
  • It is mandatory to mention your email for communication.

In case of a custom child mapping, there is a checklist that you need to finish before you submit the mapping request. Tokens that already exist on Ethereum and have to be moved on to the Polygon chain can be called as "Non Polygon-Mintable" tokens and the tokens which are going to be minted on Polygon first and then moved to Ethereum can be called as "Polygon Mintable" tokens. Lets look at the check list for both these types

Mapping checklist

Non Polygon-Mintable

  1. The deposit and withdraw functions are present on the child token contract. (Reference Template contract - ERC20, ERC721, ERC1155)
  2. Only the ChildChainManagerProxy address has the right to call the deposit function. (ChildChainManagerProxy - on Mumbai , on Polygon Mainnet )
  3. Mint function is an internal function ( This gets called by deposit function internally )

Polygon Mintable ( guide - https://docs.polygon.technology/docs/develop/ethereum-polygon/pos/mintable-assets )

  1. The deposit and withdraw function is present in the child token contract. (Reference Template contract - ERC20, ERC721, ERC1155)
  2. Only the ChildChainManagerProxy address has the right to call the deposit function. (ChildChainManagerProxy - on Mumbai , on Polygon Mainnet )
  3. The root chain contract is a standard ERC20/ERC721/ERC1155
  4. The mint function on the root contract can only be called by the corresponding token, PredicateProxyAddress (PredicateProxy addresses for each token type can be found here.
Last updated on