ion VS did-core

- For completeness and good scientific practice, also look at solutions beyond Ethereum: https://identity.foundation/ion/

ION decentralized identity (an implementation of the SideTree protocol)

Other uses are extremely limited IMO. Microsoft ION, an implementation of decentralised identity w3c spec, for example. It makes a Bitcoin transaction containing a hash that refers to several identities. Since the identities are mutable there does not seem much value in remembering the hash at a point in time.

I agree the website is very bad, currently. Maybe this page has better resources:

https://essif-lab.github.io/framework/docs/ssi-standards

But there's quite a lot going on... the work on SSI is being coordinated by the W3C Working Group on VCs (Verifiable Credentials) and DIDs (Decentralized Identifiers).

https://www.w3.org/community/credentials/

https://www.w3.org/2019/did-wg/

I don't know of any real-world usage yet, despite the fact that the specifications required for things to work and be used by real people already exist, and that there's a lot of DID methods (over 80 last I checked) registered, but as people have noted, most are based on blockchain (but not all... there's stuff like the peer, git, jwk DID methods that do not require blockchain)... but I have to say that, in this particular instance, blockchains may actually be a proper solution for a real problem (that of looking up public keys and metadata for entities/users in a distributed, highly-reliable manner).

https://www.w3.org/TR/did-spec-registries/#did-methods

If you want to look for related stuff, look for things that users would need to have to use SSI, like DID wallets... Some random examples I found by quickly searching:

https://www.abtwallet.io/en/

https://www.didwallet.io/

https://igrant.io/

https://www.dock.io/dock-wallet-app

https://identity.foundation/ion/

The OpenID Connect Standard is being extended to support self-issued OIDC (SIOP) which allows OIDC to interact with SSI constructs:

https://openid.net/specs/openid-connect-self-issued-v2-1_0.h...

So, yeah, there's a lot of stuff being created around SSI, but admitedly, almost nothing practical yet... Hence why I was hoping to find something where this work could be very helpful, like logging into Codeberg :)

I would also recommend checking ION¹. I have tested a few DID Methods including Sovrin, Veres One, and ION, and the latter is the most spec-adherent and well-implemented, apart from receiving funding from companies like Microsoft and TBD (which is proposing web5 in the first place). And yes, it is the only DID Method to receive support from big tech (was incubated within Microsoft, then donated to the Decentralized Identity Foundation), and it also happens to be a technically good solution.

¹ https://identity.foundation/ion/

Microsoft ION --->https://identity.foundation/ion/

Doing some more research: Looks like the idea is developed by tbd.website and uses a L2 tool called ION that utilizes the SideTree protocol. Interestingly, ION does not introduce a new token which I find interesting, and one of the things I've found confusing about Stacks.

In 1994, Tim Berners Lee, the creator of the World Wide Web, founded the World Wide Web Consortium (W3C). The W3C is made up of groups of people focused on setting the best practices and standards for building the web. For example, the W3C develops and maintains standards for HTML, CSS, Web Accessibility, and Web Security. In July 2022, The W3C officially published standards for Decentralized Identifiers. This way, technologists would have blueprint for building and managing digital identity as we make the shift towards controlling your identity on the internet. Check out the Decentralized Identifiers specification here.

A few months ago, I started looking into decentralization on the web and how this could impact our world as we know it today - thanks to Web5 and our work at TBD. One of the biggest and most important pillars in achieving this decentralized future is called Decentralized Identifiers (DIDs).

Unfortunate choice of name, given https://www.w3.org/TR/did-core/.

I'm also a software engineer, and I'm actively working on making it a thing in a parallel system (referenced above) lol. DIDs have been a standard for a while, and as someone who's had my SIN compromised (by Equifax of all places), our current way of handling ID is far easier to hack than a well implemented digital ID would be. Its actually asinine to me that I was compromised in 2016, and DID existed then... yet here we are 7 years later, with identity thefts only climbing year-over-year, and we still have antiquated, and clearly failing identity systems in place.

DESCRIPTION: We are looking for a Rust developer to join the team developing a cross-platform digital identity application using the Tauri framework and several (cloud-based) Rust components for Identity-as-a-Service solutions. We are a young start-up that is developing digital identity products and solutions for people and organizations, based on the decentralized identity standards. Our work includes developing open-source implementations of standards such as DID and Verifiable Credentials from W3C and OpenID4VC from the OpenID Foundation. Using this technology, people gain control over their own digital identities and data and can easily share verifiable information with third parties, enabling more privacy and digital trust.

DID methods are the W3C solution to decentralized identity: https://www.w3.org/TR/did-core/

https://www.w3.org/TR/did-core/#key-and-signature-expiration

"9.8 Verification Method Revocation" https://www.w3.org/TR/did-core/#verification-method-revocati...

Blockerts is built upon W3C DID and W3C Verified Credentials, W3C Linked Data Signatures, and Merkel trees (and JSON-LD). From the Blockerts FAQ

What do you think about Decentralized Identity (DIDs - https://www.w3.org/TR/did-core/)? With it, you can have several identities and easily generate new ones when needed (but you probably need to have a single, government-recognized identity for the real world).

Europe seems to be working hard on establishing an identity for every citizen: https://commission.europa.eu/strategy-and-policy/priorities-... (most countries already have that, but this is about unifying the various countries' ID systems).

Domain names as handles are a cool idea, and you can already do a variant of them in the "fediverse" either by hosting your own instance of a service or by configuring a WebFinger alias (which is what I do).

I'm less convinced by DIDs[1], which is what Bluesky seems to run on: I've yet to see an explanation for why the DID standard exists, given that it effectively punts all semantics (including basic things like cryptographic verification) onto unstandardized "methods" in an uncontrolled global namespace.

[1]: https://www.w3.org/TR/did-core/

- very close is the foundation regarding Decentralized Identifiers by the W3C https://www.w3.org/TR/did-core/ // https://w3c.github.io/did-core/