Skip to content
CCPEDIAby Unity Nodes
Incoming#261 Pull request

Proposal: Canton Carbon Infrastructure

Opened 28-04-2026 by oxymrn, last activity 28d ago

  1. Incoming176 days so far28-04-2026
  2. Needs Championnot reached
  3. In Reviewnot reached
  4. Ready for Votenot reached
  5. Voting Livenot reached
  6. Approvednot reached
Waiting on
Nobody has picked it up
idle 29 days
Discussion
1 message
1 person

Development Fund Proposal Submission

Proposal file:
/proposals/proposal-canton-carbon-infrastructure.md


Summary

This proposal defines a Canton-native infrastructure layer for carbon markets, including a standard for representing carbon credits as on-ledger assets, a registry integration framework, a verifiable retirement mechanism, and reference workflows for asset access and price discovery.

It establishes the foundational primitives required for institutional carbon market activity on Canton, enabling ecosystem participants to build applications, workflows, and financial integrations on top.


Checklist

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

Notes for Reviewers

  • This proposal focuses on foundational infrastructure, not a full application layer
  • Designed as a reusable reference implementation for ecosystem participants
  • Registry integration will be delivered with at least one partner during the pilot phase
  • The reference marketplace is intentionally minimal, rather than introducing new trading primitives
  • Open-source components will include the carbon asset standard, retirement framework, and reference implementations. Registry-specific integrations and production systems will remain proprietary where required by partner agreements.
  • The proposing team brings production experience from onchain carbon market infrastructure, including registry integrations and prior deployments on Base and Polygon
  • The team has existing relationships with Canton ecosystem participants, including validator operators, and will leverage these during implementation and testing
  • Author contact: Alex, Carbonmark -- alex@carbonmark.com