Framework Go v0.1.1
Objectives
Live Demo: Introduce Agents to each other and have exchange and verification of Verifiable Credentials between them
Verifiable Credentials @Dmitriy Kinoshenko
With format defined in DIF/interop, format discussion
EcdsaSecp256k1Signature2019 signature suite
Ed25519Signature2018 (already supported)
Introduce protocol (including did-exchange) @Андрій Солук
issue-credential protocol @derektrider
present-proof protocol (probably needs to be moved to next milestone) @derektrider
"Cloud" Agent via WS/REST Controller API
Bob
Dave (probably needs to be moved to next milestone)
"Edge" Agent (WebSocket did-comm transport)
Carol
Alice
Note: ideally these agents are implemented via Web Assembly (WASM) API
DIDComm "mediator"/"router" that can support edge agent demo/tests
Translate HTTP transport to WebSocket.
Web Assembly API (@Troy Ronda, Others?)
Protocol WASM "Client" API
(Browser) Local storage
(Hub storage in a future milestone)
Web socket transports
Webcrypto (future milestone)
(note: some C binding work may also be accomplished.)
Demo "GUI" for Carol
BDD driver for Aries Repo (CI)
Demo GUI page
Refactor pluggable interface categories (vdri, crypto, kms, ...) (part of #494) @Baha A Shaaban @Filip Burlacu
Update DID Exchange according to spec updates
Technical debt that must be addressed
Reuse event framework between protocols - https://github.com/hyperledger/aries-framework-go/issues/481
Logger part of context - https://github.com/hyperledger/aries-framework-go/issues/104
Error handling - https://github.com/hyperledger/aries-framework-go/issues/112
Recovery ? - https://github.com/hyperledger/aries-framework-go/issues/242
Validate DID Exchange message - https://github.com/hyperledger/aries-framework-go/issues/303
REST API
Review peer storage (how will peer doc be updated)
Review 1.1 stories for technical debt
Review TODOs in the code
Please also see the 0.1.1 GitHub milestone description.