OpenZeppelin Canton Ecosystem Stack #262 - Milestone 8: Final Reference Implementation, Year 2 Adoption

OPENIssue
by pedrodneves16-07-2026
9.9M CC requested
View on GitHub ↗← All Proposals

Milestone 8: Final Reference Implementation, Year 2 Adoption

| Field | Value | | :---- | :---- | | Estimated Delivery | Quarter 8: February to April 2028 (End of Year 2\) | | Focus | Final Reference Implementation, remaining audits, and Year 2 adoption proof |

Reference Implementations:

  • Reference Implementation 8 (use case defined during 12-Month Scope Review): Working reference code, architecture documentation, demo front-end, and threat model.

Contracts Library:

  • Additional Canton Standards (to be determined per Year 2 roadmap)

Security:

  • Security audits of Milestone 7 deliverables (audit report published)
  • Security reviews and penetration tests
  • Final security audit and documentation polish across the full library and RI codebase
  • Continuous coverage and AI-Security Agent

Developer Enablement (included):

  • Marketing and community activations
  • Dedicated Technical Account Manager
  • Leadership meeting

Delivery Acceptance Criteria:

  • RI 8 demonstrable on LocalNet/DevNet with functional demo front-end.
  • M7 security audit report published with all critical and high findings resolved.
  • Full library documentation is complete, current, and published on OpenZeppelin Documentation.
  • All library code and Reference Implementation code is publicly available under MIT license. All OpenZeppelin tooling code is publicly available under AGPL 3.0 license.

Adoption Criteria (Year 2):

The Canton Foundation and Digital Asset will continue to facilitate introductions to new and existing ecosystem teams throughout Year 2\.

  • At least 17 additional independent Canton projects (20 cumulative) have imported or integrated OpenZeppelin Contracts Library components, confirmed via written attestations or verifiable on-chain/repository evidence.
  • At least 8 external adoption events across the Reference Implementation portfolio, where a fork, deployment, or use as a foundation by an external team each count as one event, confirmed via public repository evidence or written attestations. Events may be distributed unevenly across RIs, reflecting that some use cases attract broader adoption than others.
  • Published Year 2 Adoption Report documenting cumulative usage, ecosystem feedback, and measurable impact.

| Milestone | Reference Implementations | Contracts Library | Security | Dev Enablement | Subtotal | % of Total | Trigger | | :---- | :---- | :---- | :---- | :---- | :---: | :---: | :---- | | M8 (Q8, End Y2) | RI 8 (TBD) | Additional Standards | Audits, Reviews, Pen Tests | Included | 9,932,433 CC | 5%(Delivery)<br>30% (Adoption) | Committee acceptance AND adoption criteria |

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