Proposal: AI Agent Interoperability for Institutions

[YashBit]

Development Fund Proposal Submission

Proposal file:
/proposals/proposal-agentic-ai-interoperability.md

Summary

Defines a Canton-native protocol enabling institutional AI agents to advertise capabilities, establish service relationships, and compose multi-party workflows, inheriting Canton's existing privacy, authorization, and atomicity guarantees. The protocol is implemented entirely at the Daml application layer through three interfaces (Agent Role Contract, Service Request, Service Record) and a two-phase request lifecycle, with adoption directly translating into Canton Coin burn through synchronizer traffic.

Checklist

Proposal file added under /proposals/
Milestones and funding amounts defined
Acceptance criteria included
Alignment with Canton priorities described
Notes for Reviewers

Funding structure is performance-indexed. Milestones 1–3 are fixed (5M CC) and tied to verifiable on-chain and code-level deliverables. Milestone 4 (20M CC) releases in 1M CC tranches per $10M USD of cumulative attributable burn through the standard's contracts, capped at 20 tranches. An Adoption Bonus (25M CC at $1B burn, or 50M CC at $10B burn) sits on top.
Backwards compatible. No changes to the Canton protocol, synchronization domain software, or existing Daml models. Implementable entirely at the application layer.
Dependency: CIP-56 (Canton Coin fee denomination in Terms of Service).

[github-actions]

SIG labels auto-detected and applied: financial-workflows-composability

If this is incorrect, you can ask the reviewers to update the labels.

[github-actions]

@YashBit, thank you for your interest in the Canton Development Fund!

Your proposal needs a valid Tech & Ops Committee champion organization. The champion field is either empty, contains placeholder text, or names an organization that is not a current Tech & Ops Committee member.

Per CIP-0100, all external proposals require a Tech & Ops Committee champion.

Next steps:

1. Identify a Tech & Ops Committee member organization willing to champion your proposal
2. Update the Champion field with their name
3. Reopen this PR

If you need help finding a champion, reach out to SIGs or any Tech & Ops Committee member.

This PR is being closed automatically. You are welcome to reopen it once a champion is confirmed.

[YashBit]

@srikanth-bitdynamics was added as the Champion earlier.

[YashBit]

Hi @srikanth-bitdynamics,

Hope you are doing well. We still have the needs-champion tag. How shall we go about confirming it?

Best,
Yash.