Jito Bundles Explained: Solana Routing and Limits
**Answer first** - A Jito bundle is a group of up to five signed Solana transactions submitted to the Jito Block Engine. If selected, the transactions execute sequentially and atom
Answer first - A Jito bundle is a group of up to five signed Solana transactions submitted to the Jito Block Engine. If selected, the transactions execute sequentially and atomically within one slot. A successful submission response only confirms receipt: it does not prove that the bundle landed. Operators must query status, verify signatures, and reconcile both Solana fees and the Jito tip.
Jito bundles in one table
| Property | Documented behavior | Operational consequence |
|---|---|---|
| Size | Up to five signed transactions | Keep the sequence small and deterministic |
| Ordering | Transactions execute in listed order | Order dependencies explicitly |
| Atomicity | All transactions succeed or none are committed | One failing transaction rejects the bundle |
| Scope | Execution occurs within one slot | A bundle cannot span slots |
| Selection | Bundles compete in an auction | A valid bundle may still not be selected |
| Receipt | The API can return a bundle ID | Query status; receipt is not landing |
Jito''s model should not be described as identical to an Ethereum bundle. The networks, auctions, fee models, and confirmation rules differ.
Submission lifecycle
1. Construct
Build and sign every transaction before submission. Validate account permissions, recent blockhash handling, compute budgets, token accounts, and state assertions.
2. Simulate
Simulation should use the same instructions, account set, and fee assumptions intended for submission. A successful simulation is a validation result for a referenced state, not a forecast of landing or outcome.
3. Add the tip and fee policy
Jito requires a tip for a bundle to be considered. Solana also has a base fee and an optional prioritization fee. These are separate costs and should be capped independently.
Avoid publishing a universal "competitive tip." Demand changes, and a number without a timestamped sample and method quickly becomes misleading.
4. Submit
Send the fully signed transactions to the documented bundle endpoint. Store the request time, region, blockhash, signatures, tip account, tip amount, and returned bundle ID.
5. Verify
Query the bundle status, then verify the transaction signatures on-chain at the commitment level selected by the operator. Reconcile:
- whether the bundle landed;
- the slot and signatures;
- base and priority fees;
- the Jito tip;
- any expired or rejected attempt;
- any fallback route that changed the original privacy assumptions.
What atomicity does and does not mean
Atomicity means the listed transactions are committed together if the bundle executes successfully. It does not mean:
- the bundle will be selected;
- the state used during construction remains unchanged;
- the resulting trade is profitable;
- a separate future transaction is protected;
- a stop-loss instruction exists or can execute later.
A risk control must be technically present in the submitted transaction sequence. Marketing language cannot create that control.
Common failure categories
| Category | Example | Response |
|---|---|---|
| Construction | Invalid signature or account list | Rebuild and re-simulate |
| State | Blockhash expired or account state changed | Refresh state and invalidate stale assumptions |
| Execution | A transaction in the sequence fails | Inspect logs and reject the whole candidate |
| Auction | Tip is insufficient for current competition | Respect the configured cap; do not chase automatically |
| Confirmation | Receipt exists but no landing is observed | Query status and record the attempt as not landed |
| Fallback | A direct send replaces the bundle route | Re-evaluate visibility and atomicity assumptions |
Jito and FRB Agent
FRB Agent is a non-custodial Windows execution assistant. Signing keys remain under the user''s local control. FRB can support a configured bundle workflow, but Jito remains the external submission infrastructure and its current documentation defines the route''s behavior.
Start with Simulation Mode, review Private Bundles, and keep a restricted wallet and hard fee limits for any controlled test.
FAQ
Does a bundle ID mean the transactions landed?
No. Jito states that a returned bundle ID does not guarantee processing or on-chain landing.
Are Jito tips the same as Solana priority fees?
No. The Jito tip participates in the bundle auction. Solana base and priority fees are separate network fee components.
Are Jito bundles invisible forever?
No. Landed transactions become on-chain data. Avoid absolute claims about privacy; use the provider''s current routing documentation.
Primary sources
Related Articles
Further reading & tools
Discussion
No notes yet. Add the first observation, or share the link with your team on X (@MCFRB).