Skip to content
CCPEDIAby Unity Nodes
Approved#750 Pull requestDigital Asset

[Amendment] ISS-Based BFT #53 M4: Automatic Pruning & Operational Maturity

Opened 31-08-2026 by guillaumedejenlis-da, last activity 1mo ago

  1. Incoming0 days31-08-2026
  2. Declined0.6 days31-08-2026
  3. Ready for Vote1.7 days01-09-2026
  4. Voting Live14 days02-09-2026
  5. Approvedsince 16-09-2026
Organization
Digital Asset
Discussion
5 messages
3 people

Digital Asset requests a scope change to continue work on Grant #53. At the time of the grant writing, pruning was managed manually by each SV. At the current time, the 30 days pruning window is sufficient for SVs and there is no need to make additional improvements to data pruning.

Therefore, we have taken the decision to descope this feature and allow for additional performance improvements allowing stable and fast deployment of the BFT including:

  • Performance and stability improvements, especially for networks with heterogenous load and latency
  • Nodes fetch batch data proactively and simultaneously from multiple peers to reduce delivery and ordering latency
  • Improved peer connection management to avoid requesting data from nodes that recently timed out or became disconnected
  • Nodes flush remaining segment blocks if a sufficient number of peers have already finished their own respective segments
  • Nodes use a dynamic view change timeout to increase the allotted time for new leaders (in views > 0) to successfully order blocks
  • Reduced memory footprint of expensive view changes: unnecessary messages are removed from memory, and across restarts, nodes load only the precise messages needed for rehydration
  • Exponential backoff variant of leader blacklisting to more quickly restore long periods of fast ordering when a failed leader experiences a persistent problem
  • Holistic database partitioning scheme to improve the performance and efficiency of periodic pruning. And in general, improved the efficiency of many database queries to use indexes and avoid sequential scans.
  • Enhanced the dynamic sequencing parameters to enable network-wide consistency of additional important properties, including view change settings, leader blacklisting heuristics, and maximum batch sizes for blocks

Milestones 5

  1. Core Primitives – Mempool, Availability & PersistenceMonth 2 (May 2026 if approved in March)
  2. Parallel Ordering & BFT TimestampingMonth 3 (June 2026 if approved in March)
  3. Governance, Security & Production ReadinessMonth 4 (July 2026 if approved in March)
  4. Performance & StabilityMonth 5 (August 2026 if approved in March)
  5. Successful Deployment on Global Synchronizer MainNetMonth 8 (November 2026 if approved in March)