Versions Compared

Old Version 7

changes.mady.by.user Troy Ronda

Saved on

compared with

New Version Current

changes.mady.by.user Firas Qutishat

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Objectives

  •  Creation and validation of Peer DIDs (genesis version only)

...

...

...

Please also see the 0.1.0 GitHub milestone description.

Design considerations

aries-framework-go is a highly customizable framework that provides sensible defaults.

...

Only the genesis version of Peer DIDs is required for this milestone.Note: we will implement the cryptographic envelope with the updates currently discussed in hyperledger/aries-rfcs#133

Cryptographic Envelopes

Full support for cryptographic envelopes with ECDSA keys.

Support for Ed25519VerificationKey2018

Implement the Ed25519 Signature 2018 signature suite for creating DID documents and proving ownership.

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.

...

We will demonstrate usage of a Fabric enabled with the Sidetree protocol (exposing the HTTPS binding for DID resolution).

Live Demo 1: simple DID exchange

The goal is to showcase the following with two non-mobile Agents exchanging peer DIDs with both running on the same laptop.:

  • Creation and validation of Peer DIDs (genesis version only)
  • did-exchange protocol with cryptographic envelopes and using HTTPS as transport
  • Local storage of peer DIDs

The presenter should be able to run the steps one by one as they showcase the demo to others.

A controller API is needed on each Agent in order to drive the demo's steps. The controller API in this framework will be closely aligned with the one in aries-cloudagent-python with the goal of demonstrating interoperability.

Outline:


Live Demo 2:

...

ledger-backed DID resolution using Hyperledger Fabric and Sidetree

The goal is to showcase usage of ledger-backed DIDs during DID exchange and also demonstrate usage of another Hyperledger DLT (Fabric). This is a variation of Live Demo.

As with Live Demo, we should be able to run step by step. In this case, we additionally want to highlight:

  • 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.