Decentralized Identifiers (DIDs): a practical primer

KILT: Credentials for web3

@KILTProtocol @maudnals

Agenda

1. KILT

2. DIDs

3. DIDs in our system

4. DIDs in practice: Universal Resolver driver implementation

2@KILTProtocol @maudnals

But first

page 3@KILTProtocol @maudnals

• KILT Protocol, Ingo Rübe

@KILTProtocol

kilt.io

• Maud @maudnals

• ... You x DIDs?

KILT

Parity Substrate-based

Permissionlesstrust

infrastructure

Credentialsfor the web3

Regulation-friendlyvirtual structures

page 4@KILTProtocol @maudnals

DIDs?

page 5@KILTProtocol @maudnals

Now With DIDs

Source: SSI Meetup

DIDs?

A DID is a new type of

globally unique identifier, that does not require a centralized registrationauthority; control of theidentifier can be provedcryptographically.

https://w3c-ccg.github.io/did-spec/

page 6@KILTProtocol @maudnals

4 core properties of DIDs

1. Persistent

2. Resolvable

3. Cryptographically verifiable

4. Decentralized

NOT: human-readable

page 7@KILTProtocol @maudnals

DID + DID Document

kilt

page 8@KILTProtocol @maudnals

did:ethr:did:btcr:did:sov:did:uport:...

CRUD

• Create

• Resolve

• Update

• De-activate

= f(DID method)

= `kilt` in our case

page 9@KILTProtocol @maudnals

DIDs in KILT

page 10@KILTProtocol @maudnals

did:kilt:5GZPvZad...

*

Universal Resolver by

page 11@KILTProtocol @maudnals

uniresolver.io👉

Driver guidelines

page 12

• Resolve functionality only: resolve(did) -> diddoc

• Open-source

• Container on dockerhub

• Documented methods

@KILTProtocol @maudnals

KILT‘s dockerized driver

page 13@KILTProtocol @maudnals

Food for thought

page 14@KILTProtocol @maudnals

• DID fragments

• Remote or not

• Universal Registrar

did:kilt:123456#oidc

Thank you@KILTProtocol

@maudnalskilt.io

Check out TCAs 🔥Slides coming soon

Sources

page 16@KILTProtocol @maudnals

DID Resolution Webinar // DIF at SSI Meetup

DID Methods Registry

Universal Resolver: introduction