What a bundle is, precisely
Normally a transaction is broadcast and travels a public path toward a leader. A bundle takes a different route: one or more transactions are handed to a block engine as a single unit, along with a tip, and the engine competes to have that unit included.
Two consequences follow from that, and they are the entire product. The unit is not broadcast publicly on the way in, and the transactions inside it either all land together or none of them do.
| Public submission | Bundle | |
|---|---|---|
| Route | Broadcast, then to a leader | Block engine, then to a leader |
| Visible before landing | Yes | No |
| Execution | Each transaction independently | All or nothing |
| Extra cost | None beyond priority fee | A tip you choose |
| Ordering within the group | Not guaranteed | Preserved |
Privacy: the property that matters for sniping
On a thin new pool, the intent to buy is itself valuable information. A transaction sitting in a public path announces both that a buy is coming and roughly how large it is, before the buy has actually happened.
That is uncomfortable in ordinary trading and materially worse on a curve with almost no depth, because a small amount of anticipatory activity moves the price you are about to pay.
What the privacy is and is not
- It is: your transaction not being readable on the way in.
- It is not: anonymity. The trade is on chain afterwards like any other.
- It is not: a guarantee of inclusion. Bundles compete; some lose.
- It is not: a substitute for a priority fee, which still applies to your transactions.
All-or-nothing, and why it helps
The second property is atomicity. If a bundle contains several transactions, they land as a unit in the order given, or the whole unit fails. Nothing lands halfway.
For a single buy this matters less than the privacy does. It becomes valuable when a position needs more than one transaction to be safe: for example setting up and entering together, where landing one without the other would leave you in a state you did not intend.
| Scenario | Public path risk | Bundle behaviour |
|---|---|---|
| Single buy | Fails alone, costs fees | Fails alone, costs the attempt |
| Setup plus buy | Setup lands, buy fails | Both or neither |
| Buy plus protective order | Buy lands unprotected | Both or neither |
| Multi-wallet entry | Partial fill across wallets | Consistent across the group |
The tip is not a priority fee
These are two different payments and conflating them produces bad settings. The priority fee is a price per compute unit that affects ordering within normal processing. The tip is a payment to a block engine for handling your bundle.
You pay both. Raising one does not substitute for the other, and a large tip does not compensate for a priority fee set too low, nor the reverse.
| Priority fee | Jito tip | |
|---|---|---|
| Paid to | The network's fee mechanism | The block engine |
| Affects | Ordering in normal processing | Whether your bundle is taken |
| Set per | Transaction | Bundle |
| Charged when it fails | Yes | Depends on inclusion |
| Sensible default | Adaptive to conditions | Zero, until a launch justifies it |
When to pay and when not to
- 1Pay when the launch is visibly contestedIf many participants are arriving at the same moment, your intent in a public queue is worth the most to them and the least to you.
- 2Pay when the pool is thin relative to your sizeThe thinner the depth, the more a small amount of anticipatory activity moves your fill.
- 3Pay when the entry needs more than one transactionAtomicity is the point here, not privacy. Landing half of a two-part entry is the outcome you are buying protection against.
- 4Do not pay on quiet launchesWith no crowd to hide from, privacy buys nothing and the tip is a straight cost.
- 5Do not pay to compensate for late detectionA bundle cannot recover information that arrived slots late. If detection is the problem, tipping harder is money spent on the wrong stage.
Where this fits in the wider picture
- How fast is a sniper botSubmission is one of four stages, and rarely the slowest
- What a sniper bot costsTips are one of five cost lines, and optional
- Are sniper bots profitableWhy fill rate is the number that decides cost
- The full sniper bot guideDetection, screening, execution and exits end to end
Questions people ask
These come up in the ticket queue often enough to answer once, properly. If yours is not here, send it over and it probably ends up on this page.
A group of transactions submitted to a block engine as a single unit with a tip, instead of being broadcast on the public path. The unit is not visible before it lands and it executes completely or not at all.
Key takeaways
- A bundle is private, atomic submission through a block engine rather than the public path.
- For a sniper the privacy matters more than the atomicity on a single buy.
- Privacy improves fill rate on contested launches; it does not lower latency.
- The tip and the priority fee are separate payments and neither substitutes for the other.
- The sensible default tip is zero, raised deliberately per launch.
- A bundle cannot recover a launch your detection found slots late.