Scalability, Performance and Robustness #187 Milestone 5: Node Counterparties (NC)

Milestone 5: _Node Counterparties (NC)_

• Focus: The core architectural target principle of Canton is network scalability, so that any resource contention can be scaled away elastically by adding more validators or synchronizers and sharding the workflow across the available infrastructure. As there is no global state to store, each node needs only to store the subset of data it is privy to, theoretically reducing the storage footprint. This milestone ensures that the network can support locally dense relationship graphs between nodes where single validator nodes have large sets of counterparties. The SV validator nodes hosting the DSO party are a good example, as they have relationships with all network validators and most active wallets. This requires investing in the vertical scalability of a single validator node and the Scan backend to preserve operability with large contract sets and a large number of counterparties.
• Estimated Delivery:

- NC1: 1M direct holders: no later than Sept 1st, 2026 - NC2: 5M direct holders: no later than Dec 1st, 2026

• Deliverables / Value Metrics:

- Both target numbers validated in CILR.

| Milestone | Code | Payment | Acceptance / Trigger | |-----------|------|---------|----------------------| | 5 | NC1 | 1,240,000 CC | Upon final release and acceptance | | 5 | NC2 | 940,000 CC | Upon final release and acceptance |

_Originally posted by @pedrodneves in https://github.com/canton-foundation/canton-dev-fund/issues/187#issuecomment-4350406156_