0x2d09b83a2d09…2d09b837
Jito’s BAM Puts a Price on Early Solana Transaction Data
Helius prices BAM preconfirmations at the greater of 300 credits or 10 per message; validators receive 35% of revenue, and BAM reported 39.1% of Solana stake on Nov. 7.
Outputs
Helius charges the greater of 300 credits or 10 credits per delivered message per subscription in a covered slot.
BAM’s early tests measured a median 5–10 millisecond advantage over existing shred streams.
BAM’s stake API reported 39.1% of network stake running BAM at 16:46 UTC on Nov. 7.
The revenue split assigns 35% to BAM validators, 35% to the Jito DAO and 30% to distributors.
BAM announced the service through Helius and Triton on Sept. 9, 2026.
By Tom Whitfield
Helius charges the greater of 300 credits or 10 credits per delivered message for each subscription in a slot with at least one message. These are credit charges, not a stated dollar price per trade, and Helius says pricing remains subject to change.
Helius currently offers preconfirmations on its Developer, Business, Professional and Enterprise plans, excluding free accounts. Zero-message slots and uncovered slots cost nothing.
What does BAM reveal before a shred?
BAM preconfirmations appear only after a Solana leader accepts a scheduled batch and commits to executing its transactions in order. The feed excludes unscheduled pending transactions and reveals committed activity earlier than a shred-based feed, without opening a window to rearrange that batch.
Helius offers two signals by default, and they describe different execution stages. Its own preconfirmations appear when the leader executes a transaction and include local execution status. BAM preconfirmations arrive earlier, when the leader commits to execution, and carry no execution status. Both precede shreds, but neither is equivalent to the other.
A BAM preconfirmation does not establish finality. A leader can still skip its slot or land on a fork, so the signal describes what will execute if the block lands.
How early is the signal?
BAM reported a median, or p50, advantage of 5–10 milliseconds over its distribution partners’ existing shred streams during early testing. BAM cautioned that the result did not guarantee the same lead for every subscriber or transaction.
BAM announced the service on Sept. 9, 2026, through Helius and Triton. CryptoSlate’s July 2025 coverage of BAM concerned the proposed sequencing architecture; the commercial data stream adds a separate question about access.
What does access cost?
Jito does not sell the stream directly. Its distributors handle pricing, billing and onboarding, which separates commercial access terms from the underlying execution commitment.
Helius’s published table makes the schedule concrete: 10 delivered messages cost 300 credits, while 100 messages cost 1,000 credits. Helius bills concurrent subscriptions separately, and the greater-of formula applies within each subscription and slot.
How complete is the coverage?
At 16:46 UTC on Nov. 7, BAM’s public stake API reported that about 39.1% of network stake was running BAM. That figure measures stake participation, not uninterrupted subscriber coverage.
Non-BAM leaders and opted-out BAM validators produce no BAM preconfirmations. Helius warns subscribers to expect gaps, so the reported stake share cannot serve as a proxy for continuous feed availability.
Who receives preconfirmation revenue?
BAM’s published split allocates 35% of preconfirmation revenue to BAM validators, 35% to the Jito DAO and 30% to distributors. BAM distributes the validator portion through eligible leader slots rather than paying only the validator responsible for a particular stream.
BAM describes monthly payments after distributors pay the DAO. The funds come from priority fees attached to market-tick transactions, and skipped or disconnected slots earn nothing. The arrangement gives participation a revenue incentive alongside an execution obligation.
Can validators opt out?
Current validator rules automatically enroll AgaveBAM and FireBAM operators in BAM streaming. They can forgo the revenue and opt out, but self-service controls are not yet available. Operators must currently submit a ticket through the Jito Developers Discord.
BAM says its Verifier checks produced blocks against commitments and can disconnect a validator that deviates. That check links early information to enforcement of the committed sequence; it does not turn a preconfirmation into finality.
What changes for traders?
Traders should compare distributor eligibility, delivered-message charges, actual stream coverage and commitment safeguards rather than treat a fixed place in a batch as an equal signal for everyone. The next market-structure test is whether self-service opt-out controls, broader distribution access and steadier coverage expand BAM’s 39.1% stake base without weakening Verifier enforcement.
via cryptonews.net (Source)
More from Tom Whitfield
Show full bio
News editor covering technology and product news in crypto and web3 industry at Mempool Brief.
695 articles