Deploy a Remote Contract

To ensure the wrapped token is bridged into the destination chain (in this case, C-Chain) you'll need to deploy a remote contract that implements the IERC20Bridge interface, as well as inheriting the properties of TeleporterTokenRemote. In order for the bridged tokens to have all the normal functionality of a locally deployed ERC20 token, this remote contract must also inherit the properties of a standard ERC20 contract.

Get Test ECH

Before deploying the remote contract, ensure you have some test DIS, head to the Avalanche Faucet and claim some DIS tokens on the Dispatch of the Fuji testnet.

Deploy the Remote Contract

Now we'll deploy the ERC20TokenRemote contract to the Echo chain. Use our toolbox:

Make sure you have:

1. Deployed your ERC-20 token (from Deploy ERC-20 Token)
2. Deployed your ERC20Home contract (from Deploy Home)
3. Have enough test ECH for gas fees

Deploy ERC20 Token Remote Contract

Deploy the ERC20TokenRemote contract for your ERC20 token.

This deploys an `ERC20TokenRemote` contract to the current network (). This contract acts as the bridge endpoint for your ERC20 token from the source chain.

Teleporter Registry Address

Please deploy the Teleporter Registry contract first.

Source Chain (where token home is deployed)

Select a chain ID

Please select a source chain

Token Name

Token Symbol

Token Decimals

Teleporter Manager Address

Min Teleporter Version

Deploy ERC20 Token Remote

Explore moreAvalanche Builder Tooling

Save the Remote Contract Address

After deployment, you'll need to save the contract address for future steps. You can find it in the deployment confirmation in the toolbox.

Note

Keep this address handy as you'll need it for the next steps in the bridging process.