...
- Aries Agent Test Harness (https://aries-interop.info)
- Aries Askar secure storage - https://github.com/bcgov/aries-askar
- Frameworks:
- Aries-CloudAgent-Python (https://github.com/hyperledger/aries-cloudagent-python, Meetings: ACA-Pug Meetings)
- Encryption envelope (Askar impl) not fully-developed yet. We could use different libraries (SICPA Rust). SICPA DIDComm impl is what will be used... resolves did peers natively. The keys will have to be transported out of Askar, but that is acceptable for now. SICPA is the most widely used.
- SICPA for DIDComm and did:peer https://github.com/sicpa-dlab/didcomm-python
- No near-term Askar support for the DIDComm v2 encryption envelope and core protocols.
- Protocols related to credential exchange and connection establishment. Distinguish between DIDComm v1 and v2. DID Exchange will be adapted. The main focus is on Out-of-Band protocol.
- Very important to extend the AATH.
- Encryption envelope (Askar impl) not fully-developed yet. We could use different libraries (SICPA Rust). SICPA DIDComm impl is what will be used... resolves did peers natively. The keys will have to be transported out of Askar, but that is acceptable for now. SICPA is the most widely used.
- Aries-Framework-JavaScript (https://github.com/hyperledger/aries-framework-javascript, Meetings: Framework JS Meetings)
- https://github.com/hyperledger/aries-framework-javascript/pull/1096#issuecomment-1343833016
- https://github.com/hyperledger/aries-framework-javascript/pull/1211
- Issue related to multi-base from SICPA for DID peer
- Picos as Aries agents (DIDComm v1: https://github.com/Picolab/aries-cloudagent-pico ; DIDComm v2 work in progress)
- students have returned and they are using SICPA for envelope encryption, pack/unpack and hopeful sending messages
- DIF Picos working group, useful for IoT devices.
- Rich API and Internet connected to be a capable L2 agent.
- Using Trinsic as VC as a service.
- Swift Framework
- Veramo Framework
- WACI support https://github.com/uport-project/veramo/issues/1106
- DID Peer support https://github.com/uport-project/veramo/issues/1105
- Using Brian's (AviaryTech) DID Peer impl, adapting it as a plugin
- Merged Mediation, agent can mediate. A Veramo mediator will be published soon.
- Aries-CloudAgent-Python (https://github.com/hyperledger/aries-cloudagent-python, Meetings: ACA-Pug Meetings)
- Mobile:
- Aries Mobile Agent React Native, aka Aries Bifold (https://github.com/hyperledger/aries-mobile-agent-react-native, Meetings: Aries Bifold User Group Meetings)
- aries-mediator-service – a DIDComm Mediator in a Box
- working on Pickup support
- DIDComm v2 support would probably originate from this meeting/community
- AviaryTech DIDComm TS impl
- https://github.com/aviarytech/didcomm
- https://github.com/aviarytech/did-peer
- Focused on OIDC lately
- KERI Working Group
- Alternative to peer DID. More refinements to the proposal. Then present it to the Aries groups. Similar to Algo2 of the peer DID.
- KERI parameter on the DID in order to get the document. Public encryption key and serviceEndpoint.
- Query param w/ base 64 path that you can decode
- encryption keys, service endpoint, etc.
- Compared to did:peer, the keri long form is longer
- inception event only
- But follow-on messages only need to use the short-form of KERI DID
- So, this is not a Persistent did
- Rodolfo Miranda Will add a README and sample output.
- Alternative to peer DID. More refinements to the proposal. Then present it to the Aries groups. Similar to Algo2 of the peer DID.
- ToIP Trust Spanning Protocol
- Good back and forth between Sam, Daniel, and others https://github.com/trustoverip/trust-spanning-protocol/discussions/17
- Daniel present his proposal this week, at the Wednesday TSPTF
- Sam joins the task force and has a video of Sam's that diagrams his TSP vision https://zoom.us/rec/play/1EcHtXeGPPynwwBvU3X4uAAw0xhFPC3CwwAIXwQ-P_E6tPlzvBskHuzTYftS1ZrmjPw5EiBZWYwiTgdI.tx021j9JATi2l5Xq?continueMode=true&_x_zm_rtaid=noVlj_2fRpuccKG26Jmytw.1675686252575.5cf45b925f44c52d0118a3fdef8541ea&_x_zm_rhtaid=714
Discussion Topics
Camel DIDComm impl by Thomas Diesler - Nessus DIDComm 0.23.2 First Release
- Wallet abstraction for AcaPy + Nessus native
- Camel Http Endpoint for Nessus agent
- Support for RFC0434 Out-of-Band Invitation V1 & V2
- Support for RFC0023 Did Exchange V1
- Support for RFC0048 Trust Ping V1 & V2
- Support for RFC0095 Basic Message V1 & V2
- CLI to work with supported protocols and model
DWN & KERI & DIDComm comparison
...