Feed

Walt.id announces highlights available through 1.2.0 of its identity lib and Enterprise Stack.

Product Update #34 ↗

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.

5 of 5 facts verified against the source · confidence high · claude-haiku-5-5

The update lists a new demo web wallet built on the wallet2 API.

Product Update #33 ↗

What happened

• The update lists batch issuance on Issuer2, letting several credentials go into one offer.
• The update announces guides for 10 industries on eIDAS 2 and the EUDI Wallet.

Why it matters to Signicat

• Walt.id's demo wallets and EUDI certificate profiles overlap with Signicat's Wallet Hub and EUDI readiness positioning, but the update does not claim wallet certification or deployments.

3 of 4 facts verified against the source · confidence high · claude-haiku-5-5

Under eIDAS 2 a very large online platform that requires authentication must also accept the EUDI Wallet as a login option.

eIDAS 2 for Very Large Online Platforms: What Platforms Need to Know ↗

What happened

• The article gives 20 May 2024 as the date Regulation (EU) 2024/1183 entered into force.
• The article states the practical trigger for the platform acceptance obligation is wallet availability at the end of 2026.

Why it matters to Signicat

• Content positions walt.id as a verifier-side provider for platforms, overlapping Signicat's Wallet Hub and EUDI readiness offer.
• Article claims open-source inspectability eases privacy defence; this is walt.id's own claim, not independently established.

3 of 3 facts verified against the source · confidence high · claude-haiku-5-5

Walt.id publishes eIDAS 2 guide for energy and utility suppliers

eIDAS 2 for Energy & Utilities: What Suppliers Need to Know ↗

What happened

• The guide states that eIDAS 2 names both energy and drinking water as sectors that must accept the EUDI Wallet.
• The guide states that municipal and publicly owned utilities must be ready by end of 2026, and commercial suppliers by end of 2027.
• The guide states that micro and small enterprises are exempt from the acceptance obligation.
• The guide describes walt.id Community Stack as open-source issuer, verifier and wallet infrastructure, and Enterprise Stack as the managed offering on top of it.

Why it matters to Signicat

• Content targets Signicat's utility and public-sector EUDI verifier market with a build-versus-buy pitch favouring a standards-compliant provider.
• The guide's deadlines overlap Signicat's EUDI wallet readiness priority for relying parties.

4 of 4 facts verified against the source · confidence high · claude-haiku-5-5

Walt.id announced V1 of its Community and Enterprise Stack, supporting OID4VCI and OID4VP v1.

Product Update #32 ↗

What happened

• Walt.id introduced Crypto2, a re-architected crypto library with pluggable software, device, remote-KMS and HSM (PKCS#11) providers.
• The Enterprise Stack now requires an active license to run, with online or offline activation.
• The post lists breaking changes, including removal of the init-wallet route and move of protocol routes to /v2.

Why it matters to Signicat

• Release adds EUDI-aligned OID4VCI/VP v1 issuer, verifier and wallet components that compete with Signicat Wallet Hub's wallet capabilities.
• Licensing gate and breaking API changes indicate a self-hosted enterprise offering; Signicat impact is limited to developer-segment competition.

4 of 4 facts verified against the source · confidence high · claude-haiku-5-5

Public hospitals, national health services and public insurers must accept the EUDI Wallet by the end of 2026.

eIDAS 2 for Healthcare: What Providers, Insurers and Health Authorities Need to Know ↗

What happened

• The article states that private providers have until the end of 2027 to accept the EUDI Wallet.
• The article states that walt.id Community Stack provides open-source issuer, verifier, and wallet infrastructure.

Why it matters to Signicat

• The guide positions walt.id as a 'buy infrastructure' option for healthcare verifiers and issuers, a direct overlap with Signicat's wallet and eID Hub offering in healthcare; relevance is moderate because it is a how-to guide without named customers.
• The content is generic eIDAS 2 education with a vendor product section; no pricing, customer or benchmark claims.

3 of 3 facts verified against the source · confidence medium · claude-haiku-5-5

Transport operators classified as public sector bodies face the wallet acceptance deadline first, with private operators a year later.

eIDAS 2 for Transport & Mobility: What Operators Need to Know ↗

What happened

• The article states that micro and small enterprises with fewer than 50 employees and at most €10 million turnover are exempt from the acceptance obligation.

Why it matters to Signicat

• Content is educational with no named competitor product or customer; low direct competitive threat.

2 of 3 facts verified against the source · confidence high · claude-haiku-5-5

The guide states that eIDAS 2 requires public authorities to accept the EUDI Wallet as soon as wallets are available, at the end of 2026.

eIDAS 2 for the Public Sector: What Governments Need to Know ↗

What happened

• The guide lists a European Business Wallet proposal dated 19 November 2025 as still under development.

Why it matters to Signicat

• The guide is generic explainer content for public-sector buyers on the EUDI deadline that overlaps Signicat's EUDI Wallet readiness priority, with no product or customer claim.
• The 'build apps, buy infrastructure (recommended)' framing positions a standards-compliant identity-layer provider as the default buying choice for public bodies, which Signicat's Wallet Hub could be measured against.

2 of 2 facts verified against the source · confidence high · claude-haiku-5-5

The guide defines a verifier as a government or business that requests and validates credential attributes from an EUDI Wallet.

eIDAS 2 Verifier Requirements: How to Verify Credentials Under eIDAS 2 ↗

What happened

• The guide states that every verifier must register with the national Registrar before requesting attributes, citing Regulation (EU) 2025/848.
• The guide lists a three-path integration model and marks buying the verification infrastructure as recommended.

Why it matters to Signicat

• The guide frames verifier compliance as a buy decision for relying parties, which targets Signicat's Wallet Hub and eID-brokering buyers in Nordics and DACH.
• Walt.id's claims on automated EU Trusted List validation and certificate lifecycle management are vendor-stated and uncorroborated here.

3 of 3 facts verified against the source · confidence high · claude-haiku-5-5

Walt.id publishes eIDAS 2 guide for banks on wallet SCA and acceptance

eIDAS 2 for Financial Services: What Banks Need to Know ↗

What happened

• The guide states that eIDAS 2 requires banks, fintechs, and payment institutions to accept the EUDI Wallet for customer authentication by the end of 2027.
• The guide states that the European Commission published TS12 v1.0 on 5 December 2025 as the specification for wallet-based SCA.
• The guide states that micro and small enterprises (fewer than 50 employees and at most €10 million annual turnover) are exempt from the acceptance obligation.

Why it matters to Signicat

• Content is generic educational guidance with a PDF lead-capture form; it names no Signicat product.

3 of 3 facts verified against the source · confidence high · claude-haiku-5-5

Walt.id reports OID4VCI v1 issuer2 service and OID4VCI v1 wallet support in its Enterprise Stack releases 0.19.0 and 0.20.0.

Product Update #29 ↗

What happened

• Walt.id reports a new Trust Registry service for managing ETSI trust lists (TSL, LoTE).
• Walt.id reports that legacy VICAL and certificate-store APIs were removed in favor of a new service model.

Why it matters to Signicat

• Open-source/developer-tooling release notes; limited direct overlap with Signicat's commercial eID Hub or Wallet Hub offerings, though EUDI trust-list and OID4VCI coverage is relevant to Wallet Hub competitive positioning.
• Breaking changes to VICAL and X.509 APIs indicate migration friction for existing walt.id clients.

3 of 3 facts verified against the source · confidence high · claude-haiku-5-5

The case study is a vendor-published account of NDID's use of walt.id's Community Stack for a Thai digital identity platform.

Digitizing Thailand’s National Identity Infrastructure — walt.id Case Studies ↗

What happened

• The case study states a roll-out to 20 Million+ consumers and 5-6 major banks, with go-live listed as 2025-2026.
• The case study states the Issuer, Wallet and Verifier are in production, a claim attributed to the vendor and not independently verified.

Why it matters to Signicat

• A national wallet deployment with banks on an open-source stack is a reference point in Asia-Pacific, outside Signicat's core markets.
• The piece promotes open-source ownership and no vendor lock-in, a counter-narrative to proprietary platform positioning.

3 of 3 facts verified against the source · confidence high · claude-haiku-5-5

Walt.id ships 0.18.0 with OIDC enterprise auth and zero-retention mode

Product Update #28 ↗

What happened

• Walt.id lists 0.18.0 of its identity lib and Enterprise Stack release highlights, including CWT support for TokenStatusList and a Digital Credential API test app.
• The Enterprise Auth API now supports OIDC as an authentication flow, including external role mapping from identity providers such as Keycloak.
• A configurable zero-retention mode for PII in issuance and verification sessions is introduced; when enabled, session data is not persisted beyond the immediate transaction.
• TokenStatusList support is upgraded to IETF Draft 15, with changed status value ranges and compression behaviour.
• Annex C (DC API) flow support has been integrated into the Enterprise Verifier2 Service.
• Dependency upgrades include Kotlin, KotlinCrypto, nimbus-jose-jwt and Next.js security patches.

Why it matters to Signicat

• Enterprise OIDC auth and zero-retention mode target enterprise authentication and data-minimisation buyers that overlap with Signicat authentication and privacy positioning; overlap is moderate, as the source describes a developer release rather than a commercial launch.
• Annex C DC API support and the Digital Credential API test app indicate walt.id work on browser-based credential presentation, relevant to Signicat Wallet Hub presentation flows.

6 of 6 facts verified against the source · confidence high · claude-haiku-5-5

Walt.id announced a new verifier 2 API with OID4VP v1 support in its Community Stack, to replace the current verifier by Q2 2026.

Product Update #26 ↗

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.

5 of 5 facts verified against the source · confidence high · claude-haiku-5-5

Walt.id announced an integration letting governments and businesses operate AWS Key Management Service with the walt.id stack.

AWS KMS integration ↗

What happened

• Keys for digital identity wallets created via walt.id wallet SDKs and APIs are created and stored in AWS KMS.
• Signatures for credential issuance and presentation are created inside AWS KMS when AWS is used as external KMS.
• The integration has been open-sourced via the Community Stack.

Why it matters to Signicat

• The integration targets a key-custody gap for wallet and issuance deployments that run on AWS KMS, relevant to Signicat's Wallet Hub and EUDI wallet work.
• Open-sourcing the integration lowers switching cost for developers already on walt.id, a competitive pressure on developer adoption.

4 of 4 facts verified against the source · confidence high · claude-haiku-5-5

The update states that walt.id launched the Enterprise Stack, the AWS KMS integration, and OpenID4VC library improvements in the month.

Product Update #20 ↗

What happened

• Walt.id states that the Issuer API can sign and issue credentials using keys stored in AWS KMS.
• Walt.id states that the Wallet API can store and manage holder keys via the AWS KMS integration.
• The update lists utility objects OpenID4VC, OpenID4VCI, and OpenID4VP for OpenID protocol data transformations, available through identity lib v0.9.0.
• Walt.id describes The Enterprise Stack as its most powerful product, built for businesses and governments to offer digital ID and wallet solutions at scale.

Why it matters to Signicat

• AWS KMS key support for issuance and holder wallets is a material feature for enterprise wallet deployments that Signicat's Wallet Hub competes against.
• The Enterprise Stack launch is a product positioning move toward governments and enterprises, overlapping Signicat's wallet and eID Hub offerings; details are not in this article.

5 of 5 facts verified against the source · confidence medium · claude-haiku-5-5

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.

Product Update #17 ↗

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.

4 of 4 facts verified against the source · confidence high · claude-haiku-5-5

Walt.id states its verifier API can verify EBSI-compliant credentials.

Product Update #15 ↗

What happened

• Walt.id released a feature and config system for its API services in v0.4.0 of the identity lib.
• Walt.id lists did:key, did:jwk, did:ebsi, did:web and did:cheqd as supported DID methods for issuance.
• Walt.id added a multiplatform logging service with dynamic reconfiguration and structured logging.
• Walt.id published an Android sample project demonstrating key generation, signing and DID creation.

Why it matters to Signicat

• Release is an open-source developer toolkit update with EBSI and DID method coverage; limited direct overlap with Signicat's commercial eID brokering or signing lines.
• The post states an ID verification integration offering via IDV partners, which overlaps with Signicat document IDV positioning on a generic level.

5 of 6 facts verified against the source · confidence high · claude-haiku-5-5

Walt.id announced that governments and businesses can use traditional IDV solutions from its IDV partners via the walt.id stack.

ID Verification integrations ↗

What happened

• Verified users can receive identity credentials in VC, mdoc or SD-JWT formats, or soulbound tokens on EVM-compatible wallets.
• On blockchain ecosystems, only a reference ID is placed in token metadata rather than personal data.

Why it matters to Signicat

• Walt.id's approach overlaps Signicat's document IDV and Wallet Hub offerings by bridging IDV results into reusable credentials, a limited but direct overlap.
• The post names no IDV partners, customers, or deployments, so market traction cannot be assessed from this source.

3 of 3 facts verified against the source · confidence medium · claude-haiku-5-5

Walt.id adds external KMS integrations for wallet keys and signatures

KMS INTEGRATIONS ↗

What happened

• Walt.id announced that governments and businesses can now operate external KMS providers such as Hashicorp Vault and Oracle Cloud together with the walt.id stack.
• Walt.id states that keys for digital identity wallets are created and stored in the external KMS environment.
• Walt.id states that issuance and presentation signatures are created inside the KMS provider's environment.
• Walt.id states that all KMS integrations are open-sourced via its Community Stack.

Why it matters to Signicat

• Walt.id's KMS integration addresses key custody for wallets and signing, a capability area adjacent to Signicat's Wallet Hub and trust services; the post itself makes no claim about Signicat.

4 of 4 facts verified against the source · confidence high · claude-haiku-5-5

Walt.id announced that Microsoft ID Credentials can be used within its open-source ecosystem starting on the post date.

Microsoft Entra Verified ID integration ↗

What happened

• The integration was open-sourced via The Community Stack.

Why it matters to Signicat

• Low direct overlap with Signicat's core eID brokering, IDV and signing lines; relevance is limited to verifiable-credential interoperability with a Microsoft ecosystem.
• Open-source, self-hosted positioning may compete with Signicat's wallet and orchestration offers for developers building VC issuance and verification.

2 of 2 facts verified against the source · confidence high · claude-haiku-5-5

Walt.id published a product update reporting added support for Microsoft Entra Verified ID credential issuance and verification.

Product Update #12 ↗

What happened

• Walt.id reports that user accounts in its wallet API and web wallet can now be managed via any external OIDC provider.
• Walt.id lists DID methods including did:key, did:jwk, did:web, did:ebsi, did:iota and did:cheqd as available through its DID lib or API.
• Walt.id describes a compliance service for web3 identity verification with reusable KYC, created with a consortium including IOTA, IDnow, bloom wallet and SPYCE.

Why it matters to Signicat

• Feature list covers OID4VC issuance and verification and W3C/SD-JWT credentials, overlapping Signicat's Wallet Hub reusable-credential scope at developer-library level.
• Post is a self-described feature roundup of an open-source identity library; no customer, pricing or market-entry evidence is given.

4 of 4 facts verified against the source · confidence high · claude-haiku-5-5

Walt.id announced a new SD-JWT library for Kotlin, Java, and JavaScript.

Walt.id goes Multi-Platform ↗

What happened

• The library is open source under Apache 2.
• Walt.id plans to offer its full SSI Kit and other products in these languages and add Rust, Go and others.

3 of 3 facts verified against the source · confidence high · claude-haiku-5-5