Verifiable credentials, zero-knowledge proofs, and selective disclosure get used almost interchangeably in identity marketing, and that's a problem for anyone actually building on top of them. A verifiable credential is a data format. A zero-knowledge proof is a cryptographic proof technique. Selective disclosure is neither of those by itself, it's what happens when a credential's structure and, often but not always, a zero-knowledge proof combine to let someone share exactly one fact about themselves and nothing else.
The confusion has a real cost. A team evaluating an identity stack ends up asking the wrong question, does it support zero-knowledge proofs, when the question that actually determines what a user experiences is which selective disclosure mechanism sits behind that answer. BBS+ signatures and SD-JWT solve the same problem with different math, and the EU has already picked one of them as the mandatory baseline for every European Digital Identity Wallet due by the end of 2026. This post works through what each term actually means, how they connect, and what to check before adopting any of them.
What Is a Verifiable Credential?
A verifiable credential is a digitally signed claim, structured to a specific data model rather than free-form. The W3C Verifiable Credentials Data Model 2.0 defines the shape: an issuer signs a set of claims about a subject, a holder stores the resulting credential, and a verifier checks the issuer's signature cryptographically instead of calling the issuer back to confirm anything. A university issuing a diploma as a verifiable credential, or a government issuing a driving licence the same way, are both plain examples of the model, the credential itself is the signed artifact, not a PDF or a scanned image of one.
