ERC20 Maker docs

Overview

ERC20 Maker is a no-code generator for ERC-20 tokens on supported EVM networks. You configure the token in the builder, review a summary of every enabled feature, then sign the deployment from your own wallet. The generated contracts follow standard ERC-20 architecture so the ecosystem — wallets, exchanges, block explorers — understands your token immediately.

Getting started

Creating a token takes three things: an idea, a wallet, and enough ETH. The whole flow is configure → review → connect → deploy, and the builder guides each step. Start on the create page, or read how it works for the full walkthrough first.

1. Decide your token's name, symbol and supply.
2. Prepare a Web3 wallet with ETH for service price + gas.
3. Configure the token in the builder and review the summary.
4. Connect, sign, and verify on the relevant block explorer.

Token settings

Four values define your token's identity. Name, symbol and decimals appear everywhere your token is shown, so choose them deliberately — they cannot be edited after deployment.

Token name

The full display name, e.g. “Example Token”. Up to 50 characters. Pick something distinctive and searchable, and check it does not impersonate an existing project.

Symbol

The short ticker, e.g. “EXT”. Letters and numbers only, 1–10 characters, conventionally uppercase. This is what holders see next to balances.

Initial supply

How many tokens exist at deployment, from thousands to billions. This is the starting point of your tokenomics: a fixed-supply token never exceeds it, while a mintable token can grow under predefined rules. See the supply guide for the full picture.

Decimals

How divisible the token is. 18 is the standard and works with virtually all wallets, exchanges and tooling. Only choose another value if you have a specific reason — the decimals guide explains the trade-offs.

Core features

Optional supply and safety controls. Each is a single toggle in the builder; enabled features appear in your summary with their live price.

Burnable

Holders can permanently destroy tokens, reducing circulation. Used to model deflationary tokenomics. Read the burnable guide.

Mintable

Keeps the ability to issue new supply after deployment — for rewards, treasury refills or phased distribution. Minting rights belong to the addresses configured at deployment. See mintable vs fixed supply.

Pausable

Temporarily halts all transfers in an emergency, then resumes. A safety switch many teams enable for the early life of a token.

Transfer controls

Limits and access rules for how your token moves between wallets. Percentages are of total supply, entered as plain numbers — 2 means 2%.

Max transaction

Caps the size of any single transfer. Discourages sudden whale dumps in thin markets.

Max wallet

Caps how much of the supply one wallet can hold. Often paired with max transaction for fairer launches. Both limits are explained with examples in the max wallet guide.

Blacklist

Blocks selected addresses from sending or receiving the token — for malicious or sanctioned addresses.

Whitelist

Restricts transfers to approved addresses. Useful for private rounds and staged rollouts. Blacklist and whitelist are compared in the lists guide.

Trading features

Launch economics configured in plain percentages. Buy tax 4 and sell tax 6 mean 4% and 6% — never 0.04%.

Buy tax

Percentage taken on buys (0–25%), routed to your marketing wallet.

Sell tax

Percentage taken on sells (0–25%). Sell taxes are often set slightly higher to discourage rapid flipping. Full examples in the tax guide.

Marketing wallet

The address receiving fee revenue. Must be a valid 0x… Ethereum address. Confirm it twice — fees sent to a wrong address cannot be recovered.

Anti-bot

Temporary launch protections that make automated sniping harder in the first blocks after trading opens.

Auto-liquidity

Routes a share of trading fees into liquidity automatically, so market depth builds as volume grows.

Tokenomics guide

Tokenomics is how your supply behaves over time. Common patterns:

• Fixed supply — no minting. Scarcity is set once at deployment.
• Deflationary — burnable supply that shrinks as tokens are destroyed.
• Fee-funded — small trading fees sustain marketing or liquidity wallets.
• Capped distribution — max-transaction and max-wallet limits discourage concentration.

Pricing

Start at 0.02 ETH. Add only the token features you need. Most optional features cost 0.005 ETH each. Trading Fees, Anti-Bot and Auto Liquidity cost 0.01 ETH each. The builder totals your exact service price live.

Gas & cost guide

Total cost has two parts:

1. Service price — shown live in the builder summary in ETH before you continue.
2. Network fee (gas) — paid in ETH from your wallet at deployment on the selected network. It varies with network congestion and is never set by us.

Wallet connection

Connection means your wallet authorizes this site to propose transactions — it never shares keys. You review each transaction (action, network fee, total) in the wallet itself and approve or reject it there. Disconnect any time from the wallet.

Supported networks

Deploy to Ethereum Mainnet, Base, Arbitrum One or OP Mainnet. Select the network in the builder before continuing.

Your wallet must hold enough ETH on the selected network. Deployment means real value, real fees and permanent history — test your configuration carefully in the builder first.

Ethereum Mainnet

Ethereum Mainnet (Chain ID 1) is the default network: the deepest liquidity and the reference ERC-20 ecosystem. Your wallet must be on the selected network with enough ETH.

Deployment

What happens, in order:

1. You review the builder summary and continue.
2. Your wallet proposes the deployment transaction.
3. You sign. The transaction broadcasts to the selected network.
4. Validators include it in a block (usually seconds to minutes).
5. The receipt returns your new contract address.

Verification guide

Source verification on the relevant network explorer publishes your contract code next to the deployed bytecode so anyone can confirm what the token does. Ethereum deployments use Etherscan; Base, Arbitrum and Optimism each have their own explorer. Follow the explorer's verify flow with the exact source and compiler settings. Ethereum walkthrough: verify on Etherscan. Verification is transparency — not an audit.

After deployment

To see and share your token:

1. Copy the contract address from the deployment receipt or relevant block explorer.
2. Import it in MetaMask via import-tokens — full instructions.
3. Verify the source on the relevant network explorer.
4. Share the address through channels you control — see after deployment.

Troubleshooting

Security

Deployment is non-custodial: you sign from your own wallet and keys never leave your control. Still, launching a token carries real risk — smart-contract behaviour, market dynamics and regulation. Read the disclaimer, verify your contract, keep deployer keys offline where possible, and never deploy from a compromised device. More: security best practices.

Glossary