ceramicnetwork / ceramicnetwork/CIPs

Update did:nft and did:safe specs to explain how to set Caip10Link, and the benefits of doing so

Open
#103 0 comments 1 reaction 1 assignee Claimed by @oed View on GitHub
documentation
Dominant language
HTML
Stars
84
Forks
25
PR merge metrics
No merged PRs in 30d

Description

[CIP-94](https://github.com/ceramicnetwork/CIP/blob/main/CIPs/CIP-94/CIP-94.md) (did:nft) and [CIP-101](https://github.com/ceramicnetwork/CIP/blob/main/CIPs/CIP-101/CIP-101.md) (did:safe) both have whole sections on how to read the Caip10Link from Ceramic to set the `controller` property of the resulting DID document, but doesn't have any information on how or when to *set* the Caip10Link. Nor does it explain the benefit of doing so, ie what the inclusion of the optional `controller` property to the DID document does.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.