By What a token launch bundler does on Base
A token launch bundler coordinates the moment trading opens: the call that opens trading and a set of buys from several wallets you control, placed so that your wallets buy first and at the prices you planned. On Ethereum this is usually done with a Flashbots bundle. On Base the same goal needs a different approach, because the chain is built differently.
Base is an OP Stack layer 2 with chain id 8453. Blocks come about every 2 seconds and are built in 200 ms Flashblocks. Understanding how those blocks are ordered is the key to understanding how a bundler can work here.
Why Base has no bundles
Base has no public mempool. Transactions go privately to the sequencer, and inside a Flashblock the sequencer orders them by priority fee, then by arrival. There is no builder or relay market sitting in front of it.
That also means there is no bundle market. Public Base RPCs and the sequencer endpoint reject eth_sendBundle, and Base's own bundle service (TIPS) was archived in July 2026. Any tool that claims to send a Flashbots-style bundle on Base has to be doing something else under the hood.
TokenBundle uses two methods that work with how Base actually orders transactions: Burst, which relies on an ordered batch sent straight to the sequencer, and Atomic, which uses EIP-7702 to put the whole launch into a single transaction.
The two launch modes in short
- Burst (default): the whitelist call, the open-trading call and one buy per wallet are separate transactions, signed up front, dry-run in order with eth_simulateV1, then sent as one ordered JSON-RPC batch to the Base sequencer with the same priority fee on every transaction. Buys usually land in the same Flashblock as the open.
- Atomic (Max protection): one EIP-7702 type-4 transaction from the Deployer carries authorizations from the Deployer and every bundle wallet. It opens trading and runs every wallet's buy in one go, so it lands whole or reverts whole and nothing can land in between.
- Burst looks organic on BaseScan because each buy is its own transaction from its own wallet. Atomic shows every wallet inside one transaction, so the wallets are visibly linked.
The TokenBundle flow on Base
The flow starts with Deploy Token, which creates a Clog or Standard Tax ERC-20 with taxes, a Max Tx %, a max wallet % and an anti-snipe whitelist window. The default window is 15 blocks, about 30 seconds on Base. You can verify the contract on BaseScan, then seed it with ETH and tokens.
Custom Bundle then runs in 6 steps: Token, Keys (Deployer and Master; keys are never stored), Recipients (1-100 wallets, generated or imported), Distribute, Review and Execute, where you choose Burst or Atomic.
Wallet funding and buy sizing
Distribute funds every bundle wallet in one Multicall3 transaction from the Master wallet. Each wallet keeps a 0.0005 ETH reserve that covers its own buy gas, the OP Stack L1 data fee that is charged from the sender's balance on top of L2 gas, and a later sell.
Each wallet buys its Max Tx % target, priced in order, so later wallets are sized against the price after earlier buys. Buy sizes can be randomized from 0 to 50%, with a default of 15%.
Fees on Base
Fee tiers on Base are the same as on Ethereum and are paid once from the Master wallet. More service wallets in the bundle means a lower flat fee.
| Flat fee | Extra | Service wallets |
|---|---|---|
| 0.25 ETH | 0.75 ETH tip | 0 |
| 0.15 ETH | - | 1 |
| 0.1 ETH (recommended) | - | 2 |
| 0.01 ETH | - | 3 |
After the launch: the Terminal
Once the token is trading, the Terminal lets you buy and sell across your bundle wallets with a live chart and PNL. Trades are routed through the 0x aggregator across Base's DEXes and go to the sequencer, which has no public mempool for anyone to watch.
FAQ
- Can I send a Flashbots bundle on Base? No. Public Base RPCs and the sequencer endpoint reject eth_sendBundle, and Base's own bundle service (TIPS) was archived in July 2026.
- Which launch mode is the default? Burst is the default. It sends an ordered batch straight to the Base sequencer, and Atomic is available when you want an all-or-nothing launch.
- How many wallets can I use? Custom Bundle supports 1-100 wallets. Atomic fits up to 75 of your own wallets because of the per-transaction gas cap.
- Does TokenBundle store my private keys? No. The Deployer and Master keys are used for the session and are never stored.
- Which DEX does the launch trade on? Buys go through the Uniswap V2 router on Base, paired against WETH.
Coordinate your launch with TokenBundle.
Prepare wallets, review allocations and manage network-specific launch execution from one workspace.
Open Base workspace