Core concepts
Bundles, dev wallets, distributor wallets, atomicity, simulation and the other terms used across the docs.
These terms appear on every launch page. Read this once and the network pages will make sense.
Bundle
A bundle is a group of transactions sent together: the launch (or the call that opens trading) and the buys from your wallets. Each network enforces the grouping differently, so "bundle" means a slightly different guarantee on each one:
| Network | Mechanism | Guarantee |
|---|---|---|
| Solana | Jito bundle (max 5 transactions) | All-or-nothing, in order, in one block — dev + up to 8 bundle wallets |
| Ethereum | Flashbots bundle to 4 block builders | All-or-nothing, in order, in one block — any number of wallets |
| BNB Chain | Bundle to BSC builders (48 Club, BlockRazor) | All-or-nothing, in order, in one block — any number of wallets |
| Robinhood Chain | Sequential broadcast on an FCFS sequencer | Not atomic. Buys go out immediately after trading opens, in order, first-come-first-served |
Wallet roles
Dev wallet
The wallet that creates the token (Solana, Pons) or deploys the contract (Deploy Token). It shows on-chain as the creator. Mark one wallet with ★ Dev on the Wallets page to pre-select it where the network supports that.
Bundle wallets
Wallets that buy together with the launch. On Solana these are the up-to-3 wallets inside the Jito bundle.
Snipe wallets (Solana)
Up to 50 extra wallets that buy right after the launch lands, usually in blocks 1–3. Each one sends its own small Jito bundle. They are fast but not atomic with the launch.
Deployer and Master (Custom Bundle)
Deployer is the contract owner. It calls the function that opens trading. Master funds every bundle wallet in one Multicall3 transaction and pays the service fee. You paste both keys into the page. They stay in your browser tab's memory and are never stored.
Service wallets
Wallets added by your Custom Bundle fee tier. They buy last in the same bundle, after all of your wallets. They belong to TokenBundle, and their keys are never shown.
Funding models
- Wallet-to-wallet: one of your wallets sends to the others. Fast, but the on-chain link between them is visible.
- One-time deposit address (Solana Wallets page, PumpFun Bundle and the Terminal's Fund; EVM Disperse): a fresh address with no history. When your deposit arrives, it fans out to the selected wallets automatically. The link from the deposit address to the wallets is still visible on-chain. This is not a mixer.
- Master batch (Custom Bundle): one Multicall3 transaction funds every bundle wallet with its exact amount.
Simulation
Simulation dry-runs your launch against the current chain state. It sends nothing and costs nothing. On Solana it simulates the full bundle and snipe transactions. On EVM chains it checks the whitelist call, the open-trading call and a sample buy. Ethereum Execute also simulates the signed bundle again right before it submits.
INSUFFICIENT_LIQUIDITY result on that line is expected.Progressive cost
When many wallets buy one after another from the same pool, each buy moves the price. Custom Bundle prices every wallet in order against a constant-product (Uniswap V2, 0.3% fee) pool, so later wallets cost more. That is why the cost panel shows a per-wallet range and not one number.
Anti-snipe window and whitelist
Tokens made with Deploy Token have an anti-snipe window: for N blocks after trading opens, only whitelisted addresses can buy. Custom Bundle whitelists its own wallets automatically, using the contract's configureLaunch(address[], bool) function, right before it opens trading.