> For the complete documentation index, see [llms.txt](https://docs.empe.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.empe.io/develop/verifier/future-enhancements.md). # 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. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.empe.io/develop/verifier/future-enhancements.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.