Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents
minLevel1
maxLevel6
outlinefalse
stylenone
typelist
printabletrue

Introduction

did:scid is a proposed new DID method designed to maximize the security, privacy, and portability benefits of self-certifying identifiers (SCIDs). Here is the definition of a SCID in the ToIP Glossary:

...

That is the purpose of the did:scid method.

Examples

NOTE: The first two examples are based on the verification metadata formats defined by the did:webvh and did:webs methods, both of which have the constraint of being valid did:web DID. By contrast, a did:scid is not a valid did:web DID because it does not include any location information in the DID itself (the location information is only in a did:scid URL parameter).

did:scid Webvh Example

The first example is a DID that uses version 1 of the Webvh did:scid method. The other four are example did:scid URLs that show three different web servers and one blockchain (cheqd) where the verifiable history may be found as defined by the did:webvh method.

...

A did:scid consists of five colon-delimited segments as summarized in table 1:

#

Segment

Purpose

1

did

URI scheme as required by W3C DID 1.0

2

scid

DID method name

3

scid-method-name

SCID method name

4

ver

SCID method version

5

method-specific-id

SCID value

A did:scid  MUST conform to the following ABNF (most of which is identical to section 3.1 of W3C Decentralized Identifiers 1.0):

...

Appendix A: did:scid Method Registry

TODO: Add did:scid methods (which of course need their own specs). Proposed entries:

  1. did:scid:ke — uses the ​did:webs verification metadata format.

  2. did:scid:vh — uses the ​did:webvh verification metadata format.

  3. did:scid:pr:2 — uses ​did:peer, variant 2.

  4. did:scid:pr:3 — uses ​did:peer, variant 3.

  5. did:scid:pr:4 — uses ​did:peer, variant 4.

Appendix B: Bluesky DID Requirements

...

Because it is designed to be fully portable, a did:scid can have its verifiable history written to any number of target locations.

IMPORTANT: When the verifiable history of a did:scid is written to multiple locations, this may raise data synchronization challenges. Responsibility for those challenges lies with each did:scid method specification and/or implementation.

When these locations are web servers designed explicitly to accept verifiable history updates securely (e.g., by verifying the signature of each update), we can call this a DID server

...