feat: draft proposal for CNS v2

[lgahdl]

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

• Proposal file added under /proposals/
• Milestones and funding amounts defined
• Acceptance criteria included
• 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.

[github-actions]

@lgahdl, your proposal is missing a Special Interest Group (SIG) label. Adding the right SIG label ensures the relevant domain experts can find and review your proposal, Check more about SIGs.

Please add one of the following labels to this PR:

• attestor-pools-daos-multisig
• canton-apis
• canton-protocol-multi-synchronizer
• daml-tooling
• dapp-integration
• dar-app-management
• defi-liquidity
• defi-protocols
• financial-workflows-composability
• global-synchronizer-scaling
• node-deployment-operations
• onchain-governance
• party-portability-data-resilience
• regulatory-compliance
• token-asset-standards
• tokenomics
• wallet-apps

Not sure which one fits? Pick the closest match to your proposal's domain. You can add a label from the right sidebar under "Labels".

[github-actions]

@lgahdl, thank you for your interest in the Canton Development Fund!

Your proposal needs a valid Tech & Ops Committee champion organization. The champion field is either empty, contains placeholder text, or names an organization that is not a current Tech & Ops Committee member.

Per CIP-0100, all external proposals require a Tech & Ops Committee champion.

Next steps:

1. Identify a Tech & Ops Committee member organization willing to champion your proposal
2. Update the Champion field with their name
3. Reopen this PR

If you need help finding a champion, reach out to SIGs or any Tech & Ops Committee member.

This PR is being closed automatically. You are welcome to reopen it once a champion is confirmed.

[waynecollier-da]

@lgahdl There's a working group in place that is actively working on a series of CIPs to implement CNS v2.0

Data structure and overall architectural approach: canton-foundation/cips#204
Party profiles:canton-foundation/cips#169
Address resolvers: canton-foundation/cips#171