Roadmap 2025

Here we present the product roadmap for the whole of 'Inji Stack' for the calendar year 2025. Annual product cycle of Inji stack commences in January and concludes in December.

Inji Wallet

Vision

In 2025, Inji Wallet will continue to ensure compatibility with diverse ecosystems by supporting multiple credential formats, such as mDoc/mDL, SD-JWT, and JWT. The wallet will also incorporate privacy-preserving mechanisms such as BBS+, selective disclosure, and one-time credentials, empowering users to retain full control over their personal information. Additionally, the wallet will enable multi-user credential sharing, addressing family-based use-cases such as ration cards and property deeds, further enhancing its versatility and real-world applicability.

The wallet’s roadmap includes critical features like OpenIDVP enhancements for cross-device and same-device flows, Shamir’s secret sharing for secure key recovery, ECC K1 and R1 key support. By enabling the seamless integration of features like credential offer endpoints and pre-authorized code flows (OpenID4VCI), Inji Wallet will cater to real-world use cases with ease.

The mobile and web interfaces of Inji Wallet will support high-performance operations, maintaining accessibility even in low-connectivity environments. With robust user login and profile management features, along with integration of play integrity on Android, the wallet will ensure a scalable, secure, and privacy-focused user experience.

By 2025, Inji Wallet aims to be a reliable, standards-compliant digital wallet, empowering users to manage their credentials while fostering trusted data exchange and seamless interoperability within the verifiable credentials ecosystem.

Inji Mobile

Quarter🗓️
Feature 🛠️
Details 📊
Status 📝
Release 📌
Notes 📖

Q1

iOS Keystore: RSA, ECC R1/K1, Ed25519 Key Generation Support

🟢 Completed

Q1

OpenIDVP : Cross-Device Flow

🟢 Completed

Q1

Support of mDL/mDoc Credentials

🟢 Completed

Q2

Cross-Device Enhancements for Credential Sharing

( OpenIDVP :Verifier Metadata Management)

🟢 Completed

Moved to: Q2

Q2

VC Verifier SDK (Kotlin): ECC K1 Verification Support

🟠 In-progress

v0.17.0

Added to Q2

Q2

Sharing of mDL/mDoc via OpenIDVP

🟠 In-progress

v0.17.0

Added to Q2

Q2

Complaint to Draft 23 of OpenIDVP Spec

🟠 In-progress

v0.17.0

Added to Q2

Q2

WLA login through deep link in iOS

🟠 In-progress

v0.17.0

Added to Q2

Q2

OpenID4VCI Support for credential offer endpoint and pre-authorised code flow

To be planned

v0.18.0

Moved to Q2 from Q3

Q2

Same Device Flow: Multiple credential requests during the presentation (OpenIDVP)

🟠 In-Progress

v0.17.0

Moved to Q2 to Q3

Q3

Support for JWT Credentials

To be planned

v0.19.0

Moved to Q3 from Q4

Q3

Secure Wallet Setup with Key Binding

(SIOP)

To be planned

v0.20.0

Moved to Q3 from Q1

Q3

W3C Data Model 2.0 & SVG Render Method

To be planned

v0.18.0

Moved to Q3 from Q2

Q3

Credential Revocation

To be planned

TBD

Moved to Q3 from Q2

Q3

Wallet Login with Unified Key Management

To be planned

v0.19.0

Moved to Q3 from Q2

Q3

Support for SD-JWT Credentials

To be planned

v0.19.0

Moved to Q3 from Q2

Q4

Secure Key Recovery with Shamir’s Secret Sharing

To be planned

v0.20.0

Moved to Q4 from Q2

Q4

Support for Advanced Cryptographic Keys (ECC R1)

To be planned

v0.19.0

Q4+

Presentation During Issuance

To be planned

v0.20.0

Added to Q4

Q4

Profile Creation Using a Single Credential

To be planned

v0.20.0

Moved to Q4 from Q2

2026

Advanced Privacy Features with BBS+

To be planned

NA

Moved to 2026 from Q3

2026

Android App Security with Play Integrity

To be planned

NA

Moved to 2026 from Q3

2026

Multi-User Family Credentials

To be planned

NA

Q4

Moved 2026

2026

One-Time Use Credentials for Privacy

To be planned

NA

Q4

Moved to 2026

Inji Web

Quarter 🗓️
Feature 🛠️
Details 📊
Status 📝
Release 📌

Q1

User Login & Profile Management

🔵 Planned

v0.12.0

Q1

Unified Key Management for Web & Mobile

🔵 Planned

v0.12.0

Q1

W3C Data Model 2.0 & SVG Render Method

🔵 Planned

v0.13.0

Q2

Secure Key Recovery Using Shamir’s Secret Sharing

🔵 Planned

v0.13.0

Q2

Support for Advanced Cryptographic Keys (ED25519 Signature Support 2018 & 2020)

🔵 Planned

v0.13.0

Q2

Support for Advanced Cryptographic Keys (ECC K1)

🔵 Planned

v0.14.0

Q2

Support for mDoc/mDL Credentials

🔵 Planned

v0.14.0

Q2

CBOR Credential Format Support

🔵 Planned

v0.14.0

Q3

SD-JWT Credential Support

🔵 Planned

v0.14.0

Q3

Same-Device Credential Sharing Flow

🔵 Planned

v0.15.0

Q3

OpenID4VCI Support for credential offer endpoint and pre-authorised code flow

🔵 Planned

v0.15.0

Q3

Credential Revocation

🔵 Planned

v0.15.0

Q4

Advanced Privacy with BBS+ Support

🔵 Planned

v0.16.0

Q4

One-Time-Use Credentials for Privacy

🔵 Planned

v0.16.0

Q4

Multi-User Family Credentials

🔵 Planned

v1.0

Q4

Support for JWT Credentials

🔵 Planned

v1.0

Q4

Support for Advanced Cryptographic Keys (ECC R1)

🔵 Planned

v1.0

Inji Certify

Vision

The goal of Inji Certify for the rear 2025 is to provide a comprehensive and user-centric platform for issuing, managing, and verifying credentials, tailored to meet the diverse needs of individuals, organizations, and issuers. With support for multiple credential formats (e.g., SD-JWT, mDoc/mDL), advanced cryptographic standards (ECC, BBS), and privacy-preserving mechanisms, the platform ensures secure and flexible credential handling.

By enabling features like multi-issuer onboarding, deferred issuance, subject-holder relationship management, and one-click authorization during issuance, Inji Certify addresses real-world scenarios such as sharing family credentials, automating bulk credential generation, and simplifying issuer interactions. The integration of offline capabilities (e.g., printable QR-embedded credentials) and scalable architecture ensures accessibility, even in low-connectivity environments, while maintaining performance benchmarks of up to 1 million credentials per day.

Inji Certify’s vision is to foster trust and interoperability in the digital identity ecosystem, empowering users with control over their credentials while providing issuers with a reliable and standards-compliant platform.

Quarter 🗓️
Feature 🛠️
Details 📊
Status 📝
Release 📌

Q1

Support for ECC K1 & R1

🔵 Planned

Q1

Discovery and Metadata

  • did.json, openid verification to be created during issuer creation

🔵 Planned

Q1

Credential Revocation Mechanism

🔵 Planned

Q1

Credential Formats Support for

  1. SD JWT

  2. mDoc

🔵 Planned

Q1

Pre-authorized Code Flow

🔵 Planned

Q2

Presentation during issuance of Credential

🔵 Planned

Q2

Issuer initiated Credential Issuance

🔵 Planned

Q2

Anon Credential

🔵 Planned

Q3

VC Generation: Create Credentials from the Request Payload

🔵 Planned

Q3

Multi-issuers: Onboarding of multiple issuers

🔵 Planned

Q3

Subject Holder relationship for VC

🔵 Planned

Q3

Allow bulk generation of onetime credentials

🔵 Planned

Q4

Deferred Credential Endpoint

🔵 Planned

Q4

Multi-User Credentials

🔵 Planned

Q4

Issue a physical credential (PDF / Printable)

🔵 Planned

Inji Verify

Vision

Our vision for 2025 is to position Inji Verify as the go-to tool for seamless and secure credential verification. We aim to deliver easily configurable UI components for third-party verifier portals, tailored to meet the diverse needs of organizations across the globe. With support for multiple credential formats (SD-JWT, mDoc/mDL, W3C) and advanced cryptographic standards (ECC), Inji Verify ensures flexible and secure credential handling.

Inji Verify fosters trust and interoperability in the digital identity ecosystem. By introducing features like multi-proof capabilities, QR Based Verifiable Presentation in Same Device, SVG Rendering post VC verification, able to identify revoked credentials during verification, able to support credential correction, verification of documents with multiple QR codes, BLE Based verifiable presentation - Inji Verify will redefine user experience and reliability. With a focus on performance , enhanced design for an intuitive look and feel, and adherence to global standards (Data Model 1.1/2.0), the GA release will set new benchmarks for stability, usability, and excellence in digital verification.

Quarter 🗓️
Feature 🛠️
Details 📊
Status 📝
Release 📌

Q1

Inji Verify SDK (OpenID4VP)

🟠 In-progress

Q2

Inji Verify SDK (Scan)

🟠 In-progress

Q1

OpenIDVP: Same Device Flow (QR code based Verifiable Presentation), Multiple credential requests during the presentation

🟠 In-progress

v0.12.0

Q2

OpenIDVP: Cross Device Flow

🟢 Completed

Q1

Support for Country QR code - CWT Format

🟠 In-progress

Q2

Inji Verify SDK: OpenID4VP- VP Verification component (cross device flow)

🟢 Completed

Q2

Migration of Inji Verify backend from H2 in memory DB to PostgreSQL DB

🟢 Completed

Q1

Verify mDoc and mDL Credentials

🔵 Planned

Q1

Credentials Revocation

🔵 Planned

Q2

Templatizing post-VC verification on Inji Verify (SVG Rendering)

🔵 Planned

Q2

Support Server Side VC Verification: ECC- K1 and R1

🔵 Planned

Q2

Support for verification of W3C VC, SD JWT

🔵 Planned

Q2

Verify document (pdf) with multiple QR Codes

🔵 Planned

Q3

Support for multi proof: Single credential should support multiple proofs

(both embedded and linked)

🔵 Planned

Q3

GA Release:

  1. Support multiple issuers

  2. Support common crypto algorithms

  3. Support various QR codes, VPs

  4. Data Model 1.1, 2.0 VCs

  5. Scalability

  6. Bug Fixes

  7. Performance Testing - 1 mill/day

  8. Security Testing

  9. Test Coverage>80%

  10. Sonar Coverage

🔵 Planned

v1.0

Q3

Credential Correction

🔵 Planned

Q4

Offline Verification SDK

🔵 Planned

Q4

BLE based verifiable presentation

🔵 Planned

Last updated

Was this helpful?