What Is Lil' JIT?
Lil' JIT is a Quicknode add-on that brings Jito bundle support to your Solana endpoint. It lets you submit up to five transactions that execute atomically and in order inside one slot, check whether they landed, and read current tip levels, all through the JSON-RPC endpoint you already use.
Bundles go to the Jito block engine, which forwards them to the next Jito-Solana leader. Quicknode runs that connection, so you do not stand up searcher infrastructure or manage a separate block engine URL.
The add-on covers three areas:
- Send bundles and transactions: Submit a bundle, route a single transaction through Jito, or simulate before you pay.
- Track bundle status: Check whether a bundle landed, or poll one that is still in flight.
- Look up tips and regions: Fetch tip accounts, current tip percentiles, and available routing regions.
What Is a Jito Bundle?
A Jito bundle is a list of up to five signed transactions that execute atomically, in the order you supply, within the same slot. If one transaction fails, none of them commit. sendBundle returns a bundle_id right away, which confirms that Jito received the bundle rather than confirming it landed onchain.
Why Send a Bundle Instead of a Single Transaction?
A bundle gives you two guarantees that separate transactions cannot provide: every transaction lands together or none of them do, and they land in the exact sequence you specify. Sending the same transactions individually leaves you exposed to one landing while another fails, or to them landing out of order.
That matters when the steps only make sense as a unit. An arbitrage trade and the leg that closes it, a liquidation and the swap that settles it, or a multi-step position adjustment all break badly if half of the sequence executes.
Bundles also travel to the block engine rather than through the normal forwarding path, which narrows the window in which another party can observe your transactions and act ahead of them.
How Do Bundle Tips Work?
A bundle competes for inclusion by paying a tip. The tip is a SOL transfer to one of eight Jito tip accounts, and it can sit in any instruction of any transaction in the bundle. Jito selects bundles by tip, so a bundle that tips below the going rate may never land.
Two methods size and place that tip:
getTipAccountsreturns the eight tip accounts. Pick one at random per bundle, since every bundle tipping the same account creates write-lock contention on it.getTipFloorreturns recent landed-tip levels at the 25th, 50th, 75th, 95th, and 99th percentiles, plus an exponential moving average of the 50th. Size against the percentile that matches how badly you need the slot.
Note: The tip is separate from the priority fee. A bundle still pays normal Solana transaction fees on top of whatever it tips.
How to Access Lil' JIT
Once enabled, these methods are available on your existing Solana endpoint URL. You call them like any other JSON-RPC method, with no separate hostname or API key.
Lil' JIT Methods
Send Bundles and Transactions
| Method | Description | Use It For |
|---|---|---|
sendBundle | Submits up to five fully-signed transactions for atomic execution and returns a bundle_id | Operations that must land together and in order |
sendTransaction | Forwards a single transaction through Jito and submits it as a one-transaction bundle | Routing a normal send through Jito without building a bundle |
simulateBundle | Simulates a bundle and returns account state before and after execution | Checking bundle logic before paying a tip |
Track Bundle Status
A bundle_id confirms receipt, not inclusion. Use these methods to find out what actually happened to it.
| Method | Description | Use It For |
|---|---|---|
getBundleStatuses | Returns the status of up to five bundles by bundle_id, including the slot and confirmation status of each transaction | Confirming a bundle landed |
getInflightBundleStatuses | Returns the status of up to five bundles submitted within the last five minutes | Polling a bundle that has not settled yet |
Note: getBundleStatuses returns null for a bundle it cannot find, which covers both a bundle that never landed and one that is still in flight. Check getInflightBundleStatuses first for anything submitted in the last five minutes.
Look Up Tips and Regions
| Method | Description | Use It For |
|---|---|---|
getTipAccounts | Returns the eight accounts designated to receive bundle tips | Selecting a tip account at random |
getTipFloor | Returns landed-tip percentiles from recent slots plus a 50th-percentile moving average | Sizing a tip that clears the current floor |
getRegions | Returns the regions available for routing Jito requests | Confirming the current region list |
Regional Routing
Most Lil' JIT methods take an optional region parameter that controls which block engine handles the request. It defaults to mainnet. Set it explicitly to route through the location closest to your infrastructure.
| Region Value | Location |
|---|---|
mainnet | Default when no region is set |
amsterdam | Amsterdam, Netherlands |
frankfurt | Frankfurt, Germany |
london | London, United Kingdom |
ny | New York, United States |
slc | Salt Lake City, United States |
singapore | Singapore |
tokyo | Tokyo, Japan |
Call getRegions to confirm the list, since regions change as Jito adds capacity.