Development Fund Proposal Submission
Proposal file: /proposals/proposal-cns-v2-native-metadata.md
---
Summary
This proposal funds CNS V2 — the addition of native on-ledger metadata support to Canton Name Service entries. CIP-0056 and CIP-0112 both explicitly rely on a fragile JSON workaround in the description field, and CIP-0056 directly calls for a future CIP to replace it. CNS V2 delivers that fix: a metadata : TextMap Text field on AnsEntry contracts, a by-metadata Scan API discovery endpoint, and a compatibility shim for existing V1 entries — enabling reliable, on-chain-anchored service discovery for wallets, token registries, oracle providers, and dApps across the Canton ecosystem.
---
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
- This is explicitly requested work. CIP-0056 (Final) states the description-field workaround "expects a future CIP to address that limitation." CNS V2 is that CIP. CIP-0112 (Token Standard V2, in progress) has the same dependency.
- Minimal blast radius. The change is additive — one new field on
AnsEntry, two Scan API extensions, and a backwards-compatible shim. No existing integrations break. - Unblocks multiple in-flight initiatives. Token Standard V2 (CIP-0112) and the proposed Oracle Standard both depend on structured CNS metadata for service discovery. Delivering CNS V2 ahead of or alongside those rollouts avoids a second migration wave.
- Realistic scope. The 4-month timeline covers CIP ratification (community-driven, not fully in the author's control), implementation, DevNet validation, and verified Mainnet adoption by 3+ independent services.
