This commit submits the Protocol Development Grant proposal for the Canton Gamified Progression SDK. This open-source reference implementation bridges off-chain Web2 databases with Canton's on-chain state, allowing applications to securely log user progression through "ownerless" records before a user even creates a crypto wallet.
The system is inherently extensible, built to seamlessly transition from gaming progression into a Universal Credentialing Bridge (W3C VCs) for enterprise and financial institutions.
The proposal includes a Mainnet case study integrating Tap Ants to port 50,000 active Web2 gamers on-chain, with a total funding ask of 742,000 CC distributed across 5 technical and deployment milestones.
Development Fund Proposal Submission
Proposal file: /proposals/canton-gamified-progression-sdk.md
---
Summary
This open-source reference implementation bridges off-chain Web2 databases with Canton's on-chain state, allowing applications to securely log user progression through "ownerless" records before a user even creates a crypto wallet. By delaying the wallet creation hurdle until after the user has accrued value, it drastically lowers the barrier to Web3 entry while acting as a Universal Credentialing Bridge (W3C VCs) for the ecosystem.
---
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
A few key highlights for the Tech & Ops Committee:
- Internal Champion: We have been collaborating closely with Five North, and Vinh Nguyen (CTO) has graciously agreed to act as the internal reference/champion for this PR.
- Architecture & CIP-0047: The system utilizes a Daml Propose-Accept pattern (
ClaimCoupon) and a Node.js batcher using the Direct Canton Ledger API. - Live Mainnet Case Study: Milestone 5 includes a live deployment integrating Tap Ants to port 50,000 active Web2 gamers on-chain to demonstrate immediate network value.
- Funding: We have opted to bypass a traditional Solidity-style 3rd-party audit, redirecting those funds to Node.js middleware hardening and relying on collaborative peer review with the Committee and our node operator.
