Jito JTO$0.266-2.7%'s BAM (Block Assembly Marketplace) now runs on validators holding more than 40% of Solana SOL$71.27-1.3%'s stake. In a post on 15 November 2026, Jito said 173.6 million SOL across 380 validators is connected to BAM, the system that decides the order of transactions in the blocks those validators produce.
Solana hands out turns to produce blocks roughly in proportion to stake, so BAM now orders transactions in about two of every five blocks. Joining BAM is each validator's choice. According to the BAM site, scheduling runs inside Trusted Execution Environments (TEEs), sealed hardware where "transactions remain private until execution".
Jito says that design "removes transaction supply-chain snooping and mitigates negative MEV", the value bots extract by trading around other users' orders. Jito also issues the JitoSOL liquid staking token and the JTO governance token.
BAM stake share since October: from 37% to over 40%
Jito's previous public count came in its 23 September to 9 October changelog, which put BAM at 164M SOL across 385 validators, or 37% of network stake, at epoch 1050. The 15 November figures add about 9.6M SOL in a little over five weeks, while the number of connected validators fell by five to 380.
Our own staking data lines up with Jito's share. Solana had 430.6M SOL in active stake at epoch 1087 on 15 November, according to Solana Compass validator data, which puts 173.6M SOL at about 40.3%. Jito's post is a point-in-time count, so the match is approximate.
The climb has been steady through 2026. We covered BAM passing a third of stake in Jito's Q2 results and again when BAM preconfirmations went live in September.
What 40% on one block builder means for Solana validators
BAM's 40% describes the software that orders transactions when those validators take their turn as leader; the stake itself stays with each validator and its delegators. On the same epoch 1087 snapshot of our data, 18 validators together hold a third of Solana's stake (the Nakamoto coefficient), and the 10 largest hold 24.8%.
Jito's answer to so much ordering running through one system is to make it checkable and to hand node operation to others. Its attestations design uses cryptographic proofs from the TEEs to show that BAM nodes run unmodified code. As of the 28 September attestations post, encrypted TLS connections were live on all mainnet BAM nodes and the BAM Registry was in internal testnet testing. The remaining steps were the Registry on mainnet, TLS-only validator connections, and public attestations alongside open-sourced scheduling code.
On 2 November, Jito named its first third-party BAM node operators: Triton One, Bitwise and SOL Strategies, saying "Decentralizing block building means BAM Nodes run by operators outside of Jito." We covered the operator cohort and its testnet start at the time. According to SOL Strategies, an early mainnet phase serving only each operator's own validators is expected "before the end of 2026", with full mainnet access for any validator targeted for "early Q1 2027", subject to attestations and other features shipping.
What to watch next for Jito BAM
The October changelog targeted late October for BAM Registry enrollment on mainnet, and the same update set out BAM's plan for the Alpenglow consensus upgrade. Jito's next changelog is the place to check whether the Registry is live, whether third-party nodes have reached mainnet, and where the validator count has moved.
For Solana, the 40% figure means a large share of block production now runs through software built to keep pending transactions out of view until they execute. For background on the design, our Lightspeed summary on BAM covers how Jito first pitched it.
