Non-Revocation Token

identity.foundation · 1,279 words · saved by 1 readers

This specification describes a privacy-preserving revocation method for Verifiable Credentials. A Non-Revocation Token that contains a cryptographic accumulator signed by the issuer is used by the holder to prove a Verifiable Credential hasn’t been revoked for a particular timestamp. A non-revocation token contains a cryptographic accumulator signed by the credential issuer, following the signing and proving processes laid out in zk-SAM. This allows for the holder to prove non-revocation of the credential for a particular timestamp, without revealing any extra correlating information. Like current BBS+ signature implementations the pairing-friendly BLS12-381 elliptic curve is used. This approach to proving the non-revocation of a verifiable credential has characteristics that meet the practical requirements for a number of important use cases. Each issued credential must contain two additional signed messages in order to enable revocation support, both represented as opaque 32-byte sca

§ Non-Revocation Token Specification Status: Draft Latest Draft: https://identity.foundation/revocation/non-revocation-token Editors: Andrew Whitehead Brian Richter Participate: GitHub repo File a bug Commit history § Abstract This specification describes a privacy-preserving revocation method for Verifiable Credentials. A Non-Revocation Token that contains a cryptographic accumulator signed by the issuer is used by the holder to prove a Verifiable Credential hasn’t been revoked for a particular timestamp. § Introduction A non-revocation token contains a cryptographic accumulator signed by the

Non-Revocation Token

related reading