Inji Stack Open Product Call – 15th October 2026

Dear Community Members,

Today’s Inji Open Product Call is cancelled due to low acceptance. Please join us for the next call on 29 October at the usual time. We encourage everyone to participate and bring any questions, doubts, or topics they would like to discuss.

Join the next call: Google Meet meeting

Over the last two Inji Open Product Calls, we have discussed the progress of the Inji 1.0.0 release, the capabilities introduced in our Alpha release, and the areas we are actively working on to strengthen standards compliance and interoperability.

As we continue towards the next release milestone, we would like to share an update on what has been delivered, what is planned for the upcoming Inji 1.0.0-rc.1, and how the community can contribute to shaping our roadmap for the coming year.

Our goal is to continue building an open, standards-aligned, interoperable digital credential ecosystem that meets the needs of developers, adopters, and the wider community.

1. Inji 1.0.0-alpha.1: What has been delivered?

The Alpha release represents an important step towards aligning Inji with the finalized OpenID specifications and improving the foundational capabilities across our wallet and credential infrastructure components.

Inji Mobile Wallet

The Mobile Wallet Alpha release introduces foundational support for OpenID4VCI 1.0 and OpenID4VP 1.0.

Highlights include:

  • Upgrading credential issuance and presentation flows to the finalized OpenID specifications.

  • Introducing DCQL-based credential request processing and selection.

  • Supporting mandatory and optional credential sets in the credential selection experience.

  • Adding support for ECC R1 (ES256) credentials alongside Ed25519.

  • Enhancing credential offer handling through deep links.

  • Improving error handling, automated test coverage, and overall stability.

These changes establish a stronger foundation for standards-compliant credential issuance and presentation.

Release notes: Version 1.0.0-alpha.1 | Inji

Inji Certify

Inji Certify 1.0.0-alpha.1 introduces significant changes to align credential issuance with OpenID4VCI 1.0.

Highlights include:

  • Updating credential issuance endpoints and issuer metadata.

  • Introducing a dedicated nonce endpoint to support nonce generation and replay-attack prevention.

  • Transitioning from vc+sd-jwt to dc+sd-jwt.

  • Strengthening credential request, proof, and claims validation.

  • Improving pre-authorized credential offer handling.

  • Introducing configurable JSON-LD context loading and caching.

  • Improving error handling and issuance reliability.

Important: This release introduces breaking changes to certain APIs and credential formats. Teams upgrading from earlier draft-based implementations should review the release notes before upgrading.

Release notes: Version 1.0.0-alpha.1 | Inji

Inji Web Wallet and Inji Verify

The Alpha release also advances the broader Inji ecosystem, including the Web Wallet and Verify components.

The Web Wallet builds on the shared issuance and presentation foundations, while Verify remains an important component for validating and consuming digital credentials.

Continued work across these components will focus on interoperability, protocol compliance, reliability, and developer experience.

Release notes:

2. Our focus: Working towards VCI and VP conformance

One of our key priorities is achieving conformance against the applicable OpenID4VCI and OpenID4VP conformance test suites.

We are actively working through the gaps identified during conformance testing and interoperability validation.

This includes improvements to:

  • Protocol request and response handling.

  • Credential issuance and presentation flows.

  • Cryptographic processing and validation.

  • Error responses and negative scenarios.

  • Automated testing and regression coverage.

  • Interoperability across relevant Inji modules.

The objective is to make Inji implementations more predictable, interoperable, and reliable for adopters.

We will continue this work in the upcoming RC.1 release and subsequent releases until the applicable conformance requirements are met.

3. Coming next: Inji 1.0.0-rc.1

We are targeting Inji 1.0.0-rc.1 within the next two weeks.

The upcoming release is expected to include further conformance improvements and additional capabilities across relevant modules.

DPoP support

We are working on Demonstrating Proof of Possession (DPoP) support to strengthen the security of token-based authorization flows by binding access-token usage to a cryptographic key held by the client.

PAR support

Pushed Authorization Requests (PAR) support is also planned across relevant modules. PAR allows authorization request parameters to be pushed directly to the authorization server before the authorization flow proceeds.

Digital Credentials API support

We are working towards Digital Credentials API (DC API) support. This will help advance browser-mediated credential interactions and enable further exploration of standardized digital credential requests through compatible wallets and user agents.

Continued quality and conformance improvements

Alongside these features, we will continue addressing conformance gaps, improving automated test coverage, strengthening interoperability, and resolving issues identified during QA.

The final feature scope will be reflected in the RC.1 release notes.

4. Beyond RC.1: mDoc proximity presentation

Looking beyond RC.1, one of the planned areas of development is mDoc proximity presentation based on ISO/IEC 18013-5.

This will expand the presentation mechanisms available in Inji by supporting in-person credential exchange between a holder’s wallet and a compatible reader.

The work involves device engagement, secure session establishment, reader request processing, holder consent, secure data exchange, and session lifecycle management.

We will also need to validate interoperability against compatible reader implementations and ensure that connection failures, cancellations, and other session outcomes are handled correctly.

mDoc proximity support is planned for a subsequent release. We will share more details as the implementation and testing progress.

5. Help shape the Inji roadmap for next year

Inji is an open ecosystem, and community feedback is essential to ensuring that our roadmap addresses real adoption needs.

By the end of this month, we plan to reach out to community members to gather feedback on priorities for the coming year.

We would like to understand:

  • Which features and capabilities should be prioritised?

  • What standards and interoperability requirements are most important to your projects?

  • What challenges are you encountering while integrating Inji?

  • Which credential formats and presentation mechanisms do you need?

  • What improvements would help with performance, scalability, deployment, and operations?

  • What documentation or developer experience improvements would make adoption easier?

  • What additional use cases should we consider?

We encourage community members to start thinking about their requirements and bring their questions, feedback, and suggestions to our upcoming Open Product Calls and roadmap discussions.

Our aim is to make roadmap planning collaborative and ensure that community needs inform our priorities.

6. Explore, test, and contribute

We encourage everyone to review the Alpha release documentation, try the relevant capabilities, and share feedback through the project repositories and community channels.

Your testing, implementation experience, bug reports, and feature requests are valuable inputs as we work towards RC.1 and beyond.

Thank you to all contributors, adopters, and community members who continue to support Inji.

We look forward to working together on the next release milestones and shaping the future of the Inji ecosystem.

Let’s continue building an interoperable digital credential ecosystem together.

Best regards,
Sanchi Singh
On behalf of the Inji Team

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