As of August 2019, several Aries code repositories have been created from scratch, and others are rapidly populating from various other locations, including Hyperledger Indy repositories where the Aries work was incubated. Some of the code requires refactoring work to split it from unrelated assets prior to migration.
The status of these code migrations is under regular discussion on the #aries and #indy-agent channels on chat.hyperledger.org and in the Aries Working Group weekly call. Please join us there to understand migration status and help identify places where help is needed.
When the appropriate code is migrated to this repoisitory, this README file will be updated.
Hyperledger Aries is a blockchain-agnostic, reference implementation of the agent, DID communications, wallet, protocols and key management technologies that underpin decentralized identity.
Aries work is spread across many repos. Most developers who want to solve business problems with decentralized identity should start with an agent framework such as:
- aries-cloudagent-python (this repo is likely to be renamed, since it supports agents in non-cloud deployments just as well)
- aries-framework-go
- aries-framework-dotnet
- aries-staticagent-python
[TODO: THESE LINKS ARE NOT YET ACTIVE]
If you want to understand the theory and the open standards that these frameworks implement, then you should visit:
If you want to work on the low-level features that underpin all the agent frameworks, then the repos you want are:
Hyperledger Indy is all about decentralized identity, like Aries. However, Indy is focused on a specific blockchain purpose-built for identity, whereas Aries is blockchain-agnostic. In the long run, we expect most community members to build directly on Aries; Aries will incorporate Indy support along with support for other ecosystems as it matures.
Much of the work done in Indy SDK between 2017 and 2019 was actually blockchain-agnostic, and the developers in that community began formalizing many concepts related to agents and DIDComm. Now that Aries exists, Indy artifacts will be partitioned. Functionality related to Indy's blockchain will remain in Indy, whereas general functionality will be moved over to Aries repos through a PR process for broader community ratification.
If you are using Indy SDK today to build a decentralized identity solution, keep doing so for the time being. Aries is not yet mature enough to build upon, but when it gets there, a reasonable transition process will be provided, and announcements will be made in community channels.