> For the complete documentation index, see [llms.txt](https://docs.toolkit.equs.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.toolkit.equs.ai/docs/revocation/overview.md). # Overview Learn how credential revocation works, how Status Lists are used, and what setup is required. Credential revocation invalidates a previously issued Verifiable Credential. Once revoked, the credential remains in the Holder's wallet, but Verifiers no longer accept it. The wallet also shows the revoked status to the Holder. ### How it works The platform implements the [IETF Token Status List](https://datatracker.ietf.org/doc/draft-ietf-oauth-status-list/) specification. Each Issuer gets one or more **Status Lists**: compact bitstrings where every credential the Issuer has issued occupies one index. Revoking a credential means flipping its bit. The platform publishes those lists as **Status List Tokens** at a URL carried inside each credential. To check a credential, a Verifier fetches that token and reads the one bit it cares about. Two consequences follow, and they're the point of the design: * **No request reaches your systems.** The token is a static, cacheable artifact served by the platform, so your infrastructure is never in the verification path and you don't have to be reachable, or even aware, for a Verifier to check a credential you issued. * **The fetch says little about the Holder.** A Status List covers many credentials at once, so fetching it doesn't reveal which one is being checked, and the entries themselves are anonymized indices with no personal data in them. ### Setup No additional configuration is required beyond the standard issuance setup. Status Lists are provisioned automatically for each Issuer. Multiple Status Lists can exist under a single Issuer when needed. Every credential issued through the platform already carries the metadata a Verifier needs, which Status List to look at, and which index in it. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.toolkit.equs.ai/docs/revocation/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.