Contract Keys #75 Milestone 4: Multi-synchronizer contract key optimizations are deployed and used by a dApp on MainNet

Milestone 4: Multi-synchronizer contract key optimizations are deployed and used by a dApp on MainNet

Objective: Validate contract key functionality for multi-synchronizer dApps and that they perform well enough for general use across synchronizers.

Estimated Delivery: Month 12 after approval

Deliverables:

• Contract keys support multi-synchronizer applications
• Participant node database layer batching for contract key requests
• A caching layer for the most recent contracts that match a key.

Acceptance criteria:

• A multi-synchronizer dApp or reference application is live on TestNet.
• Using micro-benchmarks, the before and after throughput of the following optimizations are measured:

The addition of node local caching to utilize batching to the database; Adding the caching layer for the most recent contracts that match a key.

• Delivery of a finalized security audit report from an independent, reputable Web3 security firm covering the Contract Key feature.All findings classified as "Critical" or "High" must have a verifiable patch merged into the main branch.

| Milestone | Earliest delivery | CC | | ----- | :---: | ----- | | Milestone 4: Multi-synchronizer contract key optimizations are deployed and used by a dApp on MainNet | Month 12 | 1.9 M |

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