Goals of DIDs (Decentralised Identifiers)

	•	Ease of creation
	•	Decentralized
	•	Persistent
	•	Resolvable
	•	Cryptographically verifiable

🧫
sys.auth
sys.identity

🐵<🐦‍⬛> ← 🙈🙉🙊 → /phil →  github.com/philcockfield →  
ƒ(🌳) →  🧫 /sys  ←  @cell <T>, 🧠 human.

Don’t have any adoption, have been around for a long time

Working on building zkTLS infra/products. A ruthless empiricist and meme connoisseur.

/opacity

and

/eulerlagrange

I worked in this industry. Verifiable credentials don’t have much adoption wrt how long they’ve been around.

Give me some examples.

I explain this here:

Rated 💯 by multiple networks. Fluent in /unglish. Unbothered by /whatday of the week it is.

Allegedly a designer.

I worked in this industry. Verifiable credentials don’t have much adoption wrt how long they’ve been around.

Give me some examples.

I explain this here: https://youtu.be/C8_Ii_rGl1A?si=a6qKr5AOnzHcqGaR

You can also play with it here: https://testflight.apple.com/join/wfkqexrx

thanks (watching now)
appreciate the reference @eulerlagrange

Web Tinkerer. DWeb. Open Source. Community. Just another one of the bees 🐝

I started /opacity for this reason.

I can take any https response and convert it into a credential using zkTLS with a zkVM. JSON-LD and everything.

Like a bank statement for example :)

Radicle is all DID-based @radworks 

I agree the enterprise verifiable-credentials I-made-my-own-DID-flavour is going nowhere. 

The adoption is people simply using did:key

Likely to be a growing set of Localfirst usages of this.

I acknowledge it’s a slow burn, but I think it’s picking up in places like:

- Bluesky/ATProto
- everything SpruceID does
- everything we did at Fission

@boris you probably have a better list than me