Proposals:canton sentinel

Development Fund Proposal Submission

Proposal file: proposals/canton-sentinel.md

---

Summary

Canton Sentinel is open-source middleware that connects natural-language intent to enforceable Daml workflows, multi-agent orchestration (Scout, Compliance, Settlement) under Canton’s party-scoped privacy model, and off-chain ZK attestations anchored on-ledger—so institutions can discover liquidity, run complex workflows, and trust agent execution without exposing confidential positions. Grant deliverables are Apache 2.0 primitives (templates, agents, SDK, ZK layer) reusable by any Canton participant or app builder, with a 700,000 CC milestone plan over ~20 weeks.

---

Checklist

• [x] Proposal file added under /proposals/
• [x] Milestones and funding amounts defined
• [x] Acceptance criteria included
• [x] Alignment with Canton priorities described

---

Notes for Reviewers

• Funding structure: 120,000 CC for M1 is requested on grant approval / executed agreement (upfront); M2–M4 (160k + 200k + 220k CC) release after acceptance of each prior milestone (M1 acceptance gates M2 payment per proposal text).
• Scope: Four milestones—M1 Daml intent primitives + NL→JSON parser MVP; M2 Scout + Compliance agents + SDK read path; M3 Settlement + atomic DvP + dashboard alpha + SDK submit path; M4 ZK circuits/prover + GA SDK + Mainnet + third-party security review of templates/circuits.
• Privacy & architecture: Agents use only Ledger API and observer/disclosure-consistent reads; ZK follows off-chain compute → on-ledger attestation (oracle-style), not bypassing sub-transaction privacy.
• Co-investment: Proposer covers OpenAI usage, extra cloud/hosting, and optional pilot costs as stated in the proposal.
• Appendix A: ZK “week” labels are engineering bands inside the ZK roadmap, not extra months beyond the M1–M4 calendar—see Calendar vs. Appendix A in the proposal.