How to Launch a Token on Base (Step by Step)

Before you start

Base is an OP Stack layer 2 with chain id 8453, about 2 second blocks built in 200 ms Flashblocks, and no public mempool. Transactions go privately to the sequencer. Gas is paid in ETH, and on top of L2 gas every sender also pays an L1 data fee from its balance.

You will need two wallets you control: a Deployer, which deploys and owns the token, and a Master, which funds the bundle wallets and pays the TokenBundle fee. Their keys are used during the session and never stored.

Step 1: Deploy the token

Open Deploy Token and choose a Clog or Standard Tax ERC-20. Set the name, supply and taxes, then the Max Tx % and max wallet %. Keep the anti-snipe whitelist window on; the default is 15 blocks, about 30 seconds on Base. During that window only whitelisted wallets can buy.

After deployment, verify the contract on BaseScan so holders can read the code.

Step 2: Seed the contract

Seed the token contract with ETH and tokens before you set up the bundle. When trading opens, the launch buys go through the Uniswap V2 router on Base, paired against WETH.

Make sure the Deployer still holds enough ETH for its own transactions. On Base every sender pays the L1 data fee on top of L2 gas, so a wallet that looks funded for gas alone can still come up short.

Step 3: Set up Custom Bundle

• Token: enter the token address.
• Keys: add the Deployer and Master keys. They are never stored.
• Recipients: generate or import 1-100 bundle wallets. If you plan to use Atomic mode, stay within 75 of your own wallets.
• Set buy sizes: each wallet buys its Max Tx % target, priced in order, and sizes can be randomized from 0 to 50% (default 15%).

Step 4: Distribute ETH to the wallets

Distribute funds every bundle wallet in one Multicall3 transaction from the Master. Each wallet gets its buy amount plus a 0.0005 ETH reserve that covers its own buy gas, the L1 data fee and a later sell.

Step 5: Review and pick a launch mode

Review shows the full plan: wallets, buy amounts and the fee. Check each wallet and the totals before going on. Fees are paid once from the Master: 0.25 ETH plus a 0.75 ETH tip with no service wallets, 0.15 ETH with 1, 0.1 ETH with 2 (recommended) or 0.01 ETH with 3.

At Execute you choose the launch mode. Burst, the default, sends the whitelist call, the open and one buy per wallet as one ordered batch to the sequencer after a dry run with eth_simulateV1. Atomic sends everything as one EIP-7702 transaction that lands whole or reverts whole, with all wallets visibly linked on BaseScan.

Step 6: Execute and check the result

With Burst and a Deploy Token contract, every bundle wallet is whitelisted before trading opens, so any other buy during the window reverts. Check the open and the buys on BaseScan. With Burst, each buy appears as its own transaction; with Atomic, all wallets appear inside one transaction.

If you used Atomic mode, every delegation is revoked after the launch, so the bundle wallets are plain EOAs again.

Once the launch is done, use the Terminal to buy and sell across your bundle wallets and follow PNL. On Base, those trades go to the sequencer, with no public mempool. Each wallet's 0.0005 ETH reserve is there to cover a later sell.

FAQ

• Do I need my own token contract? No. Deploy Token creates a Clog or Standard Tax ERC-20 with taxes, limits and an anti-snipe whitelist window.
• How much ETH does each wallet need besides its buy? Each wallet keeps a 0.0005 ETH reserve for its buy gas, the L1 data fee and a later sell.
• Which DEX is used on Base? The Uniswap V2 router on Base, with the token paired against WETH.
• Should I use Burst or Atomic? Burst with a Deploy Token whitelist reaches about 100% and looks organic; Atomic is all-or-nothing but links the wallets in one transaction.
• Can I verify my token? Yes. Verify the contract on BaseScan after deployment.

Related guides