Experiment

Experiment

Experiment

Roadmap 2025

Inji Wallet

Inji Mobile

Q1: Jan25 - Mar25

Q2: Apr25 - Jun25

Q3: Jul25 - Sep25

Q4: Oct25 - Dec25

Quarter
Feature
Status
Feature Details
Release Details

Q1

Cross Device OpenIDVP Enhancements - Verifier Metadata Management

In Progress

v0.16.0

Q1

Sharing of mDoc/mDL VC Support through OpenIDVP

In Progress

v0.17.0

Q1

Implement SIOP (Key binding as part of the download)

To be planned

v0.17.0

Q1

Support for ECC K1

To be planned

v0.17.0

Q2

W3C Data Model 2.0 & SVG Render Method

To be planned

v0.18.0

Q2

Revocation of VC

To be planned

v0.18.0

Q2

  1. SD JWT VC Support

  2. Selective disclosure of user information while sharing.

To be planned

v0.18.0

Q2

Wallet Login & Common Key Management

To be planned

v0.19.0

Q2

Shamir’s secret open standard Implementation

To be planned

v0.19.0

Q2

Create Profile - Profiling with Single VC

To be planned

v0.19.0

Q3

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

  1. Request for multiple credentials.

  2. Support multiple credential submissions.

  3. Single VP request with multiple credentials for single wallet

To be planned

v0.20.0

Q3

OpenID4VCI enhancements:

  1. credential_offer endpoint

  2. pre-authorised code flow

To be planned

v0.20.0

Q3

BBS+ support

To be planned

v0.20.0

Q3

Play integrity of the app- Android

To be planned

v0.20.0

Q4

Inji Wallet(Mobile) - One-time credentials.

  1. Request for bulk credentials. So multiple copies of the same credentials with different credential IDs and different keys are issued.

  2. Then, the wallet would present every credential once. This helps in privacy, as every credential is unique, breaking the 360-degree profiling.

  3. The wallet should abstract all these credentials and show it as only one card on the UI.

To be planned

v1.0

Q4

Multi-user Credentials -

(Eg: Revocation to be done from both the wallet )

  1. Credentials that are used for the family. combining multiple subjects.

  2. Each subject might need to download this credential.

  3. Each one can use it for their own needs.

  4. eg: ration card, property sale deed(property title)

To be planned

v1.0

Q4

JWT VC Support

To be planned

v1.0

Q4

Support for ECC R1

To be planned

v1.0

Inji Web

Q1: Jan25 - Mar25

Q2: Apr25 - Jun25

Q3: Jul25 - Sep25

Q4: Oct25 - Dec25

Quarter
Feature
Status
Feature Details
Release Details

Q1

User login, VC management, profile management (profile menu)

PLANNING IN PROGRESS

v0.12.0

Q1

Key management for download (common for both web & mobile)

To be planned

v0.12.0

Q1

W3C Data Model 2.0 & SVG Render Method

To be planned

v0.13.0

Q2

Shamir’s secret open standard Implementation

To be planned

v0.13.0

Q2

Key Support for download and Verification : ED25519 Signature 2018 & 2020

To be planned

v0.13.0

Q2

Key Support for download and Verification : ECC K1

To be planned

v0.14.0

Q2

mDoc/mDL VC Support

To be planned

v0.14.0

Q2

CBOR VC Support

To be planned

v0.14.0

Q3

SD JWT-based Support

To be planned

v0.14.0

Q3

OpenIDVP: Same-Device Flow

To be planned

v0.15.0

Q3

OpenID4VCI enhancements:

  1. credential_offer endpoint

  2. pre-authorised code flow

To be planned

v0.15.0

Q3

Revocation VC

To be planned

v0.15.0

Q4

BBS+ Support

  • Improve user privacy

  • 1 Secret, and a domain-specific public key.

To be planned

v0.16.0

Q4

Inji Wallet (Web) - One-time credentials.

  1. Request for bulk credentials. So multiple copies of the same credentials with different credential IDs and different keys are issued.

  2. Then, the wallet would present every credential once. This helps in privacy, as every credential is unique, breaking the 360-degree profiling.

  3. The wallet should abstract all these credentials and show it as only one card on the UI.

To be planned

v0.16.0

Q4

Multi-user Credentials -

(Eg: Revocation to be done from both the wallet )

  1. Credentials that are used for the family. combining multiple subjects.

  2. Each subject might need to download this credential.

  3. Each one can use it for their own needs.

  4. eg: ration card, property sale deed (property title)

To be planned

v1.0

Q4

Key Support for download and Verification: ECC R1

To be planned

v1.0

Q4

Implement SIOP (Key binding as part of the download)

To be planned

v1.0

Inji Verify

Q1: Jan 25 - Mar 25

Q2: Apr 25 - Jun 25

Q3: Jul 25 - Sep 25

Q4: Oct 25 - Dec 25

Quarter
Feature
Status
Feature Details
Release Details

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.

Wishlist

v0.12.0

Q1

Support for Country QR code - CWT Format

In-Progress

Q1

Verify mDoc and mDL

Wishlist

Q1

Revoked Credentials

Wishlist

Q2

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

Wishlist

Q2

Support Server Side VC Verification: ECC- K1 and R1

Wishlist

Q2

Verify: W3C VC, SD JWT

Wishlist

Q2

Verify document(pdf) with multiple QR Codes

Wishlist

Q3

Support for multi proof: Single credential should support multiple proofs

(both embedded and linked)

Wishlist

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

Wishlist

v1.0

Q3

Credential Correction

Wishlist

Q4

Offline Verification SDK

Wishlist

Q4

BLE based verifiable presentation

Wishlist

Last updated

Copyright © 2021 MOSIP. This work is licensed under a Creative Commons Attribution (CC-BY-4.0) International License unless otherwise noted.