BAM, short for Block Assembly Marketplace, separates transaction ordering from execution. Its nodes order transactions inside protected hardware environments and send them to Solana’s scheduled leader. Validators execute those transactions and remain responsible for consensus, block production and state management, according to BAM’s technical documentation.
The outside operators will provision hardware, deploy BAM’s software, apply releases, monitor performance and handle incidents. That does not give them unrestricted power to change transaction ordering: Jito says the software runs inside a hardware-isolated confidential virtual machine that prevents even the operator from reading or modifying what runs inside it.
Mainnet Access Comes in Stages
For now, Jito remains the operator of the mainnet BAM Nodes. The new cohort starts with testnet onboarding, followed by an early-mainnet phase expected before the end of 2026. In that second phase, each outside operator’s node will serve only its own BAM validators, allowing connectivity, uptime and performance to be tested before wider access.
The third phase, targeted for early Q1 2027, would open those nodes to any validator wishing to connect. Jito says that step depends on features still in development: attestations, the BAM Verifier and Autobahn.
Attestations let validators verify that a node is running the expected code and hardware configuration, rather than simply trusting its operator, as BAM’s attestation documentation explains. The Verifier checks that validators execute the transactions the node sent in the scheduled order; Autobahn is designed to automatically ban validators for ordering violations.
Jito is coordinating this initial onboarding process. It said it would share the process for additional operators to join, along with the economic model for sustaining node operations, as the cohort moves to mainnet and supporting features go live. The first three operators are joining without an additional economic incentive, according to the roadmap.