Walt.id states its verifier API can verify EBSI-compliant credentials.
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.
Evidence from the source (6 quotes)
- “Below are all features available through v0.4.0 of the identity lib.” source ↗
- “Methods supported: did:key, did:jwk, did:ebsi, did:web and did:cheqd.” source ↗
- “Multiplatform-based, the new logging service enables dynamic reconfigurations, multiple log outputs, and integrations with log aggregator systems supporting various log output formats.” source ↗
- “The walt.id Android Sample Project demonstrates walt.id identity lib’s ability to generate keys, sign text, create Decentralized Identifiers (DIDs), and verify signed content through various algorithms and methods in an Android environment.” source ↗
- “Libs, services, and applications are now grouped in the new walt.id identity project hierarchy:” source ↗
- “We are proud to announce that governments and businesses can use traditional identity verification (IDV) solutions from our IDV partners via our stack.” source ↗
Developer experienceReusable identity VCeID brokeringFeature updateGlobal
5 of 6 facts verified against the source · confidence high · claude-haiku-5-5