> For the complete documentation index, see [llms.txt](https://docs.j.tools/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.j.tools/tools/launch/pumpfun-create-and-bundle-buy.md). # Pump.fun Create and Bundle Buy Last updated: June 2026 · Solana mainnet Pump.fun Create and Bundle Buy launches a token on the Pump.fun bonding curve and fires opening buys from up to 16 wallets you control, all packed into one same-window Jito bundle on Solana mainnet. It runs from your browser wallet, with no install, and a flat platform fee is shown before you sign. Token creation and the first buys land together in deterministic order, so the launch sequence is yours rather than a sniper's. You drive the whole launch from the [Pump.fun Create and Bundle Buy tool](https://j.tools/en/tools/pump-create) in the J Tools app. This is an operator-level flow, not the basic single-wallet create. If you want the plain version first, the [launch a token guide](/guides/launch-a-token.md) and the [choosing how to launch](/concepts/choosing-how-to-launch.md) page walk through the options. ```mermaid flowchart TD A[Configure the token and the first buys] --> B[Create the token on the Pump.fun curve] B --> C[Bundle the first buys through Jito] C --> D{They land atomically in one slot} D --> E[Token is live with its initial holders] classDef brand fill:#EF2A2A,stroke:#EF2A2A,color:#ffffff,font-weight:bold; classDef soft fill:#1f2937,stroke:#374151,color:#e5e7eb; class D,E brand; class A,B,C soft; ``` {% hint style="warning" %} **About fees.** Every action has two costs: the Solana **network fee** paid to validators, and the **J Tools platform fee**. The platform fee always shows in the app before you confirm, and nothing is charged until you sign. Fees can change over time, so trust the in-app summary rather than a number you saw once. {% endhint %} {% hint style="danger" %} This tool reads the **raw private key** of every bundle wallet in your browser so it can sign their buys. Only use wallets you control, and treat this as a multi-key launch tool, not a single-signer one. {% endhint %} ## When to use this * You run Pump.fun launches and want controlled, anti-snipe execution instead of a plain single-wallet create. * You want the creator buy plus an initial buy spread across several wallets you own, all sequenced together. * You already hold the private keys for every bundle wallet you plan to include. If you only need a simple single-wallet Pump.fun launch, use [Pumpfun Create](/tools/launch/pumpfun-create.md) instead. To launch a token and seed a real liquidity pool on a DEX, see [Create LP and Buy](/tools/liquidity/lp-create-buy.md). For the mechanics behind atomic landing, read up on [bundles and Jito](/concepts/bundles-and-jito.md). ## Before you start * A connected wallet **or** a creator private key. The creator wallet must also appear in your bundle wallet list, otherwise the launch is blocked. * Token metadata ready: a name (up to 32 characters), a symbol (up to 10 alphanumeric characters), a description (up to 500 characters), and a token image (uploaded, or a valid `http`/`https` URL). A banner and social links are optional. * A private key for each bundle wallet (Base58, Base64, or array format). Each wallet needs enough SOL for its own buy amount, its reserve, network and priority fees, and its share of the Jito tip. * SOL to cover the platform fee, a per-wallet service fee, the creator and bundle buy amounts, the Jito tip, and network fees. The app shows the full breakdown before you launch. {% hint style="warning" %} The mint address must end with the **`pump`** suffix, and that policy is locked to strict. If you supply your own vanity mint key, it has to already end with that suffix or the launch is rejected. {% endhint %} ## Step by step {% stepper %} {% step %} ### Connect and fill in token info Connect a wallet or supply the creator private key. Enter the name, symbol and description, upload the token image, and add a banner or social links if you want them. Twitter and Telegram accept an `@handle` or a full URL; website wants a full URL. {% endstep %} {% step %} ### Set the creator buy Enter how much SOL the creator wallet spends as the first buy in the sequence. The default is `0`, so set it to whatever opening size you want from the creator. {% endstep %} {% step %} ### Pick your tips and priority Choose a Jito MEV tip preset (Default, High, or Ultra) or a custom value, and a priority-fee preset. A higher tip improves the odds your bundle wins its auction and lands. {% endstep %} {% step %} ### Add your bundle wallets Add up to 16 wallets, each with its private key, a buy amount, and a reserve. Refresh balances so the tool can check funds and compute a fee-safe maximum buy for each row. {% endstep %} {% step %} ### Review the summary Check the live preview: wallet count, total bundle buy, the platform fee, the per-wallet service fee, the Jito tip, and the grand total. Nothing is sent until this looks right. {% endstep %} {% step %} ### Launch in window Click **Launch In Window**. The tool runs preflight (balance and duplicate-wallet checks), builds the create-plus-buy bundle, and has the creator wallet sign. It then submits token creation and all buys as same-window Jito bundles in deterministic order, polling each for confirmation. {% endstep %} {% endstepper %} [**Open Pump.fun Create and Bundle Buy in the app →**](https://j.tools/en/tools/pump-create) {% hint style="info" %} **About wallet warnings.** Some tools sign more than one thing in a single step, for example creating a token and its metadata together. Phantom can show a caution banner for these multi-step transactions. The banner is expected here and does not mean something is wrong. Read what you are signing, then approve. {% endhint %} ## Why bundle the launch instead of doing it manually? Doing this by hand means creating the token, then racing to send each opening buy in separate transactions, where a sniper can wedge in between your create and your first buy. The bundle approach packs everything into one same-window Jito submission so the order is set before anything hits the chain. Here is how the two compare. | | Pump.fun Create and Bundle Buy | Manual multi-wallet launch | | ----------------- | ------------------------------------------ | ----------------------------------------- | | Setup | No-code, runs in your browser wallet | Scripts or several manual sends | | Launch order | Deterministic, same-window Jito bundle | Whatever order the network confirms | | Anti-snipe | Create and first buys land together | Gap between create and buy is snipeable | | Wallets | Up to 16 in one flow, fee-safe max per row | You track funding and limits yourself | | Authority control | You keep your keys; non-custodial | You keep your keys, but more moving parts | | Cost clarity | Flat platform fee shown before you sign | You add up tips, fees, and buys yourself | ## The options, explained | Field | What it does | | ----------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Name / symbol / description / image | Token metadata. Name up to 32 chars, symbol up to 10 alphanumeric chars, description up to 500 chars. Image must be an upload or a valid `http`/`https` URL. Banner is optional. | | Twitter / Telegram / website | Optional social links. Twitter and Telegram take an `@handle` or full URL (up to 100 chars); website needs a full URL (up to 200 chars). | | Creator buy amount (SOL) | SOL the creator wallet spends as the first buy in the launch sequence. Default `0`. | | Bundle wallets | One to 16 wallets, each with a private key, a buy amount above zero, and a reserve (default `0.005` SOL). The maximum is 16 wallets. | | Jito tip | Controls bundle landing priority. Presets are Default, High, and Ultra (Ultra is the UI default), or a custom value within the accepted range. | | Priority fee | Compute-budget priority fee in micro-lamports. Presets are Default, High, and Ultra; High is the UI default, or set a custom value. | | Mode | Fixed to same-window multi-bundle. It is the only valid execution mode. | | Mint suffix | The mint must end with `pump`, locked to strict. An optional vanity mint key must already match that suffix. | {% hint style="info" %} Execution is **deterministic same-window**, which is strong anti-interleave intent. It is not a strict on-chain atomic guarantee. Bundles can land in different slots, and in rare cases only part of the set lands. The summary and your confirmations show what actually went through. {% endhint %} ## Fees This launch has more cost lines than a single-wallet tool. The summary lays them out before you commit: * **Platform fee** for the launch, shown in the app. * **Per-wallet service fee**, which is tiered by how many bundle wallets you include. More wallets means a lower per-wallet rate. * **Jito tip**, **priority fee**, and **network fees**, paid separately. * **The actual SOL buy amounts** for the creator and each bundle wallet. Fee amounts are admin-configurable, so read the in-app summary rather than any fixed figure. The current numbers live in the [Fee schedule](/reference/fee-schedule.md), and [fees explained](/getting-started/fees-explained.md) covers how each line is charged. If a term here is new to you, the [Glossary](/getting-started/glossary.md) defines mint, bundle, and Jito tip. ## If something goes wrong * **Creator not in the bundle.** The connected creator wallet has to be one of the bundle wallets. Add it to the list and try again. * **A wallet is underfunded.** Each wallet needs its buy amount plus reserve plus fees plus its tip share. Preflight stops before sending if any wallet fails validation, which avoids wasting a tip. Top up the wallet and refresh balances. * **Bundle drifted or only partly landed.** The bundles can land in different slots or only some of them land. Check the per-bundle confirmation in the summary to see what went through. * **Bundle did not land.** On a rate-limit or auction rejection the bundle may not land. A higher Jito tip improves your odds; if the tip was already sent for a landed bundle it is not refundable. * **Mint suffix rejected.** Your vanity mint key must already end with `pump`. Use a key that matches, or let the tool generate one. For the full list, see the [Error codes reference](/reference/error-codes.md). ## FAQ
How many wallets can I bundle? Up to 16, including the creator wallet. Each one needs a valid private key and a buy amount above zero.
Is the whole launch guaranteed to land in one slot? No. The tool aims for same-window, deterministic landing with strong anti-interleave intent. It is not a strict on-chain atomic guarantee, so bundles can land in separate slots, or only part of the set can land. Treat the in-app confirmations as the source of truth.
Does J Tools hold the private keys I paste in? No. J Tools is non-custodial. The bundle-wallet keys are used in your browser to sign that launch and are not stored or transmitted to us. Even so, only use wallets you control, and consider rotating any wallet whose key you have pasted into a browser tool.
Why does the creator wallet have to be in the bundle? The creator buy is the first step in the launch sequence, so the tool needs the creator wallet present in the bundle list to sign and sequence it. If it is missing, the launch is blocked before anything is sent.
Should I raise the Jito tip? A higher tip improves the odds your bundle wins its auction and lands in the window you want. The trade-off is cost: if a bundle lands, that tip is spent. Start with a preset and raise it only if you are launching into heavy competition.
How does bundling stop snipers? Snipers watch for a fresh token and try to slip a buy in right after creation, before your own buys land. Packing the create and your opening buys into one same-window bundle removes that gap, so your wallets are the first holders. For the wider playbook, see the [safe Pump.fun launch guide](/guides/pumpfun-safe-launch.md).
## Related tools {% content-ref url="/pages/xENB3pWkEElG6NsYww6X" %} [Pumpfun Create](/tools/launch/pumpfun-create.md) {% endcontent-ref %} {% content-ref url="/pages/CamsCO8l3GAbpPyUzhxh" %} [LP Create and Buy](/tools/liquidity/lp-create-buy.md) {% endcontent-ref %} {% content-ref url="/pages/ABVX2mBQDoCv7DEdVmKp" %} [Multi Sender](/tools/wallets/multi-sender.md) {% endcontent-ref %} {% content-ref url="/pages/gbx1RbByQOVKZzt0PQkP" %} [Make Immutable](/tools/secure/make-immutable.md) {% endcontent-ref %} {% hint style="success" %} **J Tools is non-custodial.** We never hold your private keys and never ask for them. Every transaction is built in your browser and signed by your own wallet. If any page ever asks you to paste a private key, stop, close it, and let us know. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.j.tools/tools/launch/pumpfun-create-and-bundle-buy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.