Skip to content

Proposal: Canton Party Namespace Registry (CPNR)#153

Open
blackthornlover wants to merge 2 commits intocanton-foundation:mainfrom
blackthornlover:cpnr-proposal-v2
Open

Proposal: Canton Party Namespace Registry (CPNR)#153
blackthornlover wants to merge 2 commits intocanton-foundation:mainfrom
blackthornlover:cpnr-proposal-v2

Conversation

@blackthornlover
Copy link
Copy Markdown

Development Fund Proposal Submission

Proposal file: proposals/canton-party-namespace-registry.md


Summary

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.

Checklist

  • I have read the contribution guidelines
  • The proposal follows the template structure in proposals/_template.md
  • I have included a clear abstract, specification, milestones, and funding breakdown
  • The proposal includes adoption-based milestones with verifiable acceptance criteria

Notes for Reviewers

  • Suggested label: party-portability-data-resilience
  • Total funding request: 1,400,000 CC across 4 milestones
  • Branch: cpnr-proposal-v2 (clean branch off canton-foundation:main — 1 commit, 1 file)

This proposal outlines the creation of a Canton Party Namespace Registry (CPNR) aimed at facilitating privacy-aware party discovery across synchronizers. It includes a versioned specification, reference implementation, and integration guidelines to reduce off-ledger coordination in multi-party applications.

Signed-off-by: blackthornlover <h@bitdynamics.me>
@blackthornlover
Copy link
Copy Markdown
Author

Hey @hythloda

Could you please apply the party-portability-data-resilience label to this PR? The CPNR proposal defines a privacy-aware, decentralized registry for Canton party identifiers, enabling cross-synchronizer party discovery without off-ledger coordination, which aligns directly with party portability and data resilience concerns.

Thank you!

Signed-off-by: blackthornlover <h@bitdynamics.me>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Incoming

Development

Successfully merging this pull request may close these issues.

1 participant