Create an ERC-20 token in minutes
This is the action page: what to do, in order, to go from idea to a live ERC-20 on one of the four supported EVM networks.
- Networks · 4 EVM chains
- Starting fee · 0.02 ETH
Before you click anything (5 minutes)
Write down three decisions: the exact token name, the symbol, and the supply figure with its reasoning (fixed scarcity vs mintable flexibility). Check the name against impersonation on Etherscan and social platforms. Confirm your wallet holds ETH for the service price (from 0.02 ETH) plus a gas buffer, and that any marketing wallet address is copied from its source — never retyped.
Do this now
- Write down name, symbol, supply — check for impersonation.
- Prepare a wallet with ETH on the selected network for service price plus gas.
- Configure in the builder and read the entire summary.
- Sign the deployment when gas is reasonable.
- Verify on the relevant block explorer and publish the address yourself.
How long each step takes
| Step | Typical time | Waiting on |
|---|---|---|
| Configuration | 3–10 minutes | Your decisions |
| Review | 5–10 minutes | Your carefulness |
| Signing | 1 minute | You |
| Confirmation | Seconds–minutes | Selected network conditions |
| Verification | 5–15 minutes | You, once |
Mistakes that waste money
- Mistyped marketing wallet — fees go there forever.
- Skipping the summary review — the last editable moment.
- Deploying at peak gas — check a tracker first.
- Enabling features you don't understand — minimal is safer.
Decision fatigue management
Configuration involves dozens of micro-decisions; fatigue degrades the later ones (usually wallets and review — the highest-stakes items). Counter it structurally: decide identity and supply on a separate day from deployment, take breaks between configuration and review, and never sign tired. Spreading decisions across sessions costs nothing and protects everything.
Pre-signing pause protocol
Before every signature, pause thirty seconds and answer: what action is this, what does it cost, what is irreversible about it? If any answer is unclear, stop and re-read rather than signing through confusion. This micro-ritual costs half a minute and prevents the signature-speed mistakes behind most user-side losses. Fast fingers lose funds; deliberate ones keep them.
What to do when stuck
Stuck mid-flow is normal and safe — nothing happens until you sign. Identify the exact blocker: confusion about a setting (read its guide), wallet trouble (check network and funds), gas anxiety (consult a tracker), or cold feet (sleep on it). Each has a specific remedy in the docs; generic rushing has none. Stopped-and-safe beats moving-and-unsure every time.
Readiness self-test
Answer five questions honestly: can you state your supply model in one sentence, is every wallet address confirmed from source, does the wallet hold service price plus buffer, have you checked gas conditions, and can you explain each enabled feature? Five yeses means proceed; any no means pause on that item specifically. Launches fail on skipped fundamentals, never on insufficient enthusiasm.
First-timer timeline
| Phase | Time | Activity |
|---|---|---|
| Prepare | Evening before | Decisions, wallets, funding, tracker check |
| Configure | 10 minutes | Builder fields + feature toggles |
| Review | 10 minutes | Aloud read-through + address checks |
| Deploy | 5 minutes | Sign, confirm, record address |
| Verify | 15 minutes | Block explorer + wallet import + announcement |
What 'minutes' actually means
Minutes refers to mechanics, honestly measured: configuration (your speed), review (your care), signing (one minute), confirmation (network-dependent, usually fast). What takes longer — and should — is deciding: supply model, fees, wallets, distribution. Budget an evening for decisions, minutes for execution. Anyone promising instant launches without decisions is selling recklessness.
Pre-flight checklist
| Item | Status to confirm |
|---|---|
| Identity | Name/symbol written, impersonation checked |
| Supply | Figure matches plan; model (fixed/mintable) decided |
| Wallets | All addresses copied from source, double-checked |
| Funds | Service price + gas buffer present in deployer wallet |
| Timing | Gas tracker consulted; calm window chosen |
Right after signing
Record the contract address from the receipt, verify the source, import the token in your wallet to confirm display, then announce through your own channels with the fee and limit settings documented. The post-launch playbook covers the first hour in full.
Common questions
How long does it take?
Configuration takes minutes; on-chain confirmation usually seconds to minutes depending on gas.
What if I make a mistake?
Before signing: fix it free. After signing: only rules baked into the contract (like minting) can change anything.
Can I do this on my phone?
Yes, with a mobile Web3 wallet — though a desktop review of the summary is calmer for a permanent transaction.
Related guides
Ready to build?
Configure your token, review the price, and deploy from your wallet.