A revocation mechanism is a cryptographic or registry-based procedure for invalidating a previously issued credential, certificate, or access token before its natural expiry, allowing issuers to withdraw trust following compromise, policy change, or holder misconduct. In digital identity systems, revocation mechanisms range from Certificate Revocation Lists and OCSP for X.509 certificates to Bitstring Status Lists and cryptographic accumulators for verifiable credentials. The privacy characteristics and scalability of each approach differ substantially, making mechanism selection a critical design decision.
Content
- Credential revocation has been a challenge since the early public key infrastructure standards of the 1990s. X.509 v3 introduced Certificate Revocation Lists (CRLs) as the primary mechanism, but CRLs suffer from scalability problems as lists grow and from the staleness inherent in periodic publication. Online Certificate Status Protocol (OCSP) addressed timeliness by enabling real-time status queries, but introduced availability dependencies on OCSP responders and privacy concerns — an OCSP query reveals to the responder which certificate is being checked and approximately when.
- Modern verifiable credential systems have developed purpose-built revocation mechanisms designed for privacy and decentralisation. The W3C Status List 2021 (now Bitstring Status List 2024) specification encodes revocation status as a compressed bitstring hosted at a URL referenced within the credential, allowing verifiers to download the status list and check the relevant bit without revealing which credential they are verifying. Anoncreds-style credentials use cryptographic accumulators (typically RSA accumulator or Merkle-based constructions) that allow issuers to publish a compact revocation registry update without exposing individual credential identifiers.
- In decentralised identity ecosystems, revocation registries may be anchored on distributed ledgers (Hyperledger Indy, Cheqd) to prevent issuer unilateral manipulation after credential issuance. On-chain revocation registries provide auditability and censorship resistance at the cost of gas fees and public visibility of registry updates. Privacy-optimised designs encrypt registry entries or use zero-knowledge proofs to hide the revocation status of individual credentials even from the registry operator, a property called revocation privacy or selective revocation anonymity.
- Between 2023 and 2025, the W3C Bitstring Status List has been widely adopted in EU digital identity wallet pilots (EUDI Wallet architecture under eIDAS 2.0) as the standard revocation mechanism for SD-JWT VC and mDL credentials. The EUDI specification mandates short-lived credential re-issuance as an alternative to complex revocation for some use cases, reducing reliance on online status checks. Zero-knowledge revocation using accumulator schemes has advanced from academic prototype to production deployment in privacy-sensitive credential ecosystems, particularly for age verification and professional licence credentials where identity correlation is a significant concern.