# Roadmap 2026 & Beyond

Here we present the **Inji-Stack product roadmap for 2026** and our strategic horizon forward. This roadmap outlines the planned features, progress, and release details for **Inji Stack**.

> The **annual product cycle** for the Inji Stack begins in **January** and concludes in **December**.

For detailed module-wise roadmaps, please refer to the respective sections; Inji Wallet ([Mobile](#inji-mobile), [Web](#inji-web)), [Inji Certify](#inji-certify) and [Inji Verify](#inji-verify).

## Inji Wallet

* [Inji Mobile](#inji-mobile)
* [Inji Web](#inji-web)

### Inji Mobile

<details>

<summary>Vision</summary>

*Building a trust-first digital wallet experience simplified sharing, enhanced protection, and frictionless verification for every user, everywhere.*

Inji Mobile Wallet’s 2026 vision is to evolve into a fully interoperable, standards-aligned verifiable credential wallet that is secure, user-centric, and future-ready. The roadmap focuses on strengthening foundational capabilities—OpenID4VP & VCI final spec compliance, advanced cryptographic support (ECC R1, BBS+), unified key management, profile creation, and end-to-end revocation across all major VC formats (SD-JWT, JWT, mDoc). These upgrades ensure the wallet remains globally interoperable while meeting the needs of governments, implementers, and ecosystems adopting Inji.

We aim to deliver a highly reliable and scalable wallet that supports cross-platform verification, richer offline and BLE capabilities, multi-format rendering (SVG, PDF), and enhanced privacy models.

We will be able to introduce strategic features such as Shamir’s Secret Sharing for key recovery, BLE enhancements for iOS↔iOS, mDoc revocation, and a dedicated iOS verification library later during the year. Longer-term (2027+) innovation tracks explore multi-user credentials, one-time/bulk credential patterns, consent management, DIDComm, anonymous credentials, and multi-tech-stack portability—setting the foundation for Inji as a universal, secure, and inclusive digital credential wallet for global public infrastructure.

</details>

<table><thead><tr><th width="91.8984375">Priority 🗓️</th><th width="332.28125">Features 🛠️</th><th width="116.6015625">Details 📝</th><th width="137.13671875">Status 📊</th><th>Release 📌</th></tr></thead><tbody><tr><td>P1</td><td>Presentation During Issuance.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/inji-wallet/issues/2178">2178</a></td><td>🟢 Completed</td><td><a href="https://github.com/mosip/documentation/tree/inji/docs/inji-wallet/inji-mobile/versions/version-0.22.0">v0.22.0</a></td></tr><tr><td>P1</td><td>Claim 169 QR Code Support.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/inji-wallet/issues/2179">2179</a></td><td>🟢 Completed</td><td><a href="https://github.com/mosip/documentation/tree/inji/docs/inji-wallet/inji-mobile/versions/version-0.22.0">v0.22.0</a></td></tr><tr><td>P1</td><td>Wallet Login &#x26; Common Key Management.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/inji-wallet/issues/2119">2119</a></td><td>🟠 In-Progress</td><td></td></tr><tr><td>P1</td><td>Create Profile - Profiling with Single VC.</td><td><i class="fa-github">:github:</i> TBA</td><td>🟠 In-Progress</td><td></td></tr><tr><td>P1</td><td>Support for ECC R1.</td><td><i class="fa-github">:github:</i> TBA</td><td>🟠 In-Progress</td><td></td></tr><tr><td>P1</td><td>Credential Refresh Support.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td>DC API Support.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td>Upgrade to OpenIDVCI final version 1.0</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td>Upgrade to OpenIDVP final version 1.0</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td>W3C Data Model 2.0-based SD-JWT &#x26; JWT VC Support.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td>IETF based SD-JWT &#x26; JWT SVG Rendering.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td>Delegated Access Support from Issuer.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td>Shamir’s secret open standard Implementation.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td>Revocation of mDoc/mDL VC Format.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr></tbody></table>

### Inji Web

<details>

<summary>Vision</summary>

The vision for the Inji Web roadmap is to build a secure, interoperable, and user-friendly web wallet that fully supports the next generation of global verifiable credential standards. By introducing capabilities such as W3C Data Model 2.0, SD-JWT, mDoc/mDL, revocation, credential refresh, profile management, delegated access, and offline/USSD-based sharing, Inji Web aims to offer citizens and organizations a trusted platform to receive, manage, and present credentials across diverse digital ecosystems. With enhanced privacy features like BBS+ and seamless integration with identity providers and verifier services, Inji Web will evolve into a comprehensive, inclusive, and scalable wallet experience suitable for national-level deployments and cross-sector use cases.

</details>

<table><thead><tr><th width="87.953125">Priority 🗓️</th><th width="333.5390625">Features 🛠️</th><th width="109.44921875">Details📝</th><th width="141.58203125">Status 📊</th><th>Release 📌</th></tr></thead><tbody><tr><td>P1</td><td>W3C Data Model 2.0 &#x26; SVG Render Method.</td><td><i class="fa-github">:github:</i> TBA</td><td>🟢 Completed</td><td><a href="https://github.com/mosip/documentation/tree/inji/docs/inji-wallet/inji-web/inji-web/version-0.16.0">v0.16.0</a></td></tr><tr><td>P1</td><td>Claim 169 QR Code Support.</td><td><i class="fa-github">:github:</i> TBA</td><td>🟢 Completed</td><td><a href="https://github.com/mosip/documentation/tree/inji/docs/inji-wallet/inji-web/inji-web/version-0.16.0">v0.16.0</a></td></tr><tr><td>P1</td><td>Revocation of Data Model 2.0 VC.</td><td><i class="fa-github">:github:</i> TBA</td><td>🟠 In-Progress</td><td></td></tr><tr><td>P1</td><td>SD-JWT via OpenIDVP Flow.</td><td><i class="fa-github">:github:</i> TBA</td><td>🟠 In-Progress</td><td></td></tr><tr><td>P1</td><td>Pre-Auth Code Flow.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P2</td><td>Recovery of Web Wallet.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td><p>Create Profile - Profiling with Single VC (Profile Management </p><p>Multi-profile).</p></td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td>Presentation During Issuance.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td>mDoc/mDL VC Support.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P2</td><td>Credential refresh.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P2</td><td>Enhancement to Inji Web Login: Support other ID provider login like eSignet.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P2</td><td>Delegated Access Support from Issuer.</td><td><i class="fa-github">:github:</i> TBA</td><td></td><td></td></tr><tr><td>P2</td><td><p>USSD Support - Offline VC sharing via a feature phone</p><p>USSD Wallet.</p></td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P2</td><td><p>BBS + Support:</p><ul><li>Improve user privacy</li><li>1 secret, and a domain-specific public key</li></ul></td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P2</td><td>W3C Data Model 2.0 SD-JWT &#x26; JWT VC Support.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P3</td><td>Enhancement to Inji Web Login: Audit Mechanism with Inji web login.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr></tbody></table>

### Inji Certify

<details>

<summary>Vision</summary>

In 2026, Inji Certify will be a globally trusted, standards-aligned digital credential issuance platform enabling secure, interoperable, and scalable verifiable credentials across ecosystems. By supporting universal credential formats, OpenID4VCI v1.0, advanced cryptography, and a robust multi-issuer architecture, Certify will simplify adoption for large-scale government and enterprise deployments. Alongside delivering policy-ready issuance, revocation, and trust framework integrations, the platform will prioritize clearing technical debt and strengthening security, maintainability, and operational reliability—ensuring Certify remains a future-ready, developer-friendly backbone for privacy-preserving digital credentials worldwide.

</details>

<table><thead><tr><th width="94.57421875">Priority 🗓️</th><th width="334.1875">Feature 🛠️</th><th width="107.62890625">Details 📝</th><th>Status 📊</th><th>Release 📌</th><th data-hidden>Details - 2 📝</th></tr></thead><tbody><tr><td>P1</td><td>Presentation During Issuance with JSON LD VC Format.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/inji/inji-certify/issues/293">293</a></td><td>🟠 In Progress</td><td>0.14.0</td><td><ul><li><a href="https://mosip.atlassian.net/browse/INJICERT-990">Presentation During Issuance for Inji Certify as an Issuer</a></li><li>Mode of issuance where requesting wallet to provide another VC as proof to issue another VC</li><li>Supports only JSON-LD</li></ul></td></tr><tr><td>P1</td><td>VC Issuance with mDoc/mso VC format.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/inji/inji-certify/issues/279">279</a></td><td>🟠 In Progress</td><td>0.14.0</td><td><ul><li><a href="https://mosip.atlassian.net/browse/INJICERT-981">Inji Certify - mDoc VC Format Support</a></li><li>Support for mDoc/mso VC Issuance</li></ul></td></tr><tr><td>P1</td><td>Pre Auth Code Issuance for JSON-LD Format.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/inji/inji-certify/issues/453">453</a></td><td>🟠 In Progress</td><td>0.14.0</td><td><ul><li><a href="https://mosip.atlassian.net/browse/INJICERT-976">Implement Pre-Authorized Code Flow</a></li><li>Mode of issuance to issue VC with pre authorised code</li><li>Supports JSON-LD format</li></ul></td></tr><tr><td>P1</td><td>Embedding Multiple QR code in VC.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/inji/inji-certify/issues/491">491</a></td><td>🟠 In Progress</td><td>0.14.0</td><td><ul><li><a href="https://mosip.atlassian.net/browse/INJICERT-1223">Privacy-Preserving Verifiable Credentials with Embedded QR Code Support</a></li><li>Embedding multiple QR code in VC</li><li>Supports JSON-LD Format</li><li>Aligns with Claim 169 Specification</li></ul></td></tr><tr><td>P1</td><td>Multiple issuer.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td><td><p>Multiple data providers on one instance of Certify.</p><p>Multi Issuers support: (focusing towards one DB-postgres)</p><ul><li>multiple issuers with multiple cred</li></ul></td></tr><tr><td>P1</td><td>Adoption of OpenIDVCI v1.0.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td><td>Modifying system to follow the lates t version OpenIDVCI</td></tr><tr><td>P1</td><td>Support VC Format.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td><td><ul><li>plain JWT - W3C JSON</li><li>Support data model 2.0</li></ul></td></tr><tr><td>P1</td><td>SVG Rendering - support for multiple templates rendering.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td><td><ul><li>Allowing issuer to configure mutilple template for same VC</li></ul></td></tr><tr><td>P1</td><td>Support for adoption of external key manager system to Certify.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td><td><ul><li>Enabling certify to adopt external key manager systems</li></ul></td></tr><tr><td>P1</td><td>Multi-lingual support for credential data (Enhancement).</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td><td><ul><li>Support for other VC formats to incorporate in well-known</li><li>Support for other VC Formats with SVG Rendering</li></ul></td></tr><tr><td>P1</td><td>Credential Refreshing.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td><td><ul><li>Support to retire the old credential and issue the new credential</li><li>Support using refresh methods (credential status)</li></ul></td></tr><tr><td>P1</td><td>Support for wallet attestation client auth.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td><td></td></tr><tr><td>P1</td><td>Revocation of Credentials.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td><td><p>Support for VC Formats:</p><ul><li>SD-JWT</li><li>mDoc/mso</li></ul></td></tr><tr><td>P1</td><td>Presentation during Issuance.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td><td><p>Support for VC Formats:</p><ul><li>SD-JWT</li><li>mDoc/mso</li></ul></td></tr><tr><td>P1</td><td>Support for VC Issuance in PDF format.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td><td>Enabling certify to issue VC as PDF with signing</td></tr><tr><td>P1</td><td>Pre-Auth Code.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td><td><p>Support for VC Formats:</p><ul><li>SD-JWT</li><li>mDoc/mso</li></ul></td></tr><tr><td>P2</td><td><p>Trust registry and verifiable data registry/</p><p>Support for keri protocol.</p></td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td><td>Integrate with Gleif (keri protocol)</td></tr><tr><td>P2</td><td><p>Trust registry and verifiable data registry/</p><p>Support for dedi protocol.</p></td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td><td>Integrate with DeDi</td></tr><tr><td>P2</td><td>VC issuance with mutiple VC formats.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td><td><ul><li>SD-JWT as per W3C</li><li>Support for Data model 2.0</li></ul></td></tr><tr><td>P2</td><td>Multiple QR Codes embedded in VC.</td><td><i class="fa-github">:github:</i>  TBA</td><td>🔵 Planned</td><td></td><td><p>Support for VC Formats:</p><ul><li>SD-JWT</li><li>mDoc/mso</li></ul></td></tr><tr><td>P2</td><td>BBS Support.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td><td></td></tr><tr><td>P2</td><td>Multi-proof support for single credentials. Inji Certify all have to be enhanced with multi-proof - ED, EC &#x26; BBS+.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td><td></td></tr><tr><td>P2</td><td>VC Generation: Create Credentials from the Request Payload.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td><td><ul><li>Enable creation of credentials from request payload by internal sub-systems that are authorized to call it (using W3C VC API)</li><li>Additionally, the signing key is stored + source data can be cached (Sunbird R).</li><li>This takes data + type + format as input</li></ul></td></tr><tr><td>P3</td><td>Subject Holder relationship VC.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td><td><p>Indirectly holder holds VC not /only belongs to holder</p><p>Holder: a person who holds the VC but it either does not belong to the holder or sharing with another person (biometric owner is different)</p><p>use case :</p><ol start="1"><li>birth certificate of an infant</li><li>Share marriage certificate</li><li>Guiding elder person on usage of VC</li></ol><p>Delegated Access Support for VC Issuance</p></td></tr><tr><td>P4</td><td>VC multiple status List support.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td><td><ul><li>Support more than one status list per credentials such as support fot uspension along with revocation</li></ul></td></tr><tr><td></td><td>GA Release.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td><td>Release of Certify with Stable version</td></tr><tr><td>P4</td><td>Plug-ins for commonly used databases and data exchange.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td><td><ul><li>Reference implementation for other DB source in addition to PostgresSQL</li><li>Reference implementation to integrate with existing API</li></ul></td></tr><tr><td>P4</td><td>Allow bulk generation of onetime credentials.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td><td><ol start="1"><li>Ability to generate multiple copies of the same credentials with different credential IDs and different keys are issued.</li><li>Auto generation of credentials on a timely basis</li></ol></td></tr><tr><td>P4</td><td>Support for PDF Template and rendering (Credential Issuance).</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td><td>Enabling support for pdf-moustache for Issuer to allow VC to be issued in pdf format</td></tr><tr><td>P4</td><td>Support for WebVH (Verified History).</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td><td></td></tr></tbody></table>

## Inji Verify

<details>

<summary>Vision</summary>

By 2026, Inji Verify aims to become a universal, multilingual, and highly interoperable verification platform supporting all major credential formats including W3C JSON/JWT VCs, IETF JWT/SD-JWT, mDoc/mDL, MOSIP UIN VCs, and advanced revocation with multiple status lists backed by decentralized trust through KERI, DEDI, and global trust registries. It plans to deliver rich, branded verification outputs through SVG and PDF templatising, multi-language rendering, and support for multiple QR formats.

Verification experiences aims to be seamless across online, offline, and proximity-based scenarios with OpenID4VP and OpenIDVP same-device flows, BLE presentations, offline SDKs, and server-side ECC-R1 verification.

Inji Verify plans to expand platform reach through native Android/iOS apps and broad framework-compatible SDKs, making it a secure, accessible, future-ready, and developer-friendly global standard for credential verification.

</details>

<table><thead><tr><th width="101.4609375">Priority 🗓️</th><th width="340.55078125">Feature 🛠️</th><th width="114.34375">Details 📝</th><th width="137.12890625">Status 📊</th><th>Release 📌</th></tr></thead><tbody><tr><td>P1</td><td>Ability to verify Claim 169 QR Code.</td><td><i class="fa-github">:github:</i> <a href="https://mosip.atlassian.net/browse/INJIVER-1365">1365</a></td><td>🟠 In Progress</td><td></td></tr><tr><td>P1</td><td>OpenID4VP - Same device flows alongside Web wallets.</td><td><i class="fa-github">:github:</i> <a href="https://mosip.atlassian.net/browse/INJIVER-1437">1437</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td>Support Server Side VC Verification: ECC- R1.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/inji-verify/issues/1017">1017</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td>Ability to verify JSON (W3C) VC.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/inji-verify/issues/1018">1018</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td>Upgrade to OpenIDVP final version 1.0.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/inji-verify/issues/1019">1019</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td>W3C Data Model 2.0-based JWT VC.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/inji-verify/issues/1020">1020</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td>Multi language for SVG Template rendering.</td><td><i class="fa-github">:github:</i><a href="https://github.com/mosip/inji-verify/issues/1021">1021</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td>OpenIDVP: Same Device Flow (via DC API).</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/inji-verify/issues/1016">1016</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P2</td><td>Offline Verification SDK.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/inji-verify/issues/1022">1022</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P2</td><td>BLE based verifiable presentation.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/inji-verify/issues/1023">1023</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P2</td><td>Multi-Lingual Support.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/inji-verify/issues/1024">1024</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P2</td><td>BBS+ Support.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/inji-verify/issues/1025">1025</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P2</td><td>VC Label translation with well known.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/inji-verify/issues/1026">1026</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P3</td><td>Inji Verify SDK Support apart from React applications for Wider Framework Compatibility.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/inji-verify/issues/1027">1027</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P3</td><td>Ability to verify mDoc and mDL.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/inji-verify/issues/1028">1028</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P3</td><td>Support for philisys QR code.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/inji-verify/issues/1029">1029</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P3</td><td>Revocation for SD-JWT and JWT.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/inji-verify/issues/1030">1030</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P3</td><td><p>Trust registry and verifiable data registry/</p><p>Support for: </p><ol start="1"><li>keri protocol</li><li>dedi protocol</li></ol></td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/inji-verify/issues/1031">1031</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P4</td><td>IETF JWT VC Support.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/inji-verify/issues/1032">1032</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P4</td><td>Native App for Inji Verify - Android device.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/inji-verify/issues/1033">1033</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P4</td><td>Native App for Inji Verify - iOS device</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/inji-verify/issues/1034">1034</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P4</td><td>Revocation for mDoc/ mDL.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/inji-verify/issues/1035">1035</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P4</td><td>Multiple QR Codes embedded in VC in a single PDF.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/inji-verify/issues/1036">1036</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P4</td><td>SVG Rendering for IETF based SD-JWT &#x26; JWT.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/inji-verify/issues/1037">1037</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P4</td><td>PDF Template Support.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/inji-verify/issues/1038">1038</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P4</td><td>VC multiple status List support.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/inji-verify/issues/1039">1039</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P4</td><td>Support for WebVH (Verified History).</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/inji-verify/issues/1040">1040</a></td><td>🔵 Planned</td><td></td></tr></tbody></table>

***

**Acronyms and Legends**:

<i class="fa-github">:github:</i> **TBA**: 'Github Issues Link - To Be Added'