ssi-service
credo-ts
| ssi-service | credo-ts | |
|---|---|---|
| 1 | 1 | |
| 150 | 238 | |
| 2.7% | 3.4% | |
| 8.4 | 9.3 | |
| 17 days ago | 3 days ago | |
| Go | TypeScript | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ssi-service
-
How to get started learning web5
to publish credentials anyone can discover and independently verify" without spending any thought on how such a PKI would be ("independently") governed without centralizing everything back again – an all too common failure model in 'web3' [3].
Meanwhile, both Dorsey's slideware [4] and the actual specifications referenced [5][6] make bad technological choices with regard to privacy where users have stable identifiers (their public keys) which must be published, allowing them to be easily tracked across transactions. While this can be considered a building block, no material on the PR website or the TBD54566975 Github repository (I guess it's some other wordplay) indicates that they even recognize this as a problem, let alone how to solve it.
This is no new problem however: Sovrin – which many people referenced in the OP have worked on or with – has published a commentary on this back in 2018 [7]. There's also a great talk by Drummond Reed if you need to refresh your memory about what you need to consider when designing identity systems [8].
Otherwise the OP can be a great introduction to identity, but please don't feed the magical hypetrain.
[1] https://github.com/TBD54566975/ssi-service#whats-supported
[2] https://developer.tbd.website/docs/Decentralized%20Web%20Pla...
[3] https://moxie.org/2022/01/07/web3-first-impressions.html
[4] See the diagram on page X of [2]
[5] https://identity.foundation/decentralized-web-node/spec/#ser...
[6] https://identity.foundation/ion/
[7] https://sovrin.org/wp-content/uploads/2018/10/What-Goes-On-T...
[8] https://www.youtube.com/watch?v=JzM_Brpk95E&t=1574s
credo-ts
-
Hyperledger SSI Ecosystem
Here is a diagram showing how all those components fit together. I took Aries JavaScript Framework for demonstration (I’m a little bit biased here because I started the project, and I’m a fan of it, of course):
What are some alternatives?
ion - The Identity Overlay Network (ION) is a DID Method implementation using the Sidetree protocol atop Bitcoin
aries-askar - Secure storage designed for Hyperledger Aries agents.
sidetree-cardano - Implementation of Sidetree protocol on top of Cardano blockchain and IPFS
indy-sdk - indy-sdk
findy-agent-cli - CLI tool for Findy agency
indy-node - The server portion of a distributed ledger purpose-built for decentralized identity.
verity
indy-vdr - A library and proxy server for interacting with Hyperledger Indy Node ledger instances
aries-rfcs - Hyperledger Aries is infrastructure for blockchain-rooted, peer-to-peer interactions
issuer-kit - Verifiable Credential Issuer Starter Kit
ursa - Hyperledger Ursa (a shared cryptographic library) has moved to end-of-life status, with the components of Ursa still in use moved to their relevant Hyperledger projects (AnonCreds, Indy, Aries and Iroha).
indy-shared-rs - Shared Rust data types and utility functions for Hyperledger Indy.