Thread by @fraser_again

#web5 is a genius marketing move to capture #SEO for what is mostly self sovereign identity #SSI but the key part is, it's the basis for #decentralised #twitter which we saw the first hints of at internet identity workshop #IIW

Some more thoughts👇

https://twitter.com/fraser_again/status/1521872738444480512?s=20&t=li-FJkRyKgLgrTSE7Yn4Pg

https://twitter.com/jack/status/1535314738078486533

1/ First up, this is exactly the publicity that #SSI has been missing for global adoption!

There has been a great and growing community beavering away on this for years but the dam is finally breaking on awareness and adoption.

2/ @blocks' #web5 project is being built by longstanding leaders in this community like @csuwildcat.

They're also members of both Chain Agnostic Standards Alliance and @DecentralizedID (as is @cheqd_io). This means it's going to be built in the right way

github.com/ChainAgnostic/…

3/ What counts as the right way?
- Open
- Standard-based
- Privacy-focused
- Interoperable

4/ @brockm made a big point of describing #web5 as a protocol at #consensus22. The codebases referenced below by @blocks should be viewed as just one set of implementations.

developer.tbd.website/projects/web5/

5/ Either I can't find it or this image has been removed from the @TBD54566975 website overnight.

Each of the components below has many implementations ranging from @SpruceID through to @evernym, now part of @Avast (in case we needed another data point that #SSI is happening!)

6/ So how does that fit with what we're building over at @cheqd_io, if we re-use the same image:

- DID management: there is a #cheqd DID which is in the process of being added to the w3c registry here: w3c.github.io/did-spec-regis…

7/
- Credential schemas: We're working on improvements to these, specifically how they're versioned, managed and accessed: cheqd.link/Xe5E

- Revocation: We'll be working on a more privacy preserving method for this.

8/ However, these are mainly scaffolding for what our core purpose is:

"building sustainable commercial models for #SSI" (or #web5 as it might now be known)

9/ This isn't a problem if you're @blocks / building decentralised twitter but for everyone else it matters:

https://twitter.com/JoukoSalonen/status/1535658119606546436?s=20&t=li-FJkRyKgLgrTSE7Yn4Pg

Our thesis at @cheqd_io is that (aside from awareness) it's commercial viability that has been holding #SSI / #web5 back

10/ Looping back to the tech, whilst @blocks' initial implementation will focus on using ION as the ledger, their membership of CASA and stance of #web5 being a "protocol" means it will need to interoperate across networks.

11/ To that end, we at @cheqd_io will be looking at the self-sovereign identity service and SDK codebases to see how easy other DID, schema and revocation methods can be added in so builders have choice.

12/ To close this out:
- The publicity this will generate for all of #SSI is incredible and has been needed for so long!
- @blocks are building in the right way with the right people
- #decentralizedtwitter is coming!

13/ Check out my co-founder, @ankurb's take cause he's better at this than I am👇

And full credit to him for the #SEO point!

https://twitter.com/ankurb/status/1535667405539577856?s=20&t=li-FJkRyKgLgrTSE7Yn4Pg