ssi-service VS sidetree-cardano

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

Here’s the code: https://github.com/rodolfomiranda/sidetree-cardano