ERC-20 Token Generator

The contract you deploy is the same on every chain; what differs is the cost to deploy it, the cost for holders to trade it, and where liquidity already exists. This is the decision worth spending five minutes on, because a token cannot be moved to another network later without deploying a second contract and migrating holders.

Low-cost networks

Base, BNB Smart Chain, and Polygon deploy for a few cents and keep transfers cheap enough that ordinary holders are not priced out. Base has Coinbase distribution behind it, BSC has the deepest retail trading culture, and Polygon has broad tooling support. For most new tokens one of these three is the right answer.

Layer 2s

Arbitrum and Optimism inherit Ethereum security with much lower fees and have mature DeFi ecosystems. They cost more than Base or BSC and less than mainnet, and suit projects that want to integrate with established Ethereum-native protocols.

Ethereum mainnet

The most credible venue and the most expensive by a wide margin — deployment and every subsequent transfer are priced in real money rather than fractions of a cent. Choose it when institutional perception matters more than transaction cost, not because it is the default name you know.

1. 01

   Connect an EVM wallet

   Connect MetaMask, Rabby, Coinbase Wallet, or any injected wallet, and switch it to the network you want to deploy on. If you are on the wrong chain the page offers a one-click switch.

2. 02

   Choose the network

   Gas cost varies enormously between networks for the same deployment. Base, BNB Smart Chain, and Polygon cost a small fraction of Ethereum mainnet — pick mainnet only if you specifically need it.

3. 03

   Set the token details

   Enter name, symbol, decimals (18 is the ERC-20 convention), and initial supply, which is minted to your wallet on deployment.

4. 04

   Pick your optional features

   Decide whether the contract should be mintable, pausable, or support a blacklist. These are compiled into the contract and cannot be added afterwards.

5. 05

   Deploy and verify

   Approve the deployment transaction. Test on Sepolia or Base Sepolia first at no platform fee, then deploy to mainnet and verify the source on the block explorer.

These are compiled into the contract bytecode, so they cannot be added or removed afterwards — only disabled permanently by renouncing ownership. Every one of them is reported by token scanners, so pick deliberately and document what you picked.

• •Mintable — the owner can create new supply. Necessary for emissions and rewards, but it means holders cannot treat the supply as fixed.
• •Pausable — the owner can halt all transfers, including DEX swaps. A real emergency brake and a real centralisation risk.
• •Blacklist — the owner can block specific addresses from transferring. Used against sniper bots; read by holders as centralised control.
• •Transfer, liquidity, dividend, and auto-burn taxes — a percentage of each transfer routed to a wallet, the pool, holders, or burned.
• •Anti-bot cooldown and per-wallet or per-transaction limits — launch protection that most projects relax after the first hours.
• •Permit (EIP-2612) — gasless approvals via signature, which improves the experience in DeFi integrations.

Once your launch is finished, consider renouncing ownership to disable all of them permanently, or transferring ownership to a multisig if you still need them.