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

**URL:** <https://community.mosip.io/t/release-announcement-inji-certify-v1-0-0-alpha-1-is-here/2852>\
**Category:** Inji\
**Tags:** announcement\
**Created:** [August 3, 2026, 9:21am UTC](https://community.mosip.io/t/release-announcement-inji-certify-v1-0-0-alpha-1-is-here/2852 "2026-08-03T09:21:27Z")\
**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 3, 2026, 9:21am UTC](https://community.mosip.io/t/release-announcement-inji-certify-v1-0-0-alpha-1-is-here/2852/1 "2026-08-03T09:21:28Z")

</div>

📢 Dear Community Members,

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

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

Key highlights of v1.0.0-alpha.1:

- OpenID4VCI 1.0 specification alignment (credential endpoint, well-known metadata, authorization flows)
- Credential format transition (`vc+sd-jwt` to `dc+sd-jwt`)
- Addition of a Nonce endpoint - c\_nonce generation + replay attack prevention, Redis-backed with TTL expiry
- Pre-authorized credential offer API — now validates `credential_configuration_id` and claims against issuer metadata
- Configurable JSON-LD context loader with caching - in-memory caching, host allowlisting, and locally bundled W3C contexts. Faster, safer, no more runtime dependency on external hosts!

> **⚠ Note:** This release is **not backward compatible** with the earlier OpenID4VCI draft specifications. The `vc+sd-jwt` format is replaced by `dc+sd-jwt`, and `c_nonce` must now be fetched from the new `/nonce` endpoint instead of the token response. Upgrading is optional but recommended for spec compliance — teams on earlier releases can continue without disruption, with the option to upgrade at a time that suits your roadmap. Please review the Breaking Changes section of the release notes before upgrading.

Refer to our detailed [release notes](https://docs.inji.io/inji-certify/releases/version-1.0.0-alpha.1) to learn more about what Inji Certify 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-certify/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 Certify  
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 13, 2026, 9:22am UTC](https://community.mosip.io/t/release-announcement-inji-certify-v1-0-0-alpha-1-is-here/2852/2 "2026-08-13T09:22:18Z")

</div>

Closed on August 13, 2026, 9:22am UTC

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