Search results

Clarify bit-to-byte ordering in bitstring serialization

Status: Open.

#211 In w3c/vc-bitstring-status-list;

· oriolcanades opened on Jan 30, 2026

Broken links in Bitstring Status List v1.1

Status: Open.

#210 In w3c/vc-bitstring-status-list;

· dontcallmedom-bot opened on Aug 18, 2025

information that gets embedded in the compressed bitstring (GZIP)

Status: Open.

#209 In w3c/vc-bitstring-status-list;

· adeinega opened on Jul 19, 2025

a decompression bomb and maximumNumberOfEntries

Status: Open.

#208 In w3c/vc-bitstring-status-list;

· adeinega opened on Jul 17, 2025

Add table for mitigations that increase privacy when using revocation lists

Status: Open.

#207 In w3c/vc-bitstring-status-list;

· msporny opened on Jun 3, 2025

Add privacy consideration regarding k-anonymity degradation over time

editorial

Status: Open.

#206 In w3c/vc-bitstring-status-list;

· msporny opened on Jun 3, 2025

Suggested improvement for using ZKPs to prevent the revocation index from being revealed to the verifier

enhancementNew feature or requestNew feature or request

future

normativeThe item is normative in nature.The item is normative in nature.

Status: Open.

#203 In w3c/vc-bitstring-status-list;

· kdenhartog opened on Apr 22, 2025

Alternative compression algorithms

enhancementNew feature or requestNew feature or request

future

normativeThe item is normative in nature.The item is normative in nature.

Status: Open.

#202 In w3c/vc-bitstring-status-list;

· daniel-dewa opened on Mar 27, 2025

The explainer needs more clarity around example bitstring list I am unable to decode the example bitstring status list

editorial

future

Status: Open.

#201 In w3c/vc-bitstring-status-list;

· mjaferDo opened on Mar 12, 2025