Web3 login web3 ID vs Web5 DIDAuth ( DID authentication)
https://makertube.net/videos/watch/767f8fe8-3f37-4dd1-943a-f6b24b90d8f1
Web3 login web3 ID vs Web5 DIDAuth ( DID authentication)
https://makertube.net/videos/watch/767f8fe8-3f37-4dd1-943a-f6b24b90d8f1
Advanced DID Auth with VP and SIOP for openID
https://makertube.net/videos/watch/f6d1306b-69eb-4434-b722-09a4149d298c
Web3 login web3 ID vs Web5 DIDAuth ( DID authentication)
https://diode.zone/videos/watch/f833e695-2039-47b8-9dfa-942d24863cc7
#web3 id or #web3 login is a remedy to all our problems - decentralized, OTP less, passwordless! Before we all move to a new happier world. I have a few questions: how do we rotate a key and deal with a stolen private key?, is it passwordless? How do we unlock a wallet, and how do we recover a password?, how do we make it cross-device?, I have a better answer to this challenge— #Web5 Auth, or how we call it in our #affinidi #sdk - #DIDAuth. DIDAuth - is an edge auth protocol that proves ownership of private keys based on DID. With #DID, we decouple but cryptographically bind Controller (user), private/public pair, and identifier. So with a DID method that supports key rotation, we could solve the first challenge. With seed migration, we could solve a cross-device experience. Recovery is a more complex story #affinidi #sdk solve it for custodial users and give building blocks for edge developers to implement their solutions for this challenge. Lets #build a new world together
Advanced DID Auth with VP and SIOP for openID
https://diode.zone/videos/watch/a7b52504-a0f2-4b98-8051-190c3533f222
To use DIDAuth for private key proof, your could use #affinidi #sdk https://github.com/affinidi/affinidi-core-sdk/tree/master/common-libs/did-auth-lib. It covers a lot of cases when the resource is connected to did. What to do if you need to share claims together with DID? The answer is quite simple all you need is a slightly modified exchange protocol for Verifier. So we ask the verifier to send us a challenge and issue a VP. All protocols have a common issue - the adoption curve. It is much easier to get adoption when you build on top of standards that are already in use. I am happy to see the recent OpenID for Verifiable Presentations spec https://openid.net/specs/openid-4-verifiable-presentations-1_0.html that is based on another fantastic spec: Self-Issued OpenID Provider v2 https://openid.net/specs/openid-connect-self-issued-v2-1_0.html. It lifts #SSI concepts with #openId ecosystem and allows us to use a VP for advanced DID Auth