Solana’s Block Building Battle: Jito BAM vs. Harmonic

This episode decodes Solana's fractured block-building landscape, urgent MCP timelines, and how protocol sequencing can restore market structure and composability.

Key Takeaways

MCP urgency: AlpenGlow targets August; MCP expected 6–12 months later (12–18 months total). Solana must prioritize deployment to avoid losing market leadership.
Fragmented block building harms markets: inconsistent packing and end-of-slot cramming enable frontrunning, widen spreads, and block perps from achieving tight execution.
BAM vs Harmonic: JITO's BAM (TEE-based, closing to open-source) and Harmonic compete on packing strategies; in-protocol MCP could displace third-party business models.
Protocol fixes proposed: attestation aggregation, consistent merge/dedupe and ordering rules, and application-controlled execution (ACE) to standardize sequencing and reduce market friction.
Fees and infrastructure: base, priority, and out-of-protocol tips plus multiple TPUs complicate onboarding; MCP aims to simplify the stack and capture value natively.
Action for teams: collaborate now to adapt business models, test integrations, and prepare for MCP; report and Solana Lightspeed resources will publish deeper analysis.

Original Source

Visit Source