Discussing the Future of Aries, Indy, and Ursa

The Future of Indy, Aries & Ursa

Session: 9G

Convener: Richard Esplin

Notes-taker(s): Keng Suzuki

Tags for the session - technology discussed/ideas considered:

Discussion notes, key understandings, outstanding questions, observations, and, if appropriate to this discussion: action items, next steps:

Discussion topics:

• Background on the projects
• Current work items
• Open questions about the future

purpose: for new contributors

http://github.com/hyperledger

ursa related repo: ursa-rfcs, ursa-docs, ursa-python

indy related repo: indy-hipe(like rpc), indy-node(identity role on top of plenum), indy-lenum(consensus alg), indy-sdk(library makes easier to talk ledgers)

aries related repo: aries-rfc, aries-framework-[go|dotnet|, aries-acapy-plugin-toolbox, aries-protocol-test-suite

bestway to track status:

http://wiki.hyperledger.org/display/indy/Indy+Contributors+Meeting

http://wiki.hyperledger.org/display/IWG/Identity+WG+Implementers+Call

current work stream in here [1]

indy-vdr

indy-credx: key storage

use more github issues

cicd (from jenkins to github actions)

rich schema (about verifiable credential)

privacy preserving revocation

Communication place

chat: http://chat.hyperledger.org/home

create LFID: http://wiki.hyperledger.org/display/CA/setting+up+an+LFID

indy networks

sovrin: public ledger

bedrock: steward model

consensus

- there is an independent Aries implementation, ACA-Pico, being written by students in Pico Labs as an open source project at https://github.com/Picolab/aries-cloudagent-pico