Decentralized Identity
Instead of every company storing your data, you hold your own verifiable credentials and prove claims yourself — a genuine promise with genuinely hard problems.
Think about how identity works online today: dozens of companies each store a copy of your data — name, age, documents — behind logins you don’t control, and every breach spills it. Crypto offers a different model, using the one thing this track started with: keys you control (lesson 2). The idea is that you hold your own credentials and prove things about yourself without a central authority holding your data. It’s one of crypto’s most genuinely appealing applications — and, honestly, one of its hardest to actually pull off. Hold the question: if you control your own keys, how could you prove “I’m over 18” or “I have this degree” without a company storing and vouching for you?
The idea: you hold your credentials, not the companies
The model is called decentralized or self-sovereign identity. Instead of each service storing your data, a trusted issuer (a government, a university, a bank) gives you a verifiable credential — a digitally signed statement (like “this person is over 18” or “holds this degree”) that you store in your own wallet (lesson 2). Later, when a service needs to check that claim, you present the credential, and they can cryptographically verify the issuer really signed it — without contacting the issuer and without the issuer storing a record of every place you used it. You become the holder of your own identity, presenting proofs on demand, rather than a row in a hundred company databases. The blockchain’s role is usually small and specific: a public place to look up issuers’ keys and check that a credential hasn’t been revoked — not to store your personal data.
The genuine promise: control and privacy
Done right, this is genuinely better on two axes. Control: you decide who sees what, and services no longer each hoard a copy of your data to be breached (recall the privacy duty from the AI track — less data stored is less data to leak). Privacy via selective disclosure: the killer feature is proving just what’s needed and nothing more. To buy alcohol you must prove “over 18” — but today you hand over an ID showing your exact birthdate, name, and address. A verifiable credential (often with a zero-knowledge proof, recall the crypto scaling module) can prove “over 18 = true” while revealing nothing else — not even your birthdate. That’s a real privacy win no plastic ID can match, and it’s the most compelling reason the idea keeps attracting serious effort.
Proving you’re over 18, two ways: • Today: show a driver’s license → the bouncer sees your birthdate, full name, address, license number — far more than needed. • Verifiable credential: your wallet proves “over 18: true,” signed by the government, verified cryptographically → the bouncer learns only that you’re over 18, nothing else. • Same claim proven; drastically less data exposed.
The hard reality: UX, recovery, and where trust still lives
So why isn’t this everywhere? The honest obstacles are steep. Key management & recovery (lessons 2, 18, 40): if you hold your identity keys, losing them means losing your identity — and “no undo” is terrifying for something as critical as identity, so recovery (without recreating a central authority) is a genuinely hard, unsolved-at-scale problem. UX & adoption: ordinary people find key management confusing, and the system only works if issuers and verifiers all adopt the same standards — a massive coordination problem (network effects, from the Future track). And the crucial honest point: decentralized identity doesn’t remove trust in the issuer — you still have to trust that the government or university that signed the credential is legitimate and honest (the same off-chain-trust lesson as real-world assets, lesson 47). It relocates where your data lives (to you) and improves privacy, but the credential is only as trustworthy as its issuer. So the honest verdict: a genuinely promising model with real privacy benefits, held back by hard recovery/UX/adoption problems — one of crypto’s better ideas that is still mostly promise, not reality. (Neutral education — no product named.)
Think of the difference between a bar tab kept by the bar versus cash in your own wallet. Today’s online identity is the bar tab: every establishment keeps its own record of you, and if any of their books get stolen, so does your info. Decentralized identity is carrying your own sealed, tamper-proof documents: a university hands you a signed diploma you keep, and anyone can verify the seal is real without phoning the university or the university logging where you showed it. Better yet, you could reveal just one line of the diploma and cover the rest. The catches are equally down-to-earth: if you lose your wallet of documents there’s no registrar to reissue them, everyone has to agree to accept this kind of sealed document, and the diploma is still only as trustworthy as the university that sealed it.
Judging a decentralized-identity claim honestly: 1. What does it genuinely improve? → you hold your data (fewer honeypots to breach) and can selectively disclose (prove “over 18” without your birthdate). 2. What does it NOT remove? → trust in the issuer (a fake or dishonest issuer still fools verifiers) and the need for everyone to adopt shared standards. 3. What’s the scary risk? → key loss = identity loss, with recovery unsolved at scale. 4. Verdict: real privacy/control benefits, but held back by recovery/UX/adoption — mostly promise so far.
This is the reading. The interactive version — active-recall quiz, a hands-on experiment you run in your own AI, and an earned mastery check — is free in the app.
Start this lesson free →