For the complete documentation index, see llms.txt. This page is also available as Markdown.

Future Enhancements

The Verifier already covers the core of an OpenID4VP presentation flow today: it creates DID-signed authorization requests, describes the credentials you need with DCQL or DIF Presentation Exchange v2, verifies SD-JWT VC and JWT-VC presentations, honors SD-JWT selective disclosure, and streams session state over SSE. The items below are on the roadmap to extend that surface. They are not implemented yet — they are listed here so you can plan an integration around what exists now rather than what is planned.

Roadmap

  • Enhanced selective disclosure and predicate proofs: SD-JWT selective disclosure — revealing only the claims a verifier requests — is supported today. The roadmap extends this toward predicate proofs, where a holder can prove a statement about a claim (for example, "is over 18" or "salary band is X") without revealing the underlying value, further minimizing data exposure.

  • Zero-Knowledge Proofs (ZKP): Building on predicate proofs, ZKP support would let holders prove specific facts derived from a credential without disclosing the credential's contents at all, improving privacy and regulatory compliance for high-sensitivity use cases.

  • Additional client libraries: Integration today is plain HTTP plus an SSE subscription, so any language works. Planned helper libraries beyond JavaScript/TypeScript would wrap request creation, QR/deep-link rendering, and session streaming to shorten time-to-integration in more ecosystems.

  • Broader DID-method resolution: The Verifier resolves did:web, did:key, and did:jwk today. As the wider Empeiria ecosystem matures, support for resolving additional DID methods — including the EMPE DID method (did:empe) anchored on the EMPE blockchain — is an ecosystem direction. This is not yet available in the Verifier.

Last updated