Digital Asset has released Canton 3.5.13, a maintenance update focused on how nodes handle missing batches and connectivity issues during consensus.
The update focuses on CantonBFT and the Traffic Enforcement App. When a node is contributing to consensus but has not received a batch, it can now consider a broader set of potential sources, begin retrieving earlier, and request the batch from several nodes in parallel. According to the release notes, this improves the chances of successful dissemination and can improve ordering latency for nodes experiencing connectivity issues.
Canton 3.5.13 also deletes unnecessary messages from previous views during a view change, helping prevent excessive memory use. CantonBFT’s P2P server-side now has configurable keepalive settings, with defaults made more robust when infrastructure drops idle connections without closing them cleanly. The release adds more detailed logging around view changes, including why a change occurred and which node became the new leader.
For participant operators, the update introduces optional Traffic Enforcement App settings covering multi-party submissions, periods when an account balance cannot be determined, and time limits for database and account lookups. The two new submission-behaviour controls are disabled by default.
The release also addresses a case in which an unsupported future contract-ID version could cause the engine to crash. It now returns an interpretation error instead. Canton 3.5.13 supports protocol versions 34 and 35.
