Proposal: Canton Party Namespace Registry (CPNR)
RejectedPR- SIG
- party-portability-data-resilience
- Champion
- —
- Author org
- —
- Ask
- 1,400,000
Abstract
This PR adds the Canton Party Namespace Registry (CPNR) proposal — a privacy-aware, decentralized registry specification and reference implementation for Canton party identifier discovery across synchronizers, eliminating the need for off-ledger party identifier exchange in multi-party workflow initiation.
Milestones
| Title | Due date | Target | Amount (CC) |
|---|---|---|---|
| Specification Published and First Namespace Validated | — | At least one Canton operator or application team has reviewed the CPNR specification, provided written feedback incorporated into the final document, and confirmed that the namespace structure and disclosure policy model are applicable to their party discovery requirement without requiring off-ledger workarounds. | 300,000 |
| Daml Registry Contracts Deployed and Validated in a Live Environment | — | At least one Canton operator or application team has deployed the reference Daml registry contracts against a real (non-sandbox) Canton participant node, registered at least one party entry, and confirmed that the disclosure policy model correctly controls resolution access in their environment. | 500,000 |
| TypeScript Resolution Toolkit Adopted by at Least One Application | — | At least one Canton application team has integrated the TypeScript resolution toolkit into their application, replaced an off-ledger party lookup with an on-ledger CPNR resolution flow, and confirmed that the integration reduces their off-ledger coordination requirement. | 400,000 |
| Multi-Synchronizer Resolution Validated and Standard Publicly Released | — | At least three independent Canton operator or application teams have adopted some portion of CPNR — specification, registry contracts, or resolution toolkit — and the project has been publicly released with documented adoption evidence, so that future teams can start from a validated baseline rather than building off-ledger discovery from scratch. | 200,000 |
| Total | 1,400,000 | ||
Budget impact
- % of approved-to-date
- 1.9%
- % if all RFV pass
- —
RFV scenario unavailable — using approved-to-date as denominator (degraded mode).
- Ask (CC)
- 1,400,000
Comments by org
3 comments · 1 org · last activity May 5, 2026
| Organisation | Comments |
|---|---|
| Unknown | 2 |
| Digital Asset | 1 |