protocols
Cardano clears LSM storage for block-producing nodes
Intersect confirmed on November 15 that LSM is supported for block production. Node version 11.2.1 remains a pre-release awaiting approval for mainnet use.

A pre-release recommended on DijkstraNet
In its November 15, 2026 update, Intersect confirmed that LSM storage is supported for block production across Cardano networks. The announcement accompanies node 11.2.1, a pre-release since November 9 and the recommended node on the DijkstraNet test network. Intersect was still awaiting approval of this version for mainnet. Supporting the LSM storage option and recommending the 11.2.1 binary for deployment on mainnet are separate decisions.
Version 11.2.1 fixes memory usage problems seen in the 11.1.x series and improves snapshot creation during synchronization. It also updates three node components, including the Ouroboros consensus layer. The changes concern the software operators install to track the ledger and produce blocks. The update gives no firm date for when mainnet operators should switch to this version.
Less memory used during snapshots
Nodes record ledger snapshots so they can return to a known state. The release notes say that writing a snapshot no longer causes temporary memory usage to rise by about the size of the snapshot. The chain database also stops retaining the genesis ledger state in memory. This can save several hundred mebibytes on networks whose initial state contains large sets of unspent outputs or delegations.
The other change concerns the LSM storage option in UTxO-HD, which manages data on unspent transaction outputs. The release notes say the option meets the expected performance guarantees for producing blocks with Praos, Cardano’s consensus protocol. Intersect presents it as an option for operators with limited resources. It is a node storage choice that can change how much memory the machine needs.
Testing before block production
The maintainers recommend testing LSM in a safe environment before using it on a block producer and allowing at least 8 GB of RAM. System test and benchmarking results are published separately from the release notes. For stake pool operators, those documents can help identify which configuration to try on their own machines before migrating.
The node now advertises version 11.3 in block headers. That number may therefore appear in explorer adoption statistics even though the installed software is version 11.2.1. The status published by the maintainers is still the reference for deciding whether to deploy on mainnet. As of November 15, Intersect still described mainnet approval as a pending step.
