Objectives
- Creation and validation of Peer DIDs (genesis version only) -
...
- contained in [#35]
did-exchangeprotocol
...
- - contained in [#42]
- Cryptographic envelopes with the updates discussed in hyperledger/aries-rfcs#133 -
...
- contained in [#36]
- Support for Ed25519VerificationKey2018 - contained in [#96]
- Local storage of peer DIDs -
...
- contained in [#35]
- Resolution of DIDs
...
- - contained in [#86]
- Live Demo 1: simple DID exchange -
...
- contained in [#67] [#68] [#74] [#44]
- Live Demo 2: ledger-backed DID resolution using Hyperledger Fabric and Sidetree via HTTPS binding - contained in [#124]
Please also see the 0.1.0 GitHub milestone description.
Design considerations
aries-framework-go is a highly customizable framework that provides sensible defaults.
...
Full support for cryptographic envelopes with ECDSA keys.
Linked Data Cryptographic Suite
Support for Ed25519VerificationKey2018
Implement the Ed25519 Signature 2018 signature suite for creating DID documents and proving ownership.TODO: Support for at least one of these is required such that DIDs can be created and verified. Initial thought is to support the one most commonly used among the registered DID methods (Secp256k1?)
did-exchange protocol using HTTPS as transport
...
No specific implementation targeted for this milestone. (note: it is assumed we will continue with the goleveldb approach for this iteration.)
Define generic storage interface that allows the Agent to protect its secrets from the storage provider.
...
- Creation of the DID in fabric-sidetree.
- Demonstrate that the fabric ledger contains the DID (showing the JSON document, batch file, and block containing the hash).
- The HTTPS request & response that shows we made an external call to the DID resolution endpoint of fabric-sidetree (and that it follows the HTTPS binding).
- Exchange and resolution of the Sidetree DIDs between agents.
The Fabric with Sidetree project should be pulled from dockerhub and used with a docker-compose environment for easy demo setup.
This demonstration makes progress towards one of the goals of the Hyperledger Aries project: "Cross-platform integration" (see Aries Proposal FAQ), and also helps demonstrates the possibility of a cross-Hyperledger scenario.