Development Fund Proposal Submission
Proposal file: https://github.com/BlockXAI/canton-dev-fund/blob/canton-streams/proposals/canton_streams.md
---
Summary
GrowStreams is an open-source payment streaming primitive for Canton that makes continuous financial obligations flow the way they actually accrue, instead of settling in monthly batches. It provides Daml smart contract templates, a TypeScript SDK, CIP-103 dApp API integration, and CIP-56 compliant settlement for LP incentive programs, node operator billing, vesting schedules, consortium revenue distribution, and USDCx settlement flows. Unlike previous streaming proposals to this fund, GrowStreams enters the review process with demonstrated demand: 4,300+ participants in our Canton launch campaign in under 24 hours, 7,233 upvotes on the CCTools ecosystem directory, 1,317 registered users, and 66/66 tests passing on Canton 3.4.11 with six institutional use cases live.
---
Checklist
- [x] Proposal file added under
/proposals/ - [x] Milestones and funding amounts defined
- [x] Acceptance criteria included — all binary, all verifiable on-chain without trusting the team
- [x] Alignment with Canton priorities described
---
Notes for Reviewers
Champion: Srikant Label: financial-workflows-composability
We spoke with Melvis (Executive Director, Canton Foundation) and W. Eric Saranlecki (Canton co-founder) before filing. Both shaped this proposal directly.
Melvis told us per-second streaming is probably too aggressive for where Canton is today, and that the bulk of funding should be tied to adoption milestones rather than code delivery. We followed both instructions. This proposal leads with hourly and daily streams as the primary institutional use case. 85% of development funding is gated on active streams on Canton Mainnet.
Shaul-da said in the PR #94 voting thread that he would vote yes if milestones were completely tied to adoption metrics like CC burn. Milestone 3 requires 500,000 CC burned through GrowStreams template IDs by external parties before the primary tranche releases. The performance bonus in Milestone 4 is paid entirely in proportion to on-chain CC burn. That is the structure described.
On the demand question that led to PR #94 being declined: we have answered it upfront. CCTools (the most recently approved Dev Fund project) is our active integration partner. Our joint Canton launch campaign generated 4,300+ participants in 24 hours. The campaign is live and verifiable at https://www.cctools.network/earn/growstreams-x-cctools. Our platform at growstreams.xyz has 1,317 registered users and 3,078 on-chain quest completions. The CCTools ecosystem directory shows 7,233 upvotes and 8,905 views.
The technical proof is in the repository. 66 consecutive test passes on Canton 3.4.11, six working institutional use cases, terminal output in /evidence/. Any committee member can clone the repo and reproduce the results.
We are not connected to PR #94 and not competing with it. We are open to collaboration if the committee considers that useful.
