Skip to content
Registry StackDocsv0.20.1

evidence verify-presentation command reference

View as Markdown

Re-verify one stored holder-bound presentation offline against a pinned key set.

This page is generated from the public Clap command tree. Hidden implementation commands are omitted.

Re-verify one stored holder-bound presentation offline against a pinned key set. The named file is one compact SD-JWT VC serialization carrying the holder’s key-binding JWT after its last tilde, so the proof is never a separate input. Naming the input states its shape: a stored credential that ends in a trailing tilde offers no proof of possession and is refused here rather than verified without one. Success proves the presenter held the confirmation key’s private key when the key-binding JWT was signed. It does not prove that the presentation is fresh, single-use, or unreplayed: the expected challenge is compared, never consumed, and this command retains no state between runs, so the same file verifies again under the same policy. Retiring a challenge belongs to the relying party’s own challenge lifecycle.

evidence verify-presentation [OPTIONS] --sd-jwt-vc-presentation <SD_JWT_VC_PRESENTATION> --jwks <JWKS> --policy <POLICY>
OptionAlways requiredDefaultValuesEnvironmentDescription
--sd-jwt-vc-presentation <SD_JWT_VC_PRESENTATION>Yesn/an/an/aStored compact SD-JWT VC presentation file
--jwks <JWKS>Yesn/an/an/aPinned trusted JWKS document. This file is the complete trust set
--policy <POLICY>Yesn/an/an/aHolder-bound relying-procedure verification policy document
--at <AT>Non/an/an/aVerification instant as strict RFC 3339 UTC; system time by default
--runtime <RUNTIME>No/etc/registry-evidence/runtime.yamln/aREGISTRY_EVIDENCE_RUNTIMEOne closed operator runtime file that binds the governed bundle
-h, --helpNon/an/an/aPrint help (see a summary with ‘-h’)

Run npm run generate from docs/site after changing a public command, argument, option, default, environment binding, or help description.