Walt.id announced a new verifier 2 API with OID4VP v1 support in its Community Stack, to replace the current verifier by Q2 2026.
What happened
- Walt.id stated that OID4VP v1.0 is not yet supported in its wallet or demo apps.
- Walt.id added a configurable JSON→CBOR mapping layer for mDoc namespaces.
- Walt.id published a demo portal and JS components for verification flows using the Digital Credentials API.
- Walt.id added session PII retention and auto-purge controls to its Enterprise Stack.
Why it matters to Signicat
- Verifier-side OID4VP v1 and Digital Credentials API support is relevant to EUDI-wallet presentation flows, a capability area in Signicat's Wallet Hub scope; impact on Signicat's roadmap is not established by this source.
Evidence from the source (5 quotes)
- “Note: OID4VP v1.0 is not yet supported in the wallet or demo apps.” source ↗
- “A configurable JSON→CBOR mapping layer was added with namespace builders, typed namespace data, and recursive translators” source ↗
- “We’ve also published a demo portal and JS components to make building verification flows with walt.id and the Digital Credentials API easier.” source ↗
- “Configurable issuer/verifier session retention via `data-retention.conf` and the `data-retention` feature flag, including scheduled auto-purge, dry-run mode, and logging to limit stored PII.” source ↗
- “Use the new Verifier 2 API to verify credentials via OID4VP v1 and the Digital Credentials API.” source ↗
EUDI wallet eIDAS 2Developer experienceReusable identity VCData sovereignty privacyFeature updateProduct launchGlobal
5 of 5 facts verified against the source · confidence high · claude-haiku-5-5