# Release Announcement : Inji verify v1.0.0-alpha.1 is here!

**URL:** <https://community.mosip.io/t/release-announcement-inji-verify-v1-0-0-alpha-1-is-here/2853>\
**Category:** Release\
**Tags:** announcement, inji\
**Created:** [August 6, 2026, 4:38am UTC](https://community.mosip.io/t/release-announcement-inji-verify-v1-0-0-alpha-1-is-here/2853 "2026-08-06T04:38:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![likhitha\_j](https://dub1.discourse-cdn.com/flex017/user_avatar/community.mosip.io/likhitha_j/32/647_2.png) [@likhitha\_j](https://community.mosip.io/u/likhitha_j)\
**Post date:** [August 6, 2026, 4:38am UTC](https://community.mosip.io/t/release-announcement-inji-verify-v1-0-0-alpha-1-is-here/2853/1 "2026-08-06T04:38:28Z")

</div>

📢 Dear Community Members,

We are excited to announce the release of **Inji verify v1.0.0-alpha.1** , a major milestone as we move from the OpenID4VP draft specifications to the finalized [OpenID4VP 1.0](https://openid.net/specs/openid-4-verifiable-presentations-1_0.html) specification! 🎉

This release introduces enhancements, new features along with **breaking changes** to align with the OpenID4VP 1.0 specification.

> **⚠ Note:** This release **does not maintain full backward compatibility** with draft specification implementations. Limited support for Presentation Definition (PD) based sessions is retained on result-fetch endpoints only, allowing existing integrations to keep working through the transition. **Upgrading is optional but recommended** for teams ready to align with the finalized OpenID4VP 1.0 specification. Earlier ‘Inji Verify’ releases built on draft specifications remain fully functional, and can be continued without disruption, with the option to upgrade at a time that suits your roadmap.

The core change is the migration from Presentation Exchange (PEX) to **[DCQL](https://openid.net/specs/openid-4-verifiable-presentations-1_0.html#section-6)**[(Digital Credentials Query Language)](https://openid.net/specs/openid-4-verifiable-presentations-1_0.html#section-6)

**Key Highlights**

- **Stronger holder proof** — `require_cryptographic_holder_binding` lets verifiers demand cryptographic proof of holder possession for both SD-JWT VC and LDP\_VC presentations
- **Wider SD-JWT compatibility** — both `vc+sd-jwt` and `dc+sd-jwt` format identifiers are accepted
- **Replay protection** — KB-JWT `nonce` and `aud` claims are validated on every SD-JWT submission
- **Tamper-resistant sessions** — VP request expiry and duplicate submissions are now enforced server-side
- **Spec-aligned protocol fields** — Full field-level details [API Documentation](https://docs.inji.io/inji-verify/api/api-changes)

Refer to our detailed [release notes](https://docs.inji.io/inji-verify/releases/version-1.0.0-alpha.1) to learn more about what Inji Verify v1.0.0-alpha.1 brings to the community.

These new features will be available in the Collab environment soon for you to try. Stay tuned for further announcements.

For comprehensive information, take a moment to explore our [documentation](https://docs.inji.io/inji-verify/overview).

Thank you for being part of this exciting journey with us! Keep an eye out for future updates and stay engaged with the Inji community.

Warm Regards,  
Likhitha R L  
Product Owner - Inji Verify  
On behalf of the INJI Team

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex017/uploads/mosip1/original/1X/f60a343830fe848c9a68e2d1cc654d0cb7fbbaf2.svg) [@system](https://community.mosip.io/u/system)\
**Post date:** [August 16, 2026, 4:38am UTC](https://community.mosip.io/t/release-announcement-inji-verify-v1-0-0-alpha-1-is-here/2853/2 "2026-08-16T04:38:29Z")

</div>

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.