WTF is BAM?

BAM (Blockspace Assembly Markets) is a next-generation transaction scheduling system for Solana that separates transaction ordering from validation. Validators delegate scheduling decisions to specialized external BAM nodes running in secure hardware (TEEs).

BAM nodes operate within AMD SEV-SNP Trusted Execution Environments to ensure transaction privacy and prevent front-running. They receive transactions via QUIC and Block Engine, perform optimal (non-exploitative) scheduling, and forward ordered microblocks to validators for execution.

Validators maintain three operational modes: Normal Agave (standard Solana), Block-Engine (current Jito MEV), and BAM mode. In BAM mode, validators execute transactions in strict FIFO order without reordering.

This architecture enables verifiable, private transaction sequencing while maintaining Solana's security guarantees and allowing validators to dynamically switch between scheduling modes via admin RPC.

Technical Diagram

BAM Technical Architecture - Transaction flow from User through RPC/Block Engine to BAM Node (TEE) to Validator to Block

Key Benefits

→Privacy-Preserving: TEE hardware ensures transaction content remains private during scheduling
→Verifiable Scheduling: Cryptographic attestations prove honest execution within secure enclaves
→Flexible Operation: Validators can dynamically switch between Normal, Block-Engine, and BAM modes