Walt.id states that v0.6.0 of its identity lib adds support for SD-JWT VC and mDL credentials via its issuer, verifier and wallet API services using OID4VC/VP.
What happened
- Walt.id states that OID4VC session data can be stored in a distributed manner using solutions like Redis, enabling multiple issuer or verifier instances.
- Walt.id states that the issuer metadata key credentials_supported was renamed to credential_configurations_supported and restructured from an array to an object.
- Walt.id states that the verifier endpoint field policies was renamed to policyResults.
Why it matters to Signicat
- SD-JWT VC and mDL support on OID4VC is a feature-level move in the open-source wallet/issuer toolkit space, relevant to Signicat's Wallet Hub and EUDI work but not a market-facing commercial event.
Evidence from the source (4 quotes)
- “This enables you to run multiple instances of the issuer or verifier service while sharing the OID4VC session data among them.” source ↗
- “the key `credentials_supported` has been updated to `credential_configurations_supported`. Additionally, the data associated with this key is now structured as an object instead of an array.” source ↗
- “has been renamed to `policyResults` .” source ↗
- “Issue, receive, present and verify SD-JWT VC credentials via our issuer, verifier and wallet API services using the OID4VC/VP protocol.” source ↗
Reusable identity VCEUDI wallet eIDAS 2Developer experienceFeature updateGlobal
4 of 4 facts verified against the source · confidence high · claude-haiku-5-5