Skip to content

Proposal: CIP-56/ERC-20 Middleware

CLOSEDPull Request
by Eunoia-cym09-06-2026Declined
needs-sig-labelneeds-champion
References:CIP-0056CIP-0112

Development Fund Proposal Submission

Proposal file: /proposals/2026-06-Eunoia-cip56-erc20-middleware.md

---

Summary

MetaMask-compatible middleware exposing an Ethereum JSON-RPC facade over CIP-56 token contracts, plus a distributed indexer and an Ethereum↔Canton bridge relayer. Any EVM wallet, dapp, explorer, or indexer can transact against Canton-native tokens through the RPC surface it already uses, while Canton's privacy and finality guarantees are preserved. Phase 2 adds fully non-custodial signing via a MetaMask Snap plus an institutional custody path; all deliverables are Apache 2.0 open source.

---

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

  • Submitted by Eunoia Limited (the "Applicant") with its technical partner Chainsafe Systems Inc. As an external team we currently need a Champion per the submission requirements — guidance from the committee or SIG directory on Champion matching is welcome.
  • Includes a CIP-112 (Token Standard V2) migration plan with per-layer code-reuse estimates and a contingency clause for mid-Phase-2 ratification.
  • Includes an explicit audit policy (independent third-party audits of the MetaMask Snap and the full middleware stack, reports published under docs/audits/) and a post-grant long-term sustainment commitment funded by the Applicant.
  • Total request: 40M CC (Phase 1: 15M, Phase 2: 5M, Maintenance Y1: 10M, Y2: 10M). Project duration > 6 months, so the 6-month CC re-evaluation stipulation applies.