Searchers send bundles straight to Jito's BAM
An early cohort sends bundles straight to Jito BAM. The block engine hop drops out. DBI is paused during Alpenglow maintenance.
Straight into the BAM nodes
On 13 October, Jito introduced Direct Bundle Ingest, DBI, in an article on X. An early cohort of searchers has been sending bundles straight to nodes of the Block Assembly Marketplace, BAM, for about a month. The path is QUIC or JSON-RPC and skips the Jito Block Engine.
A bundle holds up to five transactions and counts only as a whole. If one fails, the whole bundle reverts. BAM checks these bundles and hands them to the validator that is building the block.
The hop bundles used to take
Since the launch in September 2025, the block engine authenticated, simulated, and filtered bundles before BAM saw them. BAM nodes then ordered them inside a block and sent them to BAM validators. Jito says that extra hop took about 50 milliseconds and left BAM’s improved filtering and simulation unused.
With DBI, checking starts at the BAM node. Jito lays the path out as follows:
- A searcher submits a bundle of at most five transactions to a BAM node. QUIC authenticates with an Ed25519 keypair. JSON-RPC authenticates with a UUID.
- The node checks the signature on every transaction.
- It simulates the bundle. The bundle moves on only when every transaction succeeds.
- An auction that knows the current leader ranks bundles by total fees per requested compute unit. Those fees are priority fees plus Jito tips.
- Winners go to the current BAM leader as one batch.
- If any transaction fails there, the whole bundle reverts.
Jito also lists pre-execution privacy, revert protection, and static tips. Authenticated bundles and sendTransaction traffic still arrive at the block engine. From there they are forwarded through DBI.
On that path the block engine auction drops out. Jito puts it at about 50 milliseconds.
Access is a whitelist. Searchers and apps request it on a form. Jito says they can send as soon as they are on the list.
Questions go to the Jito Developer Discord. The low-latency send guide still documents sendBundle to the block engine.
Jito’s figures for the first weeks
Jito compares two windows of about two and a half weeks each. One runs from 3 to 20 September. The other runs from 20 September to 7 October.
Jito leaves out epoch 1052, because it was still running when the article was written. The figures describe the first weeks of the new path. Only the early cohort was sending directly.
Jito gives the figures as follows:
| Metric | 3–20 September | 20 September–7 October | Change |
|---|---|---|---|
| Unique bundles received | 23.76 billion | 21.97 billion | −7.5% |
| Landed bundles | 106.3 million | 124.3 million | +16.9% |
| End-to-end land rate | 0.45% | 0.57% | +26.7% |
| Simulation success | 11.43% | 16.14% | +41.2% |
| Median fee per CU consumed | 1.80 lamports/CU | 2.76 lamports/CU | +53.4% |
| Average reward per landed bundle | 0.000134 SOL | 0.000231 SOL | +72.4% |
| Total landed bundle tips | 14,279 SOL | 28,765 SOL | +101.5% |
Jito says auction success rose from 3.4 percent to 4.7 percent. The share of compute spent on failed simulations fell from 50 percent to 41 percent.
Note: This is reporting, not investment advice.
Off during Alpenglow maintenance
For the Alpenglow activation, Jito plans to put every mainnet BAM node into maintenance mode. That is in the 5 October blog and the 9 October changelog on bam.dev. During that window, Jito pauses DBI and the Maker Priority Plugin.
Block engine bundles keep working. DBI users are told to use the previous block engine path. A validator connected to BAM falls back to ordinary Jito-Agave block engine mode.
After activation, the nodes come back gradually. Jito says the timing of the maintenance will be announced on Discord.
Anza and the Solana Foundation plan Alpenglow for 21 October, at the start of epoch 1064. That date is in the mainnet report.
What to watch
- When BAM nodes enter maintenance, and when DBI is available again
- Whether the land rate and tips hold once more than the early cohort sends directly
- Whether Jito sets a date for a full switch from the block engine to DBI
Sources
- Jito — Post, 13 October 2026, 10:20 p.m. Berlin · Article, “Introducing: BAM’s Direct Bundle Ingest”
- BAM — Blog, 5 October 2026 · Changelog, 9 October 2026
- Jito docs — Low Latency Transaction Send, read 14 October 2026
- Access — Whitelist form · Jito Developer Discord
- SOLANA·HUB — Alpenglow on 21 October