Skip to content
CCPEDIAby Unity Nodes
Incoming#600 Pull request

Proposal: Open-Source MiCA EMT Issuance Framework for Canton

Opened 27-07-2026 by SchumanFinancial, last activity 19d ago

  1. Incoming91 days so far27-07-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 19 days
Champion named in file
W. Eric Saraniecki, Co-Founder & Head of Network Strategy, Digital Asset
Discussion
7 messages
2 people

Development Fund Proposal Submission

Proposal file:
/proposals/2026-07-Schuman-open-source-mica-emt-framework.md


Summary

Schuman Financial proposes to develop an open-source MiCA EMT issuance framework for Canton. The framework provides reusable Daml, operational, reporting and integration foundations for regulated fiat-backed stablecoin issuance, with EURØP expected as the first intended implementation.

The proposal maps primarily to the Dev Fund 2.0 RFP category RWA Standards — Daml and Institutional RWA Workflow Standards, and secondarily to Payments and DeFi.


Checklist

  • Proposal file added under /proposals/
  • Milestones and funding amounts defined
  • Acceptance criteria included
  • Alignment with Canton priorities described
  • Dev Fund 2.0 RFP category added
  • Ecosystem need and adoption impact added

Notes for Reviewers

This proposal is intended to provide an issuer-neutral framework for EMT-style fiat stablecoins on Canton. It is designed to support regulated issuance, redemption, issuer controls, holder eligibility, reporting, regulator/auditor visibility, deployment guidance and issuer-platform integration.

The direct ecosystem value is a reusable foundation for regulated fiat-backed settlement assets on Canton, supporting tokenized assets, institutional settlement, collateral mobility, treasury flows, payments and related workflows.

Milestones 4

  1. Specification and architecture30 days after approval
  2. Smart contract implementation60 days after approval
  3. Reporting, deployment, and integration layer90 days after approval
  4. Audit and final release180 days after approval