Why Verifiable Credentials and Decentralized Identity?
summary
Explains that verifiable credentials follow W3C and OpenID specs, store claims in a user wallet (not on-chain), and use DIDs and DID Documents retrieved from a verifiable data registry to check issuer public keys. Demonstrates a patient portal using Entra Verified ID, QR-based issuance and presentation to a verifier, TeamViewer wallet mirroring, and selective disclosure. Credentials have expiry and revocation, can be backed up and restored, and the demo issues and verifies credentials successfully after a transient live error.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:34Centralized identity systems
- 10:45Challenges with centralized identity
- 15:39Decentralized identity and verifiable credentials
- 19:36How decentralized identity works
- 27:30Verifiable credentials components
- 33:53Distributed ledger in identity
- 37:07Selective disclosure and privacy
- 41:23Live demo: verifiable credentials
- 53:36Real-world use cases
- 53:56Standards for verifiable credentials
- 57:48Q&A
related talks
46mDecentralized identity: What’s all the fuss about?
52mVerifiable Credential in Actions During ID-Verification Process
41mVerifiable Credentials and the Future of Enterprise Security
47mIntroduction to Verifiable Credentials
16mThe Importance of Digital Trust: An Overview of Decentralized Identity
55mDecentralized Identity Landscape: Communities, Projects, Technologies, and Tools
51mHealth Credentials, Travel, Climate Change, Financial Inclusion & More: Digital Identity Gets Real
30mPanel Discussion: Decentralized Identity Deep Dive - Advances in Trust, Security and Scalability