Walt.id announces highlights available through 1.2.0 of its identity lib and Enterprise Stack.
What happened
- Issuer2 can verify key attestations and a credential configuration can require one with key_attestations_required.
- Wallet2 supports batch issuance requesting several copies of a credential, each bound to its own holder key.
- Issuer2 can require PAR via requirePushedAuthorizationRequests; default is false.
- A walt.id demo shows the Verifier API requesting a credential from Google Wallet.
Why it matters to Signicat
- Feature release adds issuer-side controls (key attestation, mandatory PAR) relevant to wallet issuance interoperability; a competitor build, not a Signicat event.
- Google Wallet verifier demo indicates walt.id interoperability work with a major wallet; demo-only, no customer or availability claim.
Evidence from the source (6 quotes)
- “Issuer2 can now verify a key attestation carried in a JWT proof or sent as a standalone attestation proof, and a credential configuration can require one with `key_attestations_required`.” source ↗
- “One receive call can select offered credential configurations and request several copies, each bound to its own holder key.” source ↗
- “Set `requirePushedAuthorizationRequests` to `true` when you create or update an Issuer2 service and wallets must post the authorization parameters to the pushed authorization endpoint first.” source ↗
- “This demo shows interoperability between the walt.id Verifier API and Google Wallet.” source ↗
- “Require Key Attestations in Issuer2” source ↗
- “walt.id Verifier x Google Wallet – Demo showcasing the request of a digital credential from the Google Wallet” source ↗
EUDI wallet eIDAS 2Developer experienceReusable identity VCFeature updateProduct launchGlobal
5 of 5 facts verified against the source · confidence high · claude-haiku-5-5