Before you launch: what to decide first
Before deploying anything, a creator needs to settle the basics: the token contract itself (a standard ERC-20 or a custom contract with launch-specific logic), total supply, how much ETH will be paired as initial liquidity, and whether the launch will involve additional wallets beyond the creator's own.
It is also worth deciding upfront how much ETH is available for the launch overall - deployment, liquidity provisioning and gas all draw from the same budget, and Ethereum gas costs can be a meaningful part of that budget compared to other chains.
Step-by-step: launching a token on Ethereum mainnet
- Deploy the token contract and verify it on a block explorer so holders can inspect the code.
- Prepare the creator wallet and confirm it holds enough ETH for deployment gas, liquidity provisioning and any opening buy.
- If launching with additional wallets, prepare and fund each one before deployment.
- Provide initial liquidity - typically by pairing the token with ETH in a liquidity pool - and decide whether that liquidity will be locked.
- Submit the deployment and liquidity transactions, confirming each lands successfully before taking further action.
- If coordinating additional wallets, execute their buys according to your planned sequence and gas settings.
Funding wallets and estimating gas costs
Every wallet that will participate needs enough ETH to cover both its planned buy and its own gas costs - unlike some other chains, Ethereum gas costs can fluctuate significantly with network demand, so a funding buffer above a simple estimate is worth building in.
For a multi-wallet launch, funding each wallet ahead of time, with a gas buffer, removes one of the most common sources of a transaction failing right when it matters most.
Reviewing the launch before execution
- Recheck every wallet address involved - a single mistyped or wrong address can send funds somewhere unrecoverable.
- Confirm the total allocation across all participating wallets matches what you actually intended.
- Confirm the contract has been verified and its parameters (supply, taxes if any, ownership) match what you configured.
- If using a bundler or launch tool, review its execution plan screen rather than assuming the configuration matches what you entered earlier.
After launch: providing liquidity and what changes
Once liquidity is live, the token trades against normal two-sided AMM dynamics - price moves with buy and sell pressure the same way any liquidity pool does, with no bonding-curve mechanic unless the contract specifically implements one.
A creator's job does not end at deployment - reviewing how the token is trading, whether planned wallets executed as intended, and whether liquidity is locked as planned all follow the initial launch.
FAQ
- Do I need to write a custom smart contract to launch a token on Ethereum? No - a standard ERC-20 token paired with a liquidity pool is enough for many launches; custom logic is only needed for specific mechanics beyond a standard token.
- How much ETH do I need to launch a token? This depends on deployment gas, how much liquidity you plan to provide, and any additional wallets - there is no single universal figure, and gas costs vary with network conditions.
- Should I lock my liquidity? Locking liquidity is a common practice that signals to holders that the pool cannot be withdrawn unilaterally - whether and how to do it depends on the specific launch and tooling used.
- What happens if gas prices spike right before my launch? A transaction with too low a gas setting can get stuck pending or fail outright - reviewing current network conditions before submitting reduces this risk.
Coordinate your launch with TokenBundle.
Prepare wallets, review allocations and manage network-specific launch execution from one workspace.
Open Ethereum workspace