Verifiable Credential

A Verifiable Credential (VC) is a digital, cryptographically signed statement of claims — a diploma, a membership, a proof of age — that anyone can check for authenticity and integrity without contacting the issuer in real time. The W3C Verifiable Credentials Data Model defines a three-party ecosystem: an issuer signs and grants the credential, a holder stores it in a wallet they control, and a verifier checks the signature against the issuer's public key. The trust lives in the cryptography and in your knowledge of who the issuer is — not in a phone call to their server.

How it differs from a database record

A traditional credential — a username row, a centrally hosted certificate — only means something while the issuing system is online and willing to confirm it. The issuer sees every verification, can revoke your access silently, and becomes a single point of failure for everyone downstream. A verifiable credential inverts that: the proof travels with the data. The signature is embedded in the credential itself, so verification works offline, the issuer cannot log each use, and losing the issuer's website does not erase your diploma. Bitcoiners will recognize the shape of this argument — it is the same property that makes a Bitcoin transaction self-verifying against the chain rather than against a bank's API, applied to identity instead of money.

Selective disclosure and holder binding

Modern VC formats support selective disclosure, letting a holder reveal only the specific claims a situation requires — proving "over 18" without handing over a birth date, name, and address. Zero-knowledge techniques push this further, proving a predicate about a claim without revealing the claim at all. Just as important, credentials are bound to the holder's keys, typically expressed through a Decentralized Identifier (DID): presenting a credential involves a fresh signature from the holder's private key, so a stolen credential file cannot simply be replayed by someone else. The act of presenting one or more credentials, with proof of holding, is formalized as a verifiable presentation.

Where the model stands today

The Verifiable Credentials Data Model v2.0 was published as a W3C Recommendation in 2025, and VCs are the workhorse data format of Self-Sovereign Identity (SSI). Governments and standards bodies are converging on adjacent formats for digital driver's licenses and identity wallets, which makes the design questions urgent rather than academic: a credential system can be built so the holder controls disclosure, or so every presentation phones home. The VC model demonstrates that the privacy-preserving version is technically straightforward — whether deployments choose it is a policy fight, not an engineering one.

Why this belongs in a mining glossary

The through-line of this site is sovereignty: hold your own keys, verify rather than trust, and keep third parties out of loops they do not need to be in. Verifiable credentials apply that discipline to identity. A holder with credentials in their own wallet, bound to keys they control, is in the same structural position as a Bitcoiner in self-custody: institutions can still issue and still revoke what they issued, but they cannot silently surveil, edit, or confiscate what you carry. Understanding VCs now is how you evaluate the identity systems being built around you — before they are mandatory.