Skip to main content

Deploying your Standard ERC-20 token to Lisk

In this tutorial, you'll learn how to bridge a standard ERC-20 token from Ethereum to Lisk using the Standard Bridge system. This tutorial is meant for developers who already have an existing ERC-20 token on Ethereum and want to create a bridged representation of that token on Lisk.

This tutorial explains how to use the OptimismMintableERC20Factory to deploy a standardized ERC-20 token on Lisk or Lisk Sepolia network. Tokens created by this factory contract are compatible with the Standard Bridge system and include basic logic for deposits, transfers, and withdrawals. If you want to include specialized logic within your L2 token, see the tutorial on Bridging Your Custom ERC-20 Token to Lisk instead.

Dependencies​

Prerequisites​

note

You can deploy your Standard ERC-20 token on Lisk Mainnet by adopting the same process. For deploying to mainnet, ensure that your wallet has enough ETH.

The subsequent text contains commands for both Lisk and Lisk Sepolia for your ease. For more information, see the available Lisk networks and how to connect a wallet with them.

Get ETH on Sepolia and Lisk Sepolia​

This tutorial explains how to create a bridged ERC-20 token on Lisk Sepolia. You will need to get some ETH on both of these testnets.

info

You can use ETH Sepolia Faucet to get ETH on Sepolia. You can use the Superchain Faucet to get ETH on Lisk Sepolia.

Get an L1 ERC-20 Token Address​

You will need an L1 ERC-20 token for this tutorial. If you already have an L1 ERC-20 token deployed on Ethereum Mainnet or Sepolia, you can skip this step. For Sepolia, you can use the testing token located at 0x5589BB8228C07c4e15558875fAf2B859f678d129 that includes a faucet() function that can be used to mint tokens.

Create an L2 ERC-20 token​

Once you have an L1 ERC-20 token, you can use the OptimismMintableERC20Factory to create a corresponding L2 ERC-20 token on Lisk or Lisk Sepolia network. All tokens created by the factory implement the IOptimismMintableERC20 interface and are compatible with the Standard Bridge system. To create an L2 ERC-20 token, do the following:

1. Add a private key to your environment​

You'll need a private key in order to sign transactions. Set your private key as an environment variable with the export command. Make sure this private key corresponds to an address that has ETH on Lisk or Lisk Sepolia network.

export TUTORIAL_PRIVATE_KEY=0x...

2. Add the Lisk RPC URL to your environment​

You'll need an RPC URL in order to connect to Lisk or Lisk Sepolia network. Set your RPC URL as an environment variable with the export command.

export TUTORIAL_RPC_URL=https://rpc.sepolia-api.lisk.com

3. Add your L1 ERC-20 token address to your environment​

You'll need to know the address of your L1 ERC-20 token in order to create a bridged representation of it on Lisk or Lisk Sepolia network. Set your L1 ERC-20 token address as an environment variable with the export command.

# Replace this with your L1 ERC-20 token if not using the testing token!
export TUTORIAL_L1_ERC20_ADDRESS=0x5589BB8228C07c4e15558875fAf2B859f678d129

4. Deploy your L2 ERC-20 token​

You can now deploy your L2 ERC-20 token using the OptimismMintableERC20Factory. Use the cast command to trigger the deployment function on the factory contract. This example command creates a token with the name "My Standard Demo Token" and the symbol "L2TKN". The resulting L2 ERC-20 token address is printed to the console.

cast send 0x4200000000000000000000000000000000000012 "createOptimismMintableERC20(address,string,string)" $TUTORIAL_L1_ERC20_ADDRESS "My Standard Demo Token" "L2TKN" --private-key $TUTORIAL_PRIVATE_KEY --rpc-url $TUTORIAL_RPC_URL --json | jq -r '.logs[0].topics[2]' | cast parse-bytes32-address

If all goes well, it will respond with the address of the newly deployed contract:

0x891C582b83F69B7c2d3107cd73A3e491CB33962F
Using factories is not recommended for production

Factories make it easy to deploy contracts out of the box. The downside of this is, that you do not have control over the source code of the contract that is going to be deployed, as this is performed by the factory.

Furthermore, it is not so straightforward to verify those contracts on Blockscout, as the source code of the contract is required for the verification.