VRP Attestation Status — W3C Bitstring Status List binding v0.1
Status: Public draft Date: 2026-06-16
1. Purpose
This document profiles the W3C Bitstring Status List v1.0 as the standards-conformant status and revocation mechanism for VRP Portable Attestations. It fulfils the forward hook in attestations-v0.1 §6, which states that *"if a future VRP version uses BitstringStatusListEntry, the status list MUST follow the W3C Bitstring Status List format completely."*
It does not introduce a new VRP status format. It binds VRP to the W3C standard, constraining only: the issuer (a did:web host domain), the signature (Ed25519, the same key family as VRP signed offers and attestations), the unknown-status fail-safe, the no-guest-data rule, and the credential layer it applies to.
2. Scope — attestations only, not stay offers
This mechanism applies to long-lived credentials: VRP Portable Attestations.
It MUST NOT be applied to the signed verified stay offer (vrp-spec v0.1). A stay offer is ephemeral — it carries a short valid_until and is invalidated by expiry, not by a status list. Revocation infrastructure for a 15-minute credential is unnecessary and MUST NOT be required.
3. credentialStatus in an attestation
A VRP Portable Attestation MAY include a credentialStatus of type BitstringStatusListEntry:
{
"id": "https://villaakerlyckan.se/.well-known/vrp/status/attestations-bitstring-v0.1.json#94",
"type": "BitstringStatusListEntry",
"statusPurpose": "revocation",
"statusListIndex": "94",
"statusListCredential": "https://villaakerlyckan.se/.well-known/vrp/status/attestations-bitstring-v0.1.json"
}
typeMUST beBitstringStatusListEntry.statusPurposeMUST berevocationorsuspension.statusListIndexMUST be a base-10 string encoding an integer ≥ 0, unique within the referenced list.statusListCredentialMUST be an HTTPS URL controlled by the issuer host domain, resolving to aBitstringStatusListCredential.
4. The status list credential
The status list MUST be a BitstringStatusListCredential per the W3C spec, signed by the issuer host domain (Ed25519, did:web):
{
"@context": ["https://www.w3.org/ns/credentials/v2"],
"type": ["VerifiableCredential", "BitstringStatusListCredential"],
"issuer": "did:web:villaakerlyckan.se",
"validFrom": "2026-06-16T00:00:00Z",
"credentialSubject": {
"id": "https://villaakerlyckan.se/.well-known/vrp/status/attestations-bitstring-v0.1.json#list",
"type": "BitstringStatusList",
"statusPurpose": "revocation",
"encodedList": "uH4sIAAAAAAAAA-3BMQ..."
}
}
credentialSubject.typeMUST beBitstringStatusList.credentialSubject.statusPurposeMUST match the entry'sstatusPurpose.encodedListMUST be the multibase base64url (no padding,uprefix) encoding of the GZIP-compressed bitstring. The uncompressed bitstring MUST be at least 16 KB (131,072 bits) — the W3C default minimum for herd privacy.- The credential MUST be Ed25519-signed by the issuer
did:webso verifiers authenticate it without trusting transport alone. - It MUST be served over HTTPS on the issuer host domain, and SHOULD be
no-storeor short-cache so revocations propagate quickly.
5. Verification
A verifier:
- Resolves
statusListCredentialand verifies its signature against the issuerdid:webJWKS. - Decodes
encodedList(multibase → GZIP-inflate → bitstring) and reads the bit atstatusListIndex. - For
statusPurpose: revocation, a set bit (1) means revoked; forsuspension, a set bit means suspended.
Unknown-status fail-safe (carried from attestations-v0.1 §6): if the status list is absent, stale, unreachable, malformed, unsigned, or not controlled by the issuer host domain, the verifier MUST treat the credential status as unknown. Unknown status MUST NOT be converted into either revoked or not-revoked.
6. No-gatekeeper and privacy
- Optional and additive. A VRP attestation verifies standalone (
did:web+ signature). A status check is an additional layer and MUST NOT be a precondition for the protocol or a gate operated by any central party. - Privacy. The bitstring discloses only revoked/not-revoked per index. The ≥16 KB herd minimum means one fetch covers many credentials and the issuer does not learn which credential a verifier checked. The status list MUST NOT contain guest identity, booking identity, or any guest data.
7. Relationship to the transparency log
A status list is mutable by design — revocation flips a bit. This is complementary to, not in conflict with, the append-only transparency log:
- Transparency log — append-only, tamper-evident record that a credential *was issued* (append-only, tamper-evident).
- Status list — current, mutable record of whether a credential *is still valid* (revocation/suspension).
This mirrors the web PKI model (append-only Certificate Transparency logs alongside CRL/OCSP revocation). The two layers answer different questions and both are optional and host-operated.
8. Migration from VRPStatusListEntry
attestations-v0.1 §6 defines an interim VRPStatusListEntry / VRPStatusList shape. Issuers adopting this profile:
- SHOULD migrate
credentialStatusfromVRPStatusListEntrytoBitstringStatusListEntry. - MAY serve both during transition (the legacy
VRPStatusListJSON and theBitstringStatusListCredential). - Verifiers SHOULD prefer
BitstringStatusListEntrywhen present.
9. Conformance
Implementations MUST follow W3C Bitstring Status List v1.0 completely for the entry and credential data model and the encodedList encoding. This profile only adds the VRP constraints in §§3–6 (issuer = did:web host domain; Ed25519 signature; unknown-status fail-safe; no guest data; attestations-only scope).
References
- W3C Bitstring Status List v1.0
- W3C Verifiable Credentials Data Model v2.0
- VRP Portable Attestations: attestations-v0.1 (§6 Status and Revocation)
- VRP Transparency Log: transparency-log-v0.1
- VRP core: v0.1
License
Specification text: dedicated to the public domain under CC0 1.0. Reference code and conformance test vectors: Apache-2.0 (ADR 0007 D7).