Bridge ERC-20 tokens with the Thanos SDK
This tutorial describes how the Thanos SDK can bridge ERC-20 tokens from L1 to L2. You can look at our example: Github
1. Prerequisite
1.1. Dependencies
1.2. Install packages
To use Thanos SDK, first, you must install the package from NPM.
npm install @tokamak-network/thanos-sdk@latest2. Set Environments
// .env example
PRIVATE_KEY=change_me
L1_RPC_URL=change_me
L2_RPC_URL=change_me
L1_TOKEN=change_me
L2_TOKEN=change_me3. Create providers and wallets
const privateKey = process.env.PRIVATE_KEY;
const l1RpcProvider = new ethers.providers.JsonRpcProvider(process.env.L1_RPC_URL);
const l2RpcProvider = new ethers.providers.JsonRpcProvider(process.env.L2_RPC_URL)
const l1Wallet = new ethers.Wallet(privateKey, l1RpcProvider);
const l2Wallet = new ethers.Wallet(privateKey, l2RpcProvider);4. Use Thanos SDK to interact between two networks
CrossChainMessenger in Thanos SDK is designed to facilitate cross-chain communication between Ethereum and the L2 built by Thanos Stack. It allows sending messages and executes transactions between L1 and L2, simplifying moving assets between them.
The CrossChainMessenger constructor is
To deposit ERC-20 tokens, we can initialize the CrossChainMessenger instance:
We already defined the known network on the CrossChainMessenger class. But if your network is custom, you can initialize the CrossChainMessenger instance with the custom opts.contracts
5. Set the L1 and L2 ERC-20 addresses
The l1token must be deployed on the L1 network. And the l2Token must be deployed on the L2 network.
6. Setup the token contracts
7. Deposit tokens
You can use the L1 standard bridge contract to bridge the ERC-20 tokens from L1 to L2. You will receive the same amount in the L2 after successfully depositing it.
7.1. Approve the StandardBridge use of your tokens
7.2. Deposit tokens
Predefine your deposit amount.
Execute your deposit transaction by using the bridgeERC20 function.
7.3. Wait for the deposit to be relayed
We can wait for the deposit transaction until it’s relayed on the L2 chain by using the waitForMessageStatus function.
7.4. Verify your balances
8. Withdraw tokens
To withdraw the tokens from L2 to L1, you can use the L2 standard bridge contract.
Predefine your withdrawal amount.
8.1. Approve if your token is USDC
Because the USDC isn’t supported natively on the L2 network, so we follow the Circle standard to bring USDC to our L2 network.
Because of that, the USDC bridged token on the L2 network isn’t implemented by IOptimismMintableERC20 interfaces. So, you must approve the USDC bridged to our L2 standard bridge contract before executing the withdrawal transaction.
8.2. Initialize your withdrawal transaction
To withdraw your tokens on L2, you can use the withdrawaERC20 function.
8.3. Wait for your withdrawal transaction until it is ready to prove
You must prove the withdrawal transaction on L1. So, you need to wait until the withdrawal is ready to prove.
8.4. Prove the withdrawal transaction on L1
When your withdrawal transaction is ready to be proven, you must send the proven transaction on L1 to prove that the transaction happened on L2.
8.5. Wait for your withdrawal transaction until it is ready to finalize
The final step is to finalize your withdrawal transaction on L1. This can only happen after the fault-proof period has elapsed. On Thanos Sepolia, the period is 24 mins.
8.6. Finalize your withdrawal transaction
Once the withdrawal is ready to be relayed, you can finally complete the withdrawal process.
8.7. Wait until your withdrawal is relayed
8.8. Verify your balances
Last updated
