> For the complete documentation index, see [llms.txt](https://docs.cheqd.io/product/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cheqd.io/product/studio/status-lists/bitstring-status-list.md).

# Bitstring Status List

## Get started

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;">Create Bitstring Status List</mark></td><td>Create a Bitstring Status List on cheqd as a DID-Linked Resource</td><td><a href="/product/studio/status-lists/bitstring-status-list/create-status-list.md">Create Bitstring Status List</a></td></tr><tr><td><mark style="color:blue;">Update Bitstring Status List</mark></td><td>Update a Bitstring Status List to revoke/suspend credentials</td><td><a href="/product/studio/status-lists/bitstring-status-list/update-status-list.md">Update Bitstring Status List</a></td></tr><tr><td><mark style="color:blue;">Check Bitstring Status List</mark></td><td>Check whether a specified indices is revoked, suspended, unsuspended or valid</td><td><a href="/product/studio/status-lists/bitstring-status-list/check.md">Check Bitstring Status List</a></td></tr><tr><td><mark style="color:blue;">Search Bitstring Status List</mark></td><td>Search for specific entries in the Status List, traversing its history</td><td><a href="/product/studio/status-lists/bitstring-status-list/search.md">Search Bitstring Status List</a></td></tr></tbody></table>

## Understanding Bitstring Status List

The Bitstring Status List supported in cheqd Studio utilise [bitstrings](https://w3c-ccg.github.io/vc-status-list-2021/#conceptual-framework) to represent whether a Verifiable Credential has been suspended/revoked or not. A bitstring can be thought of as a long list of 1s and 0s, where, if the binary value of the position in the list is 1 (one), the [verifiable credential](https://w3c-ccg.github.io/vc-status-list-2021/#dfn-verifiable-credentials) is revoked, if it is 0 (zero) it is not revoked.

![Graphic showing the StatusList2021 bitstring](https://3569764573-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPVAMvpKH7PYzvXA6u6Cn%2Fuploads%2Fgit-blob-2492fcec68cad93f0f40cb0c328ba0f137188ffd%2FStatusList21%20Bitstring.png?alt=media)

***Figure 1**: Graphic showing the Bitstring Status List bitstring*

Each issued Credential correlates with a position and index on the bitstring, so that a verifier will be able to correlate the value within the Credential against the public bitstring to ascertain whether the Credential has been revoked or not, using a [validate algorithm](https://w3c-ccg.github.io/vc-status-list-2021/#validate-algorithm) as well as a [bitstring expansion algorithm](https://w3c-ccg.github.io/vc-status-list-2021/#bitstring-expansion-algorithm).

### Where is the StatusList usually published?

The issuer keeps a bitstring list of all Verifiable Credentials it has issued. The Status List is usually published by the issuer **in the format of its own Verifiable Credential.** This Verifiable Credential is generally hosted publicly on a centralised server or domain to enable third-party read-access.

### Where does cheqd store the Status List?

cheqd stores each Status List and subsequent entries on-ledger as [DID-Linked Resource](/product/architecture/adr-list/adr-002-did-linked-resources.md) versions. This has notable benefits, including the provenance, legitimacy and security of the Status List. For a full list of benefits, see [the context for creating DID-Linked Resources](/product/studio/did-linked-resources/understanding-dlrs/context.md).


---

# 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.cheqd.io/product/studio/status-lists/bitstring-status-list.md?ask=<question>&goal=<user_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.