Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add trait: Fork Protection #35

Open
jceb opened this issue Jan 14, 2025 · 1 comment
Open

Add trait: Fork Protection #35

jceb opened this issue Jan 14, 2025 · 1 comment
Labels
enhancement New feature or request

Comments

@jceb
Copy link
Contributor

jceb commented Jan 14, 2025

In the presentation of did:webplus on 13 Jan (https://github.com/decentralized-identity/identifiers-discovery/blob/main/agenda.md#meeting---13-jan-2025---1400-et--recording) a potentially interesting new trait was presented: Fork Protection of DID documents. The idea is to have mechanisms in place that prevent forks of DID documents, i.e. multiple versions of the DID document exist at the same time and are presented to different entities requesting the document (presumably with the intention of committing fraud). KERIs witnesses provide protection against such behavior, another mechanism was presented for did:webplus.

@jceb jceb added the enhancement New feature or request label Jan 15, 2025
@jceb jceb changed the title Consider trait Fork Protection Add trait: Fork Protection Jan 15, 2025
@ankurdotb
Copy link

It depends on whether the DID is controlled by the original author. Publishing a DIDDoc to multiple methods could be a feature, not a bug, that a DID publisher opts in to. E.g., publishing a did:webvh and a "also known as" DID on did:iden3, did:cheqd etc for compatibility reasons.

Someone external coming and just copying it without the original author's permission is where the issue lies. Is it this latter case we're talking about?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants