Drafts vs credentials
Drafts
A draft is a separate, editable resource representing the initial state of a verifiable credential (VC) that can be created, updated, and modified without requiring a signature. The draft state allows you to freely define and refine credential claims before issuing the final, signed VC.
Drafts are particularly useful in scenarios such as:
- Multi-step approval processes: When a credential needs to be reviewed by multiple stakeholders.
- Incomplete data: When you have partial information and need to update the credential later.
Drafts offer flexibility to make changes such as:
- Modifying claims (fields and values).
- Updating annotations or metadata.
- Adjusting labels or human-readable titles.
A draft is essential during the credential creation process since it allows for experimentation and adjustment before final issuance.
Credentials
Once a draft is finalized, it can be issued as a VC. A VC can exist in two states:
- Unsigned: Exported from a draft but not yet signed.
- Signed: Issued and cryptographically signed.
The lifecycle of a credential typically follows these steps:
- Creating a draft
- Updating the draft as needed
- Issuing a draft that does the following under the hood:
- Exports the draft as an unsigned VC
- Signs the unsigned VC to create a signed VC
- Imports the signed VC
Once the VC is issued:
- It is signed and no longer modifiable.
- It can be presented to verifiers for validation.
- It can be used as part of a Verifiable Presentation (VP).
Differences between drafts and issued credentials
Feature | Draft | Issued Credential (VC) |
---|---|---|
Signature Requirement | Unsigned | Signed using a private key |
Mutability | Can be updated and modified | Immutable after issuance |
Intended Use | For preparing and refining claims | For sharing, verifying, and validation |
Further reading
- Learn how to create a draft.
- Learn how to update a draft.
- Learn how to issue a credential.