Credential Workbench · T544

VC 2.0 Issuance Composer

Compose a W3C Verifiable Credential 2.0, sign it client-side with an eddsa-jcs-2022 Data Integrity proof over an ephemeral did:key, verify the signature in-page, and export the signed credential plus an OCG Standard §23 vc-2.0 input-attestation block ready to pointer into a chain's policy_parameters.

VC 2.0 eddsa-jcs-2022 Zero PII Client-Side

🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.

⚠ This credential is self-issued: the signing key is generated in your browser (or pasted by you) and is not anchored to any external identity registry. A verified signature proves the credential was not altered after signing and that it was signed by whoever holds that key; it is not, by itself, identity assurance. See the credential workbench guide for what a receipt does and does not attest.

Credential Fields

Subject id (DID or any identifier string)

Credential type (appended to VerifiableCredential)

Valid from

Valid until

§23 JSON pointer (where this attestation's claims would sit in a consuming chain's policy_parameters)

Claim key	Value

Advanced: paste your own Ed25519 signing key (JWK) instead of an ephemeral key

Signed Verifiable Credential 2.0

OCG §23 vc-2.0 Input-Attestation Block

Embed the exact claims object shown below at inside a chain's policy_parameters, and add this whole block to that chain's input_attestations[] array — the §23 verifier will recompute the digest and check the embedded proof.

OCG Receipt of the Issuance Activity