Deep Dive
1. Smart Rollup Snapshot Import Hotfix (11 May 2026)
Overview: This was a standalone hotfix for the smart rollup node, specifically addressing problems that could occur when importing a snapshot of a rollup's state. It ensures node operators can reliably set up or restore rollups.
The release fixes a regression in the "snapshot import" process that was introduced after the previous April update. Key fixes include skipping unnecessary context reconstruction when possible and providing a clear error message if the imported snapshot is too old, suggesting the operator use an archive node. It also adds a new --dal-node option to fetch necessary data when reconstructing compact snapshots and implements automatic retries with exponential backoff for layer 1 RPC calls on startup.
What this means: This is neutral for Tezos because it's a maintenance update. It doesn't add new features for end-users but is crucial for network operators and developers running rollup nodes, ensuring smoother and more reliable operations and faster recovery from issues.
(Source)
2. RISC-V Rollup & DAL Overhaul (April 2026)
Overview: This significant update brought major optimizations to Tezos's scaling infrastructure, making smart rollups faster and more efficient while improving the reliability of the Data Availability Layer (DAL).
For RISC-V rollups, it optimizes how the virtual machine state is handled, avoiding expensive data copies and reducing the number of live states from about 131 to just 4. This drastically improves performance and resource usage. The DAL overhaul changes how the node checks data attestation status, reading it directly from the main Tezos blockchain (layer 1) for greater reliability and adding graceful retry logic.
What this means: This is bullish for Tezos because it directly improves the network's scalability and developer experience. Faster, more efficient rollups mean lower costs and better performance for applications built on Tezos, while a more robust data layer strengthens the foundation for its ecosystem.
(Source)
Conclusion
The latest codebase updates demonstrate Tezos's focused execution on refining its core scaling technology, addressing immediate operational issues while deploying substantial optimizations for long-term performance. How will these under-the-hood improvements translate into increased developer adoption and on-chain activity in the coming months?