Selective Disclosure

Selective Disclosure is the data-minimization principle made cryptographic: prove the one fact that is asked for, and nothing else. Instead of handing over an entire credential, a holder discloses only the individual claims a verifier requires — confirming they are over a threshold age, hold a license, or live in a jurisdiction — while the remaining attributes stay concealed yet remain provably authentic under the issuer's original signature. The verifier gets certainty about the disclosed claims; the holder keeps everything else.

How it is achieved

Two families of technique dominate. Salted-hash schemes like SD-JWT have the issuer replace each disclosable claim with a digest of a salted value before signing; at presentation time the holder reveals only the cleartext claims and salts they choose, and the verifier recomputes the digests to confirm they belong to the signed credential. The salt is essential — without it, a verifier could brute-force low-entropy fields like birth years straight from their hashes. Zero-knowledge schemes like BBS+ and AnonCreds go further: the holder proves possession of a valid signature over hidden messages, and can even prove predicates such as "older than 18" without revealing the underlying value at all. The zero-knowledge family also delivers unlinkability — each presentation is cryptographically fresh, so two verifiers comparing notes cannot tell they saw the same credential.

Why sovereign users care

Every extra attribute you reveal is a correlation handle someone else keeps forever. Selective disclosure is the same instinct that drives coin control and address hygiene in Bitcoin: surface area is liability. A Bitcoiner who refuses to consolidate UTXOs that would link their payment history should refuse, on identical grounds, to present a full identity document when the question was merely "is this person an adult." Two interactions that each disclose only minimal, distinct facts are far harder to stitch into a single profile, which directly supports what might be called fungibility of identity. The alternative — photographing an ID card that exposes name, address, birthdate, and document number to prove a single yes/no fact — is the identity equivalent of publishing your extended public key to buy a coffee.

Practical state of play

Selective disclosure is moving from theory into deployed formats: SD-JWT is on a standards track for the credential formats used in large-scale digital identity programs, while AnonCreds has years of production history in permissioned ecosystems. The honest caveats: predicate proofs and unlinkability are only as good as the surrounding metadata discipline — a unique credential identifier or a reused holder key can re-link what the cryptography carefully separated — and verifiers must actually request minimal claims rather than lazily demanding everything. Holder-side wallets that default to minimum disclosure are what make the guarantee real for non-experts. Selective disclosure is the engine inside every privacy-preserving verifiable presentation, and the reason self-sovereign identity can credibly claim to be something better than digitized photocopies.

Threats that remain

Selective disclosure narrows what crosses the wire; it does not sanitize everything around the message. Session metadata — IP addresses, timing, device fingerprints — can re-link interactions the cryptography carefully separated, so transport privacy still matters. Verifier over-asking is the social attack: nothing technical stops a service from demanding every attribute "for compliance," and the defense is wallet software that surfaces exactly what is requested plus users willing to walk away. Issuer-verifier collusion is harder: salted-hash schemes leave the issuer's signature as a stable identifier across presentations, so unlinkability against colluding parties genuinely requires the zero-knowledge family. And revocation checks can become their own tracking channel if a wallet phones the issuer at every presentation. The honest summary: selective disclosure is necessary but not sufficient — it must sit inside a stack whose transport, wallet defaults, and governance take privacy as seriously as the math does.