CIP-TBD: Identity, Credentials and Party Metadata on Canton - Wayne Collier, Simon Meier, Eugene Birsky
cip-discuss1 messagesstarted 12-01-2026
Also mentions:CIP-0056
- Digital Asset, PixelPlex and a group of other Canton builders are working to develop CIPs for standardizing definition and sharing of identity, credentials and other party metadata on Canton. Conceptually this can be seen as building on the existing Canton Name Service (CNS).Currently the plan is to create at least three CIPs, covering the following topics:
1. How to discover the off-ledger API endpoints for CIP-0056 token admins
2. How to enable parties to self-published profile information that can be displayed uniformly across apps
3. How to empower app providers to use trustworthy human-readable names for parties both for
displaying names
accepting names to determine party values for actions the users want to take
The scope of the first CIP will roughly cover
Credential Registry APIs: define standard APIs for storing, retrieving, and using Canton Network credentials.
DSO Credentials Registry: specifies how these APIs are implemented in a decentralized registry run across the SV nodes.
Standardized Application and Metadata Discovery: specifies how these APIs are used to standardize the discovery of specific kinds of applications on the network and their metadata. In particular, this CIP standardized how to discover the off-ledger APIs of credential registries, the UIs of credential issuers, and the off-ledger APIs of CIP-0056 asset registries.
Discussions on this topic are currently taking place in a Foundation-hosted Slack channel, with the first draft proposal expected in about two weeks. That draft will be posted here, along with a long to a PR in the CIP GitHub repo, to allow more detailed discussions.
If you're working on or interested in this topic you can comment here. If you'd like to join the Foundation-hosted Slack discussion before the draft PR gets posted, please indicate here as well.