🚧
Deprecation notice
As Goerli & Mumbai testnets have been deprecated, this guide is for historical reference.

The Polygon mainnet is an L2 commit chain to the Ethereum mainnet.

Bridging your existing Ethereum smart contract to the Polygon commit chain allows network users to move their assets based on your contract between an Ethereum network and a Polygon commit chain.

In this tutorial, you will:

Deploy an ERC-20 smart contract on the Ethereum Goerli testnet.
Deploy a compatible smart contract on the Polygon Mumbai testnet.
Map the Ethereum smart contract to the Polygon smart contract.

Prerequisites

Chainstack account to deploy an Ethereum node and a Polygon node.
Truffle Suite to create and deploy contracts.
OpenZeppelin Contracts to use the audited ERC-20 libraries to create your ERC-20 contract.

Overview

To get from zero to a deployed ERC-20 contract on the Ethereum Goerli testnet and bridge it to the Polygon Mumbai testnet, do the following:

With Chainstack, create a public chain project.
With Chainstack, join the Ethereum Goerli testnet.
In the same project, join the Polygon Mumbai testnet.
With Chainstack, access your Ethereum node and Polygon node endpoints.
With OpenZeppelin, create an ERC-20 contract.
With Truffle, compile and deploy the contract through your Ethereum node.
With Truffle, compile and deploy a Polygon contract through your Polygon node.
Submit a mapping request to bridge the deployed Ethereum contract to the deployed Polygon contract.

Step-by-step

Create the root Ethereum ERC-20 contract

On your machine, in the contract directory, initialize Truffle:

truffle init

This will generate the Truffle boilerplate structure:

.
├── contracts  
│   └── .gitkeep  
├── migrations  
│   └── .gitkeep  
├── test  
│   └── .gitkeep  
└── truffle-config.js

Go to the contracts directory. In the directory, create your ERC-20 contract: myL2token.sol.

//SPDX-License-Identifier: MIT
pragma solidity ^0.8.0;

import "@openzeppelin/contracts/token/ERC20/ERC20.sol";

contract myL2token is ERC20 {  
  constructor(uint256 initialSupply) ERC20("myL2token", "ML2T") {  
    \_mint(msg.sender, initialSupply);  
  }  
}

This is a standard OpenZeppelin ERC-20 preset contract.

Create 2_deploy_contracts.js in the migrations directory.
```
var myL2token = artifacts.require("./myL2token.sol");

module.exports = function(deployer) {
  deployer.deploy(myL2token, 100);
};
```
This will create the instructions for Truffle to deploy the contract with the supply of 100 ML2T tokens.

Compile and deploy the root Ethereum ERC-20 contract

Install HDWalletProvider.

HDWalletProvider is Truffle's separate npm package used to sign transactions.

Run:
```
npm install @truffle/hdwallet-provider
```
Edit truffle-config.js to add:
- HDWalletProvider
- Your Ethereum node access and credentials
- Your Ethereum account that you will use to deploy the contract
```
const HDWalletProvider = require("@truffle/hdwallet-provider");  
const private_key = 'PRIVATE_KEY';

module.exports = {  
 networks: {  
    goerli: {  
        provider: () => new HDWalletProvider(private_key, "YOUR_CHAINSTACK_ENDPOINT"),  
        network_id: 5  
    }  
   },

 compilers: {  
    solc: {  
    version: "0.8.1",  
    }  
  }  
};
```
where
- goerli — any network name that you will pass to the truffle migrate --network command.
- HDWalletProvider — Truffle's custom provider to sign transactions.
- PRIVATE_KEY — the private key of your Ethereum account that will deploy the contract.
- YOUR_CHAINSTACK_ENDPOINT — your Chainstack node endpoint. See also View node access and credentials and Ethereum tooling.
- network_id — the network ID of the Ethereum Goerli testnet: 5.
- solc — the Solidity compiler version that Truffle must use.
Run:
```
truffle migrate --network goerli
```
This will engage 2_deploy_contracts.js and deploy the contract to the Ethereum Goerli testnet as specified in truffle-config.js.

Verify your root Ethereum ERC-20 contract on Etherscan

Once your contract is deployed, you can view it online at Etherscan.

Before you submit a mapping request to bridge your root Ethereum ERC-20 contract to the Polygon commit chain, you must verify the contract on Etherscan.

Flatten your contract code

Since your ERC-20 contract uses imported OpenZeppelin libraries, you must put all the imports into one .sol file to make Etherscan be able to verify it.

Install Truffle Flattener.

In the contracts directory, run:
```
npx truffle-flattener myL2token.sol > flatmyL2token.sol
```
Clean up the licensing information.

The flattened contract will have the same licensing note imported from each of the files. Multiple licensing notes in one file break the Etherscan verification, so you have to leave one licensing note for the entirety of the flattened contract.

The easiest way to clean up is to search for the SPDX mentions in the file and remove all of them except for the very first one.
Verify the deployed contract on Etherscan.

At this point, you have your flattened and cleaned-up contract ready for the Etherscan verification.
Go to Etherscan.
Find your deployed contract. The address of your contract should have been printed by Truffle at the end of the deployment in the contract address field.
On the contract page on Etherscan, click Contract > Verify and Publish.
In Compiler Type, select Solidity (Single file).
In Compiler Version, select v0.8.1. This is the version this tutorial used to compile the contract.
In Open Source License Type, select MIT License (MIT).
Click Continue.
Keep the Optimization option set to No as Truffle does not use optimization by default.
Paste the entirety of your flattened .sol contract in the Enter the Solidity Contract Code below field.
Click Verify and Publish.

Etherscan will take a few seconds to compile your contract, verify, and publish it.

Create the child Polygon ERC-20 contract

Go to the contracts directory. In the directory, put the default child ERC-20 contract provided by Polygon.
Create 2_deploy_contracts.js in the migrations directory.
```
var ChildERC20 = artifacts.require("./ChildERC20.sol");

module.exports = function(deployer) {
  deployer.deploy(ChildERC20, 'myL2tokenChild', 'ML2T', 18, '0x2e5e27d50EFa501D90Ad3638ff8441a0C0C0d75e');
};
```
where
- myL2tokenChild — the name of your ERC-20 token
- ML2T — the symbol of your ERC-20 token
- 18 — the default decimals number as used by the OpenZeppelin ERC-20 preset contract
- 0x2e5e27d50EFa501D90Ad3638ff8441a0C0C0d75e — the ChildChainmanager address on the Polygon Mumbai testnet. For the ChildChainManager contract addresses, look online for the addresses provided by Polygon:
  - Mainnet addresses

Compile and deploy the child Polygon ERC-20 contract

Clean up the environment by moving myL2token.sol and flatmyL2token.sol to a backup directory so that Truffle does not pick them up for deployment.

Edit truffle-config.js to change to:
- Your Polygon node access and credentials
- Your Polygon account that you will use to deploy the contract.
- The Solidity compiler version used by the default child ERC-20 contract template provided by Polygon.
```
const HDWalletProvider = require("@truffle/hdwallet-provider");
const private_key = 'PRIVATE_KEY';

module.exports = {
 networks: {
    mumbai: {
        provider: () => new HDWalletProvider(private_key, "YOUR_CHAINSTACK_ENDPOINT"),
        network_id: 80001
    }
   },

 compilers: {
    solc: {
    version: "0.6.6",
    }
  }
};
```
where
- mumbai — any network name that you will pass to the truffle migrate --network command.
- HDWalletProvider — Truffle's custom provider to sign transactions.
- PRIVATE_KEY — the private key of your Polygon account that will deploy the contract.
- YOUR_CHAINSTACK_ENDPOINT — your Chainstack node endpoint. See also View node access and credentials and Polygon tooling.
- network_id — the network ID of the Polygon network: testnet is 80001, mainnet is 137.
- solc — the Solidity compiler version that Truffle must use. OpenZeppelin contracts have a higher version Solidity compiler requirement than the default Truffle installation, hence you must provide a specific compiler version.
Run:
```
truffle migrate --network Mumbai
```

Verify your child Polygon ERC-20 contract on the Polygon explorer

Once your contract is deployed, you can view it online at the Polygon Mumbai explorer.

Go to the Polygon Mumbai explorer.
Find your deployed contract. The address of your contract should have been printed by Truffle at the end of the deployment in the contract address field.
On the contract page on the explorer, click Contract > Verify and Publish.
In Compiler Type, select Solidity (Single file).
In Compiler Version, select v0.6.6. This is the compiler version the default child contract uses as provided by Polygon.
In Open Source License Type, select MIT License (MIT).
Click Continue.
Keep the Optimization option set to No as Truffle does not use optimization by default.
Paste the entirety of your ChildERC20.sol contract in the Enter the Solidity Contract Code below field.
Click Verify and Publish.

📘
ABI data
If on the verification attempt you get a message that the explorer cannot get the ABI data for the contract verification, do the following:

Go to the online ABI encoding service.

In the service, provide the ChildERC20.json ABI data as (ticne). Remove the first and last curly bracket {} and "abi": or the code will not parse.

Click Parse.

Put your constructor data by adding arguments with the data type:

name_: myL2tokenChild

symbol_: ML2T

decimals_: 18

childChainManager: 0x2e5e27d50EFa501D90Ad3638ff8441a0C0C0d75e

Copy the encoded data.

Paste the encoded data in the ABI constructor arguments field on the explorer.

The explorer will take a few seconds to compile your contract, verify, and publish it.

Map your Ethereum ERC-20 contract to the Polygon contract

Go to the token mapper.
Select ERC20 and Goerli Testnet - Mumbai Testnet.
Provide the address of your contract on the Ethereum Goerli testnet and on the Polygon Mumbai testnet.
Provide an email address to be notified of when the mapping is done.
Click Submit.

Bridge the mapped tokens

When your token is mapped, bridge your token from Ethereum to Polygon and back:

Conclusion

This tutorial guided you through the basics of bridging an ERC-20 contract from the Ethereum Goerli testnet to the Polygon Mumbai testnet.

The same instructions will work for the Ethereum mainnet and the Polygon mainnet.

Polygon has public L2 contract templates and a network of deployed contracts monitored by Heimdall nodes, all of which make it easy to bridge assets from the Ethereum mainnet to the Polygon commit chain.

Polygon: Bridging ERC-20 from Ethereum to Polygon

🚧
Deprecation notice

Prerequisites

Overview

Step-by-step

Create a public chain project

Join the Ethereum Goerli testnet and the Polygon Mumbai testnet

Get your Ethereum node and Polygon node access and credentials

Install OpenZeppelin Contracts

Install Truffle Suite

Create the root Ethereum ERC-20 contract

Compile and deploy the root Ethereum ERC-20 contract

Verify your root Ethereum ERC-20 contract on Etherscan

Create the child Polygon ERC-20 contract

Compile and deploy the child Polygon ERC-20 contract

Verify your child Polygon ERC-20 contract on the Polygon explorer

📘
ABI data

Map your Ethereum ERC-20 contract to the Polygon contract

Bridge the mapped tokens

Conclusion

About the author

Ake

🛠️ Developer Experience Director @ Chainstack

💸 Talk to me all things Web3 infrastructure and I'll save you the costs

🚧Deprecation notice

Prerequisites

Overview

Step-by-step

Create a public chain project

Join the Ethereum Goerli testnet and the Polygon Mumbai testnet

Get your Ethereum node and Polygon node access and credentials

Install OpenZeppelin Contracts

Install Truffle Suite

Create the root Ethereum ERC-20 contract

Compile and deploy the root Ethereum ERC-20 contract

Verify your root Ethereum ERC-20 contract on Etherscan

Create the child Polygon ERC-20 contract

Compile and deploy the child Polygon ERC-20 contract

Verify your child Polygon ERC-20 contract on the Polygon explorer

📘ABI data

Map your Ethereum ERC-20 contract to the Polygon contract

Bridge the mapped tokens

Conclusion

About the author

Ake

🛠️ Developer Experience Director @ Chainstack

💸 Talk to me all things Web3 infrastructure and I'll save you the costs

🚧
Deprecation notice

📘
ABI data