Cardano’s node team has released version 11.1.3, a patch that corrects a subtle IPv4 decoding bug that surfaced in the 11.1.x series. Earlier releases had inadvertently switched from network‑order decoding to a different byte order, which could have led to misinterpretation of IPv4 addresses in the ledger. The new release restores the original network‑order logic, ensuring that IPv4 addresses are parsed consistently across the network.
Beyond the bug fix, the release notes highlight a small increase in memory consumption during node synchronization compared to the 11.0.1 baseline. The team notes that this increase is significantly lower than the regression observed in 11.1.0, and that the memory usage spike on the tip is linked to ledger snapshot operations. Full benchmark details are available in the linked reports.
Developers and operators should also note a breaking change in the plutus‑ledger‑api: the plc optimise command no longer accepts the --certify and --certifier- options. This adjustment may require updates to existing build scripts that rely on these flags.
Benchmarking reports for 11.1.3 are not affected by the node version; the relevant performance data remains those published for 11.1.1. System testing results for 11.1.1 are also applicable to 11.1.3, and can be reviewed on the corresponding tag testing page.
The release includes updated minimum system requirements: an Intel or AMD x86 processor with two or more cores at 1.6 GHz (2 GHz for stake pools or relays), 24 GB of RAM for InMemory back‑ends (8 GB for OnDisk), and 300 GB of free storage (350 GB recommended). Supported platforms cover Linux 64‑bit (Ubuntu, Mint, Debian LTS releases), Windows 64‑bit, and macOS from 10.15 to 15.
For stake pool operators and developers, the 11.1.3 update brings a critical fix, modest performance tweaks, and a clear path forward for building and maintaining compliant nodes. Keeping node software up to date remains essential for network stability and security.