Hyperledger Indy provides tools, libraries, and reusable components for providing digital identities rooted on blockchains or other distributed ledgers so that they are interoperable across administrative domains, applications, and any other silo. 

Indy is in active development across the following areas: 

Distributed Ledger

• indy-node

• indy-plenum

Client Tools

Note: We are in the process of moving our Client Tools work to Hyperledger Aries. We recommend engaging with both communities for the time being if you interested in building applications on top of an Indy network.

• indy-sdk

  • The Indy SDK has been deprecated in favor of the Indy and Aries shared libraries.  Please refer to the Deprecation Notice for information on the replacement libraries.

• indy-agent (superseded by project aries)

Shared Components

• indy-hipe

• ursa

Key Characteristics

• Distributed ledger purpose-built for decentralized identity

• Correlation-resistant by design

• DIDs (Decentralized Identifiers) that are globally unique and resolvable (via a ledger) without requiring any centralized resolution authority

• Pairwise Identifiers create secure, 1:1 relationships between any two entities

• Verifiable Credentials in an interoperable format for exchange of digital identity attributes and relationships, currently in the standardization pipeline at the W3C 

• Zero Knowledge Proofs which prove that some or all of the data in a set of Claims is true without revealing any additional information, including the identity of the Prover

Documentation

• An index of Indy documentation can be found here.

• The documentation of the nitty gritty of the underpinnings of the code is located in the “docs” folder of each repo.

• Note: Indy Documentation is in the process of migrating to: indy.readthedocs.io

Project Management

• Bugs, stories, and backlog for Indy Node (Ledger): https://jira.Hyperledger.org/projects/INDY

• Bugs, stories and backlog for Indy SDK: https://jira.Hyperledger.org/projects/IS

• Bugs, stories and backlog for reference Indy Agents: https://jira.Hyperledger.org/projects/IA

• A roadmap showing what the various teams are working on: Indy Roadmap

• Production deployments of Hyperledger Indy are listed: Indy Deployments

• Guidelines for reporting issues and working on issues: How to Contribute

Repositories

• https://github.com/Hyperledger/indy-node

• https://github.com/Hyperledger/indy-plenum

• https://github.com/Hyperledger/indy-sdk

• https://github.com/Hyperledger/indy-agent

Communication

Mailing List

Sign up for the  Hyperledger Indy Mailing List here

Chat (for questions and ephemeral discussions)

Questions are welcome and best asked in Hyperledger Discord.  Learn more about Hyperledger Discord here, get the invite and check out one of the many Indy project channels. 

Meetings

Identity WG Implementors Call

This is the call to discuss how to leverage Indy within your identity solution. More information is on the page Identity WG Implementors Call

Indy Contributors Call

People who want to contribute to Indy should join this call. This does not replace our asynchronous collaboration, but should help us keep everyone up-to-date and moving together.

Calls happen every other week: Europe afternoon / US morning: Monday at 8AM Los Angeles, 11AM New York, 4PM London, 18H Moscow

Location: https://zoom.us/j/244779296

Discussion items: upcoming releases, current PRs, work that will generate future PRs, architecture changes that will impact downstream teams, project standards, best practices, design, etc.

Agendas: Indy Contributors Meeting

You can work with us between calls on the #indy-contributors channel on Rocket Chat.

Calendars

• Add any recurring Indy events to your calendar by navigating to our public calendar and clicking on the specific events to add them to your own Google calendar.

• Hyperledger Calendar of Public Meetings

History

• Proposed by Steve Fulling and Phil Windley, Sovrin Foundation and Nathan George and Jason Law, Evernym - Slide Deck

• Approved by the TSC on 2017-03-30

• Proposed moving from Incubating to Active Status, Approved by the TSC on 2019-03-28

• TSC Updates: TSC Project Updates

• Historical updates: TSC Project Updates pre-2019