-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
GITBOOK-299: change request with no subject merged in GitBook
- Loading branch information
1 parent
1a85ebe
commit 0bea3d2
Showing
11 changed files
with
318 additions
and
32 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
23 changes: 23 additions & 0 deletions
23
credential-service/status-lists/status-list-v2021/README.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
# Status List v2021 | ||
|
||
## Get started | ||
|
||
<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><mark style="color:blue;">Create Status List v2021</mark></td><td>Create a Status List v2021 on cheqd as a DID-Linked Resource</td></tr><tr><td><mark style="color:blue;">Update Status List v2021</mark></td><td>Update a Status List v2021 to revoke/suspend credentials</td></tr><tr><td><mark style="color:blue;">Check Status List v2021</mark></td><td>Check whether a specified indices is revoked, suspended, unsuspended or valid</td></tr><tr><td><mark style="color:blue;">Search Status List v2021</mark></td><td>Search for specific entries in the Status List, traversing its history</td></tr></tbody></table> | ||
|
||
## Understanding Status List v2021 | ||
|
||
The Status List v2021 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. | ||
|
||
 | ||
|
||
_**Figure 1**: Graphic showing the StatusList2021 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](../../../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](../../did-linked-resources/understanding-dlrs/context.md). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
File renamed without changes.
16 changes: 16 additions & 0 deletions
16
credential-service/status-lists/token-status-list/README.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
# Token Status List | ||
|
||
## Get Started | ||
|
||
<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Create Token Status List</strong></mark></td><td>Create a Token Status List JWT or CWT as a DID-Linked Resource on cheqd</td></tr><tr><td><mark style="color:blue;"><strong>Update Token Status List</strong></mark></td><td>Update a Token Status List JWT or CWT as a new DID-Linked Resource version on cheqd</td></tr></tbody></table> | ||
|
||
## Understanding Token Status List | ||
|
||
Token Status List is a specification from the Internet Engineering Task Force, using JSON or CBOR encoded sets of bits and wrapping these as either a JSON Web Tokens (JWTs) or CBOR Web Tokens (CWTs), to comprise a full status list. | ||
|
||
The specification may be found below: | ||
|
||
{% embed url="https://www.ietf.org/id/draft-ietf-oauth-status-list-02.html" %} | ||
IETF Token Status List | ||
{% endembed %} | ||
|
Oops, something went wrong.