Skip to content

Proposal: CIP-56 Utility Token Support for the Canton Wallet SDK

CLOSEDPull Request
by ayushsingh8220-05-2026Declined
needs-sig-labelneeds-champion
References:CIP-0056

Development Fund Proposal Submission

Proposal file: /proposals/canton-token-integration-kit.md

---

Summary

Revised scope after maintainer feedback. Rather than a new TypeScript token library (the official canton-network/wallet SDK already covers transfer/allocation/utxos), this proposal contributes the missing Utility Registry token support upstream to that SDK, specifically generic transfer pre-approval with factory resolution (default vs pre-approval factory) and shared choice-context / disclosed-contract handling for non-Amulet registries, plus a tested reference integration against real registries and completed CIP-56 docs. It is Apache-2.0, with success measured by the contributions merging and independent teams integrating tokens through this path.

---

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

Scope revised following @meiersi-da's note that the wallet SDK and preliminary CIP-56 docs already exist. This proposal extends those resources rather than duplicating them, and targets the Utility Registry token gap raised in the USDCx mailing-list thread (the factoryId pre-approval resolution Sergei Ganebnyi described). It is distinct from #335 (local API/CI test harness) and #231 (on-ledger compliance primitive).

Suggested SIG label: token-asset-standards. Seeking a champion from the Token Standards SIG. cc @meiersi-da