...
(Introduced to some as a “Hyperledger shared wallet project,” but that moniker is an incomplete description, read on to find out more.)
Accepted and now tracking setup at Aries New Project Checklist
Sponsor(s)
Nathan George, Sovrin Foundation, nathan@sovrin.org
...
John Jordan, Province of BC, john.jordan@gov.bc.ca
Tobias Looker, Spark NZMattr, tobias.looker@spark.co.nzlooker@mattr.global
Robert Mitwicki, Lab10 Collective, robert.mitwicki@lab10.coop
...
Troy Ronda, SecureKey Technologies, troy.ronda@securekey.com<This could be a malicious sponsor! Document permissions are not set appropriately.>
Markus Sabadello, Danube Tech, markus@danubetech.com
<Please contact @nage on https://chat.hyperledger.org to be added as a sponsor>
...
Context
Hyperledger Aries is a client tool suite and framework code for trusted peer interactions and information exchange, as such it is an excellent toolkit for secrets management and can serve as a blockchain client for many systems. It is related to Hyperledger Indy, which provides a resolver implementation, and Hyperledger Ursa, which it uses for cryptographic functionality.
...
We also intend for project Aries to support multiple DID methods through a generic resolver interface. This generic interface will initially support the Hyperledger Indy resolver but will be extensible so that if someone wanted to build a pluggable Hyperledger Fabric DID method resolver, Ethereum DID method resolver, or another DID method resolver in they could. These resolvers would support the resolving retrieval of transactions and other immutable data that has a shared state on a ledger. One of the other pieces that will come built into this project will be support for a peer DID method resolver which will rely upon the wallet and p2p messaging protocol to maintain the state of a peer-to-peer relationship. Another interaction that the resolver interface will support is the ability to resolve read data that exists in a verifiable data registry. An example of a VDR is the Indy Catalyst project.
...
- https://github.com/hyperledger/aries (migrate some, but not all code from indy-SDK, remaining indy-SDK would become the indy-resolver loaded by an Aries agent)
- https://github.com/hyperledger/aries-rfcs (migrate related indy-hipe docs).
- https://github.com/hyperledger/aries-agent (migrate from indy-agent)
...
The project success can be measured by ability to use the agent protocol to communicate with code bases. If support of verifiable credentials, DIDs, or other peer to peer communications provided by this code base doesn't materialize outside of Indy it may be appropriate to fold this project back into Hyperledger Indy.
Reviewed By
- Arnaud Le Hors
- Baohua Yang
- Binh Nguyen
- Christopher Ferris
- Dan Middleton
- Hart Montgomery
- Kelly Olson
- Mark Wagner
- Mic Bowman
- Nathan George
- Silas Davis