Roadmap 2025

Here we present the product roadmap for the whole of 'Inji Stack' for the calendar year 2025.

The quarters are defined as follows:

• Q1: Jan'25 – Mar'25

• Q2: Apr'25 – Jun'25

• Q3: Jul'25 – Sep'25

• Q4: Oct'25 – Dec'25

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 📌
Q1	Cross-Device Enhancements for Credential Sharing ( OpenIDVP: Verifier Metadata Management)		🟠 In-progress	v0.16.0
Q1	Support for Sharing mDL/mDoc Credentials		🟠 In-progress	v0.17.0
Q1	Secure Wallet Setup with Key Binding (SIOP)		🔵 Planned	v0.17.0
Q1	Support for Advanced Cryptographic Keys (ECC K1)		🔵 Planned	v0.17.0
Q2	W3C Data Model 2.0 & SVG Render Method		🔵 Planned	v0.18.0
Q2	Credential Revocation		🔵 Planned	v0.18.0
Q2	SD JWT VC Support Selective disclosure of user information while sharing		🔵 Planned	v0.18.0
Q2	Wallet Login with Unified Key Management		🔵 Planned	v0.19.0
Q2	Secure Key Recovery with Shamir’s Secret Sharing		🔵 Planned	v0.19.0
Q2	Profile Creation using a Single Credential		🔵 Planned	v0.19.0
Q3	Same Device Flow: Multiple credential requests during the presentation (OpenIDVP)		🔵 Planned	v0.20.0
Q3	OpenID4VCI Support for credential offer endpoint and pre-authorised code flow		🔵 Planned	v0.20.0
Q3	Advanced Privacy Features with BBS+		🔵 Planned	v0.20.0
Q3	Android App Security with Play Integrity		🔵 Planned	v0.20.0
Q4	One-Time-Use Credentials for Privacy		🔵 Planned	v1.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 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 SD JWT 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		🟠 In-progress	v0.12.0
Q1	OpenIDVP: Same Device Flow (QR code based Verifiable Presentation), Multiple credential requests during the presentation		🔵 Planned	v0.12.0
Q1	Support for Country QR code - CWT Format		🟠 In-progress
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: Support multiple issuers Support common crypto algorithms Support various QR codes, VPs Data Model 1.1, 2.0 VCs Scalability Bug Fixes Performance Testing - 1 mill/day Security Testing Test Coverage>80% Sonar Coverage		🔵 Planned	v1.0
Q3	Credential Correction		🔵 Planned
Q4	Offline Verification SDK		🔵 Planned
Q4	BLE based verifiable presentation		🔵 Planned