Key takeaways
- A Jito bundle is a list of up to 5 signed Solana transactions that a Jito-connected leader executes in order within one slot, and the whole bundle is rejected if any transaction in it would fail.
- Jito enforces a minimum bundle tip of 1,000 lamports, paid as a plain SOL transfer to one of 8 tip accounts returned by the getTipAccounts method.
- On November 5, 2026 at 10:32 UTC, Jito's tip floor API showed a median landed tip of 0.0000172 SOL and a 95th percentile of 0.00057 SOL.
- A Jito bundle only lands in a slot whose leader runs Jito's client, and Jito's own documentation says submitting a bundle does not guarantee it lands.
- Pump.fun bundle launchers use Jito bundles so the create transaction and the creator's buyer-wallet purchases land in the same block or not at all.
The short answer
A Jito bundle is a group of up to five signed Solana transactions that a validator running Jito's client executes in the exact order you list them, inside a single slot, and only if every one of them succeeds. You pay for it with a tip: a SOL transfer of at least 1,000 lamports to one of Jito's eight tip accounts. Bundles are what make same-block launches, graduation buy-outs and atomic multi-wallet buys possible on Solana.
How does a Jito bundle work?
A Jito bundle works by sending a list of transactions to Jito's block engine instead of to the public Solana network, where the leader's Jito client includes them back to back. Jito's low-latency transaction docs set four rules:
- Up to five transactions. "Bundles are groups of transactions (max 5) bundled together."
- Sequential. "Transactions in a bundle are guaranteed to execute in the order they are listed."
- One slot. "Bundles execute within the same slot", so a bundle cannot be split across blocks.
- All or nothing. "Bundles can only contain successful transactions." If any transaction would fail, the whole bundle is rejected.
You send a bundle with the sendBundle JSON-RPC method, passing the signed transactions, and track it with getBundleStatuses or getInflightBundleStatuses, which reports Pending, Landed, Failed or Invalid for bundles from the last five minutes. The global endpoint is mainnet.block-engine.jito.wtf, with regional ones in Amsterdam, Dublin, Frankfurt, London, New York, Salt Lake City, Singapore and Tokyo. The default rate limit is 1 request per second per IP per region.
Atomicity is the point. Without a bundle, five transactions sent at once can land in different blocks, in any order, with some failing and some succeeding. With a bundle, either the whole sequence happens or none of it does, and no other transaction can be placed between them.
What is a Jito tip and how much is it?
A Jito tip is an ordinary System Program transfer of SOL to one of the eight tip accounts returned by Jito's getTipAccounts method, and the minimum Jito enforces for bundles is 1,000 lamports (0.000001 SOL). Jito's docs suggest picking one of the eight accounts at random to reduce contention, and advise putting the tip "in the same transaction that is running the MEV strategy" so it can never be paid without the trade it pays for.
How much lands in practice changes minute by minute. Jito publishes percentiles of recently landed tips at https://bundles.jito.wtf/api/v1/bundles/tip_floor. On November 5, 2026 at 10:32 UTC it returned:
| Percentile of landed tips | SOL | Lamports |
|---|---|---|
| 25th | 0.000004384 | 4,384 |
| 50th (median) | 0.0000172 | 17,200 |
| 75th | 0.0001077 | 107,700 |
| 95th | 0.0005656 | 565,600 |
| 99th | 0.000927 | 927,000 |
At the median that morning, a tip cost a fraction of a cent. The upper percentiles are where competition shows: in the first block of a popular launch, many bundles want the same accounts, and the block engine favors bundles that pay more. SOLTidy's bundle tools default to 0.001 SOL, just above the 99th percentile in this sample, and let you change it.
Tips and priority fees are different instruments: a priority fee is charged by the protocol on any transaction that lands, failed or not, while a tip is only paid when it executes. Priority fees vs Jito tips compares them in detail, and the free Priority Fee Tracker shows the live priority fee market. For bundles, Jito's docs say "only the Jito tip matters"; for single transactions sent through Jito's sendTransaction, they recommend about a 70/30 split between priority fee and tip.
What are Jito bundles used for?
Bundles are used whenever several transactions must land together and in order. The common cases:
| Use | What is in the bundle | Why a bundle |
|---|---|---|
| Bundle launch on pump.fun | Create + dev buy, then 4 transactions of buyer-wallet buys | Your own wallets buy in the launch block, in a fixed order, at known prices |
| Graduation buy-out | Several wallets' buys, the last one completing the curve | Either the whole curve is bought out or nothing is spent |
| Same-block mass buy | Up to 5 Jupiter swaps from different wallets | All wallets enter at once, none left half-filled |
| Arbitrage and liquidations | Trades that only pay off together | A failed leg costs nothing |
On SOLTidy, the Pump.fun Bundle Launcher fits up to 16 buyers into one bundle: your wallet's create and dev buy in the first transaction, then four transactions carrying the other wallets' buys, the last with the tip. How a pump.fun bundler works goes through that layout. Solana Mass Buy has a same-block mode that packs Jupiter swaps into bundles of about five wallets, and the Pump.fun Graduation Buy uses one bundle for up to 13 wallets.
The limit on wallets per bundle comes from transaction size, not from Jito. Legacy and v0 Solana transactions are capped at 1,232 bytes, according to the Solana transaction docs, and every extra signer adds a 64-byte signature plus its accounts. On pump.fun, four buyers fit in a transaction; on Bonk.fun, whose buys also wrap SOL, only two fit, so a Bonk.fun bundle launch holds nine buyers including you.
Why do Jito bundles fail to land?
Bundles fail for a handful of reasons, and in every case nothing in the bundle runs and no SOL leaves any wallet.
- No Jito leader. Tips "do not prioritize transactions for validators that are not Jito-Solana leaders", per Jito's docs, so a bundle only lands in slots led by a validator running Jito's client. Jito's stake pool API reported 98.4% of Solana stake delegated to Jito-running validators in epoch 1077 (November 2026). Counts by client type differ: Jito's Q2 2026 report, as summarized by Solana Compass, put the Jito client family at about 54% of stake, so the share depends on how you count.
- Tip too low. Other bundles for the same accounts outbid yours.
- A transaction would fail. Slippage exceeded, a wallet short of SOL, an account already created. One failing transaction drops all five.
- Expired blockhash. A transaction is valid for about 150 blocks, roughly a minute. If signing several wallets takes too long, the bundle is dead on arrival.
- Rate limits. Above 1 request per second per IP per region, requests are rejected.
Jito is also explicit that sending is not landing: sendBundle "does not guarantee the bundle will be processed or land on-chain." Good tools poll the status and retry with a fresh blockhash. Why Solana transactions fail covers the underlying errors.
Are Jito bundles private and fully atomic?
They are private until they land and atomic in normal operation, with one documented exception. Jito says that "if you send to Jito you are never going to be explicitly leaked by Jito," and it shut down its public mempool in March 2024, as CoinDesk reported at the time. Once a bundle lands, though, its transactions are as public as any other.
The exception is uncled blocks: a block built by a leader that the rest of the network doesn't accept. Jito's docs warn that transactions from such a block may be rebroadcast and "will hit the normal banking stage which does not respect the bundle atomicity and reversion protection rules." This is rare, and it is why Jito recommends keeping the tip in the same transaction as the logic it pays for.
Do bundles hide who bought?
No. A bundle changes when and in what order transactions land, not whether people can see them. Every wallet in a bundled launch buys in the coin's first block, and pump.fun's holder list, Solscan and screeners such as RugCheck, Bubblemaps and GMGN show those wallets and flag the bundled share of supply. If you bundle buys for your own team or treasury wallets, say so publicly. Using a bundle to make a token look more widely held or more in demand than it is misleads buyers, and in many places can break market manipulation law.
Bottom line
A Jito bundle is Solana's way to run up to five transactions in order, in one slot, all or nothing, paid for with a tip of at least 1,000 lamports to one of eight tip accounts. On November 5, 2026 the median landed tip was 0.0000172 SOL, so the tip is rarely the expensive part; the real constraints are the five-transaction and 1,232-byte limits, Jito-led slots, and blockhash expiry. Bundles make launches and multi-wallet buys atomic, never invisible.
Questions & answers
How many transactions can a Jito bundle hold?
Five. Jito's low-latency transaction docs describe bundles as 'groups of transactions (max 5)'. Each transaction is still bound by Solana's own size limit, 1,232 bytes for legacy and v0 transactions, which is why a pump.fun bundle launch fits about 16 buyers: one create transaction plus four transactions of three or four buys each.
How much should I tip for a Jito bundle?
At least 1,000 lamports, Jito's enforced minimum. What actually lands varies by minute: Jito's tip floor endpoint showed a 50th percentile of 0.0000172 SOL and a 95th percentile of 0.00057 SOL on November 5, 2026 at 10:32 UTC. For a contested launch block, tips well above the median compete with other bundles; SOLTidy's bundle tools default to 0.001 SOL, which was above the 99th percentile that morning.
Is the Jito tip refunded if the bundle fails?
There is nothing to refund. A bundle that doesn't land never executes, so the tip transfer never happens and no fee is paid. A bundle runs all or nothing, so a tip inside it is only paid when every transaction succeeds. The one exception Jito documents is an uncled block, when transactions can be rebroadcast outside the bundle's rules.
Why is my Jito bundle not landing?
The usual causes are a tip too low for the competition in that slot, a transaction in the bundle that fails simulation (slippage, insufficient SOL), an expired blockhash because signing took too long, the 1 request per second per IP rate limit, or no Jito leader in the slots before the blockhash expired. Check getInflightBundleStatuses for Failed or Invalid, then retry with a fresh blockhash.
Are bundled buys hidden from other traders?
No. Jito says it will not leak bundle contents before they land, but once a bundle lands its transactions are ordinary on-chain transactions. Every wallet that bought in the bundle is visible on explorers, and screeners flag first-block buyers of a new token as bundled.
Do I need a priority fee in a Jito bundle?
Not for ordering within Jito. Jito's docs say that for sendBundle 'only the Jito tip matters'. For single transactions sent through Jito's sendTransaction, Jito recommends splitting about 70% priority fee and 30% tip, because a priority fee also counts with leaders that don't run Jito.
