Skip to main content

ckERC20

Advanced
Ethereum

What is ckERC20?​

Chain-key ERC-20 (ckERC20) tokens are ICRC-2-compliant tokens that are backed 1:1 by the corresponding ERC-20-compliant token on Ethereum. For example, there are chain-key tokens for USDC and LINK.

The full list of chain-key tokens can be viewed on the Internet Computer dashboard under 'Chain Fusion'.

Just like other chain-key tokens, such as ckBTC and ckETH, the ckERC20 tokens do not rely on any centralized bridge to facilitate the conversion between the ckERC20 token and the ERC-20 token, which makes the conversion substantially more secure compared to other traditional 'wrapped' tokens.

ckERC20 tokens offer the same advantages over their counterparts on Ethereum, including faster and cheaper transactions.

A ckERC20 token can be created for any ERC-20 token. The process of adding a ckERC20 token involves creating an NNS proposal.

Note that the same requirements as for any other type of chain-key token apply.

How it works​

The ckERC20 functionality is provided by two canisters, the ckETH minter and the ledger suite orchestrator (LSO), and a helper smart contract on Ethereum:

Canister / contractEthereum mainnetSepolia testnet
ckETH Mintersv3dd-oaaaa-aaaar-qacoa-cai (Canister dashboard)jzenf-aiaaa-aaaar-qaa7q-cai (Canister dashboard)
LSOvxkom-oyaaa-aaaar-qafda-cai2s5qh-7aaaa-aaaar-qadya-cai
Helper0x6abDA0438307733FC299e9C229FD3cc074bD8cC00x674Cdbe64Df412DA9bAb1596e00c1520979B5A23

The ckETH minter is responsible for handling ERC-20 deposits and withdrawal requests. The ckETH minter handles these tasks because ERC-20 transfers require an Ethereum transaction with a fee in ETH.

The ledger suite orchestrator is responsible for a set of ICRC ledger suites, one ledger suite per ckERC20 token. Each ledger suite consists of a ledger, an index, and possibly one or more archive canisters. The ledger suite orchestrator makes it possible to handle all ckERC20 tokens in a scalable manner. Specifically, it can perform the following actions:

  • Spawn a new ICRC ledger suite when adding a new ckERC20 token via an NNS proposal.

  • Upgrade all managed ledger suites via an NNS proposal.

  • Top up the canisters of all managed ledger suites with cycles.

Converting ERC-20 tokens to ckERC20 tokens​

In order to convert ERC-20 tokens to the corresponding ckERC20 tokens, the following steps are carried out:

  1. The user submits an Ethereum transaction calling the approve function of the ERC-20 smart contract to allow the helper smart contract to withdraw some of the user's funds.

  2. The user calls the deposit function of the helper smart contract, specifying the ERC-20 contract, how many ERC-20 tokens should be withdrawn from the user's account, and the principal ID that should be credited for the minted ckERC20 tokens. The helper smart contract transfers the specified number of ERC-20 tokens to itself and, if successful, emits an event to be consumed by the ckETH minter.

  3. The ckETH minter periodically fetches the logs from the helper smart contract, minting ckERC20 tokens for every newly discovered event.

Converting ckERC20 tokens to ERC-20 tokens​

A user can convert ckERC20 tokens to ERC-20 tokens by following these steps:

  1. The user calls the icrc2_approve function on the ckETH ledger to approve the ckETH minter to burn some of the user's ckETH tokens as payment for the transaction fees.

  2. The user calls the icrc2_approve function on the ledger of the given ckERC20 token to approve the minter to burn some of the user's ckERC20 tokens.

  3. The user calls the withdraw_erc20 function on the ckETH minter, specifying the canister ID of the ledger for the given ckERC20 token, the amount to be withdrawn, and the Ethereum destination address. The ckETH minter then issues transactions to burn the fee in ckETH and the specified amount of the ckERC20 token. If both operations succeed, it sends an Ethereum transaction that transfers the specified amount from the helper smart contract to the destination address that the user provided.

More details on both flows are provided on the ckERC20 GitHub page, whereas a detailed description of the ledger suite orchestrator can be found in its GitHub repository.

The ledger and index canisters in any ckERC20 ledger suite are regular ICRC-1 compliant canisters. A guide on how to interact with these canisters can be found in the using the ICRC-1 ledger section.

Deploying ckERC20 tokens​

Tokens deployed on other networks that use the ERC-20 standard can be launched on ICP as ckERC20 tokens. To propose a new ckERC20 be launched on the mainnet, there are several technical and non-technical steps that should be completed. Learn more in creating a new ckERC20 token

ckERC20 use-cases​

ckERC20 tokens can be used in the same way as other chain-key tokens. Use cases include:

  • Token swaps

  • Decentralized exchanges

  • Point of sale applications and services

  • Crowdfunding applications

  • eCommerce platforms

  • Faster and cheaper ERC-20 transactions

ckERC20 production application examples​

Further reading​