Home/Generate/ERC-20 Token Creator/
Create Avalanche Token

Create Avalanche Token




Connect to the chosen blockchain.
Check Docs
Choose a great name for your token.
Check Docs
Choose a great symbol for your token.
Check Docs
Smart contract name is being derived from your token name and visible after verification. If you are not sure, we recommend keeping the default value.
Check Docs
Choose how many tokens you want to create.

Tokens

Check Docs
If the Mintable feature is enabled, the owner will be able to mint new tokens until the total supply reaches the maximum supply.
Check Docs
Choose how many decimal places your tokens can be divided to. If you are not sure, we recommend leaving it at 18.
Check Docs
Instead of your wallet, enter a different address to receive the initial supply of tokens.
Check Docs
Instead of your wallet, enter a different address that will have ownership of the token after it is created.
* - Required fields

How to create an Avalanche token?

Avalanche is technically three chains - C-Chain (the EVM-compatible smart contract chain), X-Chain (asset transfers), and P-Chain (validators and Avalanche L1s/subnets). For ERC-20 tokens you only care about the C-Chain (chain ID 43114), which combines full EVM compatibility with sub-second finality through Avalanche's unique consensus protocol. Gas costs typically stay low even under heavy load, and tokens deploy as standard ERC-20s with no special tooling.

Deployment in 5 steps

  1. Connect your wallet - MetaMask, Core Wallet (Avalanche's official option), Trust Wallet, or any wallet supporting WalletConnect
  2. Switch to Avalanche C-Chain - chain ID 43114, native gas token AVAX
  3. Configure the basics - name, symbol, initial supply, decimals (18 standard)
  4. Pick features - mintable, taxes, anti-bot cooldowns, or transfer limits
  5. Deploy - confirm and your Avalanche token goes live in about 2 seconds

Test free on Avalanche Fuji (chain ID 43113) using AVAX from a public faucet before deploying to mainnet.

C-Chain vs custom Avalanche L1

Avalanche lets you launch your own dedicated chain (formerly "subnets," now Avalanche L1s), which makes sense for gaming projects with custom rules or institutional deployments with specific requirements. For 99% of token launches, the C-Chain is the right answer because that's where existing AVAX liquidity and users live. Custom L1 tokens are isolated from the main DeFi ecosystem unless explicitly bridged.

Listing on LFJ and beyond

LFJ (formerly Trader Joe) is Avalanche's flagship DEX. Use our Avalanche add liquidity tool to create your initial pair, distribute to early holders via the Avalanche multisender, then submit to CoinGecko and CoinMarketCap.

Want to Generate Specific Token?

Choose the type of token from table below:

Avalanche C-Chain gas costs are usually a few cents to under a dollar in AVAX, plus a 20lab service fee shown on the summary before you confirm. Avalanche Fuji testnet (chain ID 43113) is free using test AVAX from a public faucet.

Avalanche actually consists of three chains. The C-Chain (chain ID 43114) is the EVM-compatible smart contract chain - this is where ERC-20 tokens, DeFi, and dApps live, and it's what 20lab deploys to. The X-Chain handles asset creation and transfers using a UTXO model. The P-Chain coordinates validators and Avalanche L1s (subnets). For 99% of token projects, C-Chain is what you want.

Custom L1s (formerly called subnets) make sense when you need a dedicated chain with custom rules - typically gaming projects or institutional deployments with specific compliance requirements. For 99% of token launches the C-Chain is the right answer because that's where existing AVAX liquidity and users are. Subnet tokens are isolated from the main DeFi ecosystem unless you bridge.

LFJ (formerly Trader Joe) is Avalanche's flagship DEX. After deploying through 20lab, use our Avalanche add liquidity tool to create your initial pair, or do it manually through the LFJ interface. Once a pool exists, your token automatically appears in LFJ's swap UI - no application needed.

Avalanche uses a unique consensus protocol (Avalanche consensus) that achieves probabilistic finality through repeated random sampling of validators. This is fundamentally different from the longest-chain rule used by Ethereum or BNB. The practical effect is sub-second finality - once a transaction confirms, it's effectively final, with no "wait for X confirmations" period that exists on most other chains.