User Tools

Site Tools


Running Roadmap for Hyperledger Indy


This roadmap is to coordinate the various teams contributing to the Hyperledger Indy project. Please read this explanation, and then add your own priorities to this list.

The contributor community for HyperLedger Indy is a diverse group. Each group has their own priorities. By sharing those priorities, we hope to identify areas of shared interest, foster collaboration, and increase the usefulness of delivered items. If something is high on your list, but low on another team’s list, you should seek to have a conversation as you plan your work. Each team roadmap includes a method of contacting a key stakeholder for a discussion.

This roadmap represents each team's high level development priorities, which they will break into Epics and Stories in the referenced issue tracker. Most contributions to Hyperleger Indy will eventually result in an issue being created in the appropriate project of the JIRA instance used by Hyperledger.

Standard Disclaimers

The information in this roadmap is shared in good faith, but is exclusively for informational purposes. Nothing on this roadmap shall be considered a commitment by any party to any other party. Priorities, resources, and timeframes will frequently change. Projects may be deferred or cancelled at any stage of development. Delivery of anything on this roadmap remains at the sole discretion of the people doing the work.

Hyperledger Indy is not obligated to accept any contribution, even if it appears on this roadmap. The incorporation of a contribution into the project depends on that contribution meeting established standards and aligning with the development roadmap of the core maintainers.

Current Release Plan

Indy Node

  • 1.5 (July): Plenum Plugin support, reduced logging in production, stability fixes.
  • 1.6 (August): Connection management and stability fixes.

Indy SDK

  • Indy SDK 1.6 (July): Wallet search for anoncreds, cluster shared wallet, standardize wallet export format.
  • Indy SDK 1.7 (August): Use Hyperledger CI / CD and get CII badge.

Collective Shared Objectives

Roadmap contact: Nathan George, reachable by sending an email to the Indy mailing list.
Issue Tracker:

Roadmap Updated: October 2018

In Progress

  1. Graduation from Hyperledger Incubation
    1. Security audit (underway)
  2. Community build pipelines fully hosted in the open (at the Linux Foundation and Sovrin Foundation)
  3. Payment for transactions and agent interactions (permission-less access)
  4. Default Wallet implementation
  5. Default Agents implementation
  6. Standardized message formats
  7. Schemas and data modeling
    • Improved schema format
    • On-ledger proof requests
    • Schema overlays
  8. Reducing the on-ramp for new developers
    • “off-the-shelf” demo of multi-sourced identity
    • Examples
    • Documentation
  9. Shared Crypto Library
  10. Standard for DID / DID Document
  11. W3C standards for verifiable credentials
  12. Distributed Key Management (DKMS)


Sovrin Foundation Development Team

Roadmap contact: Nathan George
Issue Tracker: See Hyperledger JIRA links above
Roadmap Updated: January 2019

In Progress

  1. Graduate from Hyperledger incubation
  2. Community build pipelines
  3. Reference Agent implementation
  4. Standardized message formats
  5. Developer documentation improvements
  6. Shared Crypto Library
  7. New schema format

Sovrin Trust Framework Working Group

Roadmap contact: Nathan George
Issue Tracker: TBD
Roadmap Updated: October 2018

In Progress

  1. Defining performance requirements for Stewards in the Trust Framework
  2. Reqs for being able to use the Sovrin trademarks in context of SSI
  3. Automate Trust Framework onboarding
  4. Trust Anchor onboarding
  5. Identity onboarding requirements TA’s must meet

Evernym Indy-Node Team

Roadmap contact: Richard Esplin
Issue Tracker:
Roadmap Updated: 2018-06-27

Recently Completed

  • Versioned ledger transaction format

In Progress

  1. Stability and availability of the Sovrin network
  2. Network monitoring
  3. Manage open connections
  4. Plugins to Plenum
  5. Performance benchmarking
  6. Technical Debt and refactorings


  1. View Change refactoring: (2018H2)
    1. Adopt View Change to be as in PBFT
    2. Adopt a state machine
  2. Changing transport between client and node to improve scalability (2018H2)
    1. replace ZMQ transport with agent-to-agent communication
      1. improved capability of controlling load
  3. DID / DID Doc standards compliance (2018H2)
  4. Ubuntu 18.04 support (2018H2)
  5. Credentials standards compliance (2018H2)
  6. Observer node support (2018H2)
    • periodic updates to multi-signature without load on the pool
    • BLS multi-signature for the pool ledger
    • Possibility to catch-up from one node only
  7. 3PC State Machine
  8. State Machine for requests
  9. Request format refactoring
  10. Improvements to RBFT protocol
    1. Improve the performance and accuracy of RBFT instances
  11. Schema Enhancement
    • Enforcement of data types and units of measurement
    • Inherit schemas
    • Embed schemas
  12. Node Reputation
  13. Upgrade Mechanism with voting
  14. Public facing dashboard
  15. Ledger explorer
    • View of only schemas
  16. Win64 support
  17. Mac support
  18. Sharding
  19. Ledgerless DIDs
  20. Documentation (Phase II)


  • Ed25519 Open source tool key compatibility (Public key generation tool)
  • Support for IPv6
  • Flex TLS / DID TLS
  • Anchoring as a transaction type
  • CII Badging

Evernym Indy-SDK Team

Roadmap contact: Richard Esplin
Issue Tracker:
Roadmap Updated: 2018-06-27

Recently Completed

  • Plugable wallet storage
  • Non-secrets API for application data in wallet
  • Plugable payments API and nullpayment plugin
  • Manage API versions between releases

In Progress

  1. Sharing a wallet between Akka nodes
  2. Wallet import / export
  3. Incorporate feedback on the Payments API
  4. Search and filtering in Wallet
  5. CI / CD Improvements, including a public Jenkins pipeline
  6. Credential exchange API (merging in Evernym/sdk libVCX)
  7. Contribute a reference Cloud Agent to indy-agent


  1. Contribute indy-crypto to hyperledger-crypto as a shared crypto library (2018H2)
  2. Scalability of LibIndy: multiple connections (2018H2)
  3. Updating Howtos
  4. Agent messaging standardization
  5. DID / DID Doc and Credentials standards compliance
  6. Android
  7. Schema Enhancement
  8. Photos/Attachments in Claims
  9. Agent Discovery Protocol
  10. Pre-allocation DIDs
  11. Proof requests
  12. Additional predicates

Evernym Debug Tools Mission

Roadmap contact: Richard Esplin
Issue Tracker: Internal Evernym. Will create public issues for pull requests.
Roadmap Updated: 2018-06-27

Recently Completed

  1. Capture and replay interactions on a node: INDY-1283

In Progress

  1. Snapshot recordings
  2. Chaos toolkit for automating integration and system tests

VON (Verifiable Organizations Network)

Community Project: Province of British Columbia, Gov of Canada (Pubic Services and Procurement Canada), Province of Ontario

Roadmap contact: John Jordan and Stephen Curran
Community Page: Verifiable Organizations Network
Issue tracker: Using ZenHub against GitHub repository

Roadmap Updated: 2018-10-15

Achieved: TheOrgBook - BC Instance - Live: October 2018

Pending: TheOrgBook - Ontario Instance - Beta Live end of October 2018 (dependent on SLN update)

Completed Contributions

  1. VON Image - Python base container image for VON and any indy-node, indy-sdk deployments
  2. VON_Anchor continues to track to latest indy-sdk - github repo
  3. VON-X - uses VON_Anchor to implement Verifiable Credential Roles - Issuer, Holder, Verifier in any combination - github repo
  4. TheOrgBook github repo
    1. Credential Processor (Credential Parser for Search Data)
    2. Web-based UI - Search and view Organizations History
    3. API for accessing/verifying the verifiable credential open data held by TheOrgBook
    4. Scaling to Loading ~7.5M Credentials - current speed - 2600 cred/min issued and stored
    5. Enterprise Wallet capable of holding ~7.5M Credentials - Postgres
    6. Enterprise hardening - deployment, backup/restore, monitoring
  5. Government Service - Verifiable Credential Issuer/Verifier
    1. Service Event Processor (Credential Issuer) - BC Registries github repo and Onbis (Ontario) implementations


  1. Additional features in TheOrgBook
    1. UI enhancements
    2. Credential Change Notifications (pub/sub and webhooks)
  2. Adding Issuer/Verifier Services to existing VON instances
    1. Tools for understanding the (simple) onboarding process
    2. Upgrade of the Permitify Demo to the latest code
  3. Adding VON Participants - more instances of TheOrgBook
    1. Hyperledger Indy Catalyst (working title) project
    2. Tools for understanding the deployment process - technical and business
  4. Verified Relationships - Organizations and Owners have their own Wallet
    1. Agent-to-Agent messaging protocol using Reference Agent
    2. Extending the Permitify Demo to include Organizations with their own Agents
    3. Client Agent Reference implementation and Test Suite
    4. Collaboration with other Agent Builders
    5. Possible: Web Assembly

BYU Office of Information Technology (OIT)

Roadmap contact: Matthew Hailstone
Issue tracker: Private GitHub
Roadmap Updated: 2018-10-15


In Progress

  1. Agency services for students and university (issuer, holder, and verifier)

Wipro Team

Roadmap contact: Vinod Panicker
Issue Tracker: Public Github ,
Roadmap Updated: 2018-05-03

In Progress

  1. PHP Wrapper for Indy
  2. Drupal Blockchain Modules for Indy


  1. Drupal Distribution for Indy


Roadmap contact: Troy Ronda
Roadmap Updated: 2018-05-10

Next (TBD)

  1. Go Wrapper for Indy
  2. Interop related topics such as resolvers, verifiable credentials, agents, and fabric integration

What follows is a template you can copy and paste to add your team.

Your Team Name

Roadmap contact: Some way to contact you
Issue Tracker: Where people can details about the items
Roadmap Updated: Today's date

Recently Completed

  • Claim credit for things you recently contributed

In Progress

  1. Most important item your team is working on now
  2. Next most important item


  1. Your next priority
  2. And the one after
  3. And the one after


  • Something you would like to see done, but aren't prioritizing now.
  • It could be blocked on something that is currently on the backlog.
  • Or it could be something you are hoping someone else will do.

projects/indy/roadmap.txt · Last modified: 2019/01/04 17:16 by michael boyd