​

Release of Canton 3.5.12

​

Summary

​

What’s New

​

Traffic Enforcement App

• This release reworks and improves the way local traffic accounts on the participant are updated. In particular the par_traffic_enforcement_event is dropped and re-created from scratch. Events were never exposed through the API so this will only affect users who have been accessing the database directly. Importantly, the traffic balances are not affected by this change and account balance continuity is preserved, and the API for querying traffic balances remains unchanged.
• Various bug fixes in the in-memory implementation of the traffic accounting

​

CantonBFT Improvements

• Upon completing the locally-led segment in an epoch, CantonBFT nodes now dynamically increase the rate of retransmission requests to decrease the time it takes to retrieve any missing messages from other peers’ segments.
• Added a new metric relative-segment-latency that records the rate and latency it takes to complete a segment after the segment led by this node completed.
• Lower log level of dissemination: some batch dissemination logs in CantonBFT were logged at WARN level, which is too high because they don’t imply abnormal conditions nor non-compliant behavior. This change lowers their log level to INFO.

​

Bugfixes

​

(26-005, Critical): LSU: Cancelled LSU leftover state prevents PN startup after a successful LSU

​

Issue Description

​

Affected Deployments

​

Affected Versions

​

Impact

​

Symptom

​

Workaround

update par_synchronizer_connection_configs
set
  status = 'I'
where
  physical_synchronizer_id = 'global-domain::1220be58c29e65de40bf273be1dc2b266d43a9a002ea5b18955aeef7aac881bb471a::35-4';

​

Likeliness

​

Recommendation

​

Compatibility