The Cardano community has just received the 11.1.2 update for the cardano‑node, a version that focuses on optimizing memory usage for time lock scripts. While the update does not eliminate all memory overhead, it mitigates the regression seen in 11.1.0 and brings usage closer to the baseline of 11.0.1. Users synchronizing the network will notice a slight increase in memory consumption compared to 11.0.1, but the spike is significantly smaller than the 11.1.0 regression. On the tip, a small rise in memory is also observed, linked to the process of taking ledger snapshots.
Developers should be aware that the 11.1.2 release introduces a number of breaking changes in the cardano‑rpc interface compared to 11.0. These changes affect how clients interact with the node, and the documentation provides guidance on migrating existing RPC calls. Updating client libraries and scripts will be necessary to maintain compatibility.
Performance benchmarks for 11.1.2 are unchanged from the 11.1.1 release, and the detailed reports can be found in the Cardano Updates archive. System testing results for 11.1.1 are fully applicable to 11.1.2, with the testing page for the 11.1.1 tag serving as the reference for validation.
The release notes also outline the minimum system requirements and supported platforms. An Intel or AMD x86 processor with at least two cores at 1.6 GHz (2 GHz for stake pools or relays) is required, along with 24 GB of RAM for the InMemory backend or 8 GB for the OnDisk backend. Storage needs include 300 GB of free space, with 350 GB recommended for future growth. Supported operating systems include Linux 64‑bit (Ubuntu 20.04–26.04, Mint 20–22.2, Debian 11–13), Windows 64‑bit (10, 11), and macOS 10.15–15, 26. The release also specifies GHC 9.6 and Cabal 3.8/3.12 as the supported compiler and package manager versions.
Users can obtain the latest binaries and configuration files through the provided links. Pre‑release configuration files are available on the Cardano documentation site, while Docker images for cardano‑node, cardano‑tracer, and cardano‑submit‑api can be pulled from the IntersectMBO container registry. These resources enable quick deployment and testing of the new node version across different environments.