Skip to content
J Tools
Open J Tools

Bundles and Jito

A bundle is a group of transactions submitted together so they land in the same block, in the order you set. J Tools builds these bundles and sends them to the Jito Block Engine, the infrastructure that lets a validator include the whole group in one slot.

HOW J TOOLS SENDS A BUNDLE

  1. You sign in your wallet
  2. The bundle is assembled with a tip createfirst buytip ATOMIC
  3. It goes to the Jito Block Engine
  4. Landing is confirmed one shared slot

This matters most when the order of two actions decides who wins. Create a token and buy it in the same block, and no bot can slip a buy in between. That is exactly what Pump.fun Create & Bundle Buy does, and the fair-launch guide walks through the playbook end to end.

Explore the tools in the app →

Why a bundle instead of separate transactions

#why-a-bundle-instead-of-separate-transactions

Send two transactions one after another and a lot can happen in the gap. Validators are free to reorder them. A sniper watching for new mints lands a buy right between your create and your first buy. Sometimes one confirms while the other simply expires.

A bundle closes that gap. The transactions are tied together before they ever reach a validator, so they land in one block, in your order, with no room for a stray buy in the middle. A single bundle is all-or-nothing.

Two common reasons to bundle:

  • Fair launch. Your create and your first buy land in the same block, so you are first by design.
  • Group trades. Many wallets buy or sell in one coordinated block instead of a slow, leaky sequence. This is the engine behind Bundled Trade. To send the same trade from many wallets without atomic bundling, see Multi Swap instead.

What a tip is

#what-a-tip-is

For a bundle to land through the Jito Block Engine, you attach a tip, paid in lamports to a Jito validator. Think of it as the priority fee for bundles: a priority fee bumps a single transaction up the queue, and a tip does the same job for the whole group. A higher tip during busy periods makes your bundle more attractive to include, and a tip that is too low can leave it sitting.

You rarely hand-tune this. J Tools reads the recent tip floor from Jito, so the tip tracks current network conditions. In Bundled Trade you pick a tip preset (Low, Med or High), and the tool only raises it when the live floor moves above your setting. Pump.fun Create & Bundle Buy works the same way through its Jito tip presets (normal, fast or turbo). It is part of the cost you see, separate from the platform fee for the tool.

How J Tools sends a bundle

#how-j-tools-sends-a-bundle

  1. You sign in your wallet

    Every transaction in the bundle is signed browser-side: through your wallet adapter, or, in the multi-wallet bundle tools, locally from the keys you imported. Nothing is signed on a server.

  2. The bundle is assembled with a tip

    The signed transactions are grouped into one bundle, which carries a Jito tip set from your preset and the current tip floor.

  3. It goes to the Jito Block Engine

    The bundle is submitted to the Block Engine, which runs across several regions worldwide. Bundles keep working even when other RPC providers are having a bad day.

  4. Landing is confirmed

    J Tools checks on-chain whether each bundle landed. A run can span several bundles. In Bundled Trade a bundle that misses is re-sent once with a fresh blockhash, and one that still cannot land is reported so you can retry exactly those wallets.

Beyond the tip preset, none of this needs configuring. The tool sends a bundle when the action calls for one.

If something goes wrong

#if-something-goes-wrong
  • Bundle did not land. The network was congested or the tip was too low for that moment. Try again; the tip re-estimates from the current floor.
  • Partial land. When a run spans several bundles, some can land while others miss. J Tools detects this and re-sends a missed bundle once; if it still cannot land, the tool lists its wallets as failed so you can retry just those.
  • Transaction expired. A blockhash in the bundle aged out before it landed. Submit again with a fresh one.

For the full list, see the Error codes reference.

#related-tools

© 2026 J Tools