2024-03-20 Aries Working Group Call
Summary:
- PR Review
- DIDComm v2 Credential protocol updates
- Basis for common identifiers
Zoom: https://zoom.us/j/93803916577?pwd=UWdLSTJ2b0kvZTRyc1hZTUdQQ3ZFZz09
Recording:
Date
(7AM Los Angeles, 10AM New York, 3PM London, 4PM CET, 18H Moscow)
Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct. |
---|
Attendees
- Sam Curren (Indicio) <sam@indicio.tech>
- Ariel Gentile (2060.io) <a@2060.io>
Welcome / Introductions
Announcements
- IIW - April 16-18
- Lots of BC Ledgers, all but BSovrinTest. Genesis now all points to the same ledger.
Release Status and Work Updates
- Aries Agent Test Harness -- https://aries-interop.info
- Aries Shared Components - Indy SDK replacements
- Indy Verifiable Date Registry - Ledger Interface https://github.com/hyperledger/indy-vdr
- PR merged for caching in Indy VDR of Pool Transactions - Aries Frameworks should be adding that to
- Release 0.4.0
- Release 0.5.0 will have breaking changes, including did:indy branch merged into main.
- Aries Askar secure storage - https://github.com/bcgov/aries-askar
- Release 0.2.9
- AnonCreds Rust - https://github.com/hyperledger/anoncreds-rs
- Release 0.1.0
- Shared Rust Library/CredX (AnonCreds) https://github.com/hyperledger/indy-shared-rs - being replaced by AnonCreds Rust
- Release 0.3.3 Bugfix (bug was in the python wrapper)
- Release 1.0.0 Embeds new AnonCreds CL Signatures library with fixes, performance improvements
- Release 0.3.3 Bugfix (bug was in the python wrapper)
- Indy Verifiable Date Registry - Ledger Interface https://github.com/hyperledger/indy-vdr
- Frameworks:
- Aries-CloudAgent-Python https://github.com/hyperledger/aries-cloudagent-python, Meetings: ACA-Pug Meetings, Documentation: https://aca-py.org
- 0.12.0rc0 – Peer DID support, many enhancement/fixes, nothing breaking yet but at least one will be made before finalized.
- Release 1.0.0 Checklist has been created and is being worked on.
- Traction Sandbox now available - https://traction-sandbox-tenant-ui.apps.silver.devops.gov.bc.ca
- Credo (Agent-Framework-JavaScript) https://github.com/openwallet-foundation/credo-ts, Meetings: Credo Meetings
- 0.5 shipped!
- Dropping IndySDK
- AnonCreds Revocation
- Dropping Node 16 support (EOL)
- W3C issuance and verification of AnonCreds credentials
- did:peer:2 and did:peer:4 support and did rotate protocol
- Continuing working on SD-JWT and OpenID4VC support
- 0.5 shipped!
- Aries VCX (https://github.com/hyperledger/aries-vcx, Meetings: Aries-VCX Meetings
- aries-vcx as repository now contains 2 project families:
- aries
- didcore
- aries-vcx as repository now contains 2 project families:
- Picos as of pico-engine version 1.3.0 natively use DIDComm v2 (https://github.com/Picolab/pico-engine/blob/master/packages/pico-engine/README.md)
- replacing ACA-Pico agents (https://github.com/Picolab/aries-cloudagent-pico) which are now deprecated
- protocols implemented so far: oob invitation, trust-ping, basicmessage (more to be added https://github.com/Picolab/DIDComm-V2)
- based on the SICPA didcomm NodeJS module
- Aries-Framework-Go (Troy) #aries-go (https://github.com/hyperledger/aries-framework-go, Meetings: aries-framework-go)
- Aries-CloudAgent-Python https://github.com/hyperledger/aries-cloudagent-python, Meetings: ACA-Pug Meetings, Documentation: https://aca-py.org
- Mobile:
- Aries Mobile Agent React Native, aka Aries Bifold https://github.com/hyperledger/aries-mobile-agent-react-native, Meetings: Aries Bifold User Group Meetings
- 0.4.0 in Bifold – including the shared components
- Aries-MobileAgent-Xamarin aka Aries MAX (https://github.com/hyperledger/aries-mobileagent-xamarin)
- 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
- Update to use SocketDock?
- aries-endorser-service – an Indy Endorser in a Box (in development)
- Aries Akrida - Load Testing DIDComm based protocols
- Added module support for different Issuer and Verifiers
Discussion Topics
- OpenID DIDComm work by IDUnion
- https://github.com/IDUnion/OpenIDIDComm
- Docs and cleanup still in process
- Ecosystem Diagram / Document
- PR Review
- 821 - Update DID Exchange Examples
- 820 - Update AIP 2 to latest clarification commits, remove static peer dids
- 819 - Update Index and remove github action
- 818 - removes references to please ack from other protocols
- 812 - OOB compression
- will this eliminate the need for http redirects?
- qr code size
- bandwidth reduction
- connectionless - messages can be large.
- Interest? Strong Maybe.
- will this eliminate the need for http redirects?
- DIDComm v2 conversion
- (Notes from previous weeks)
- Smaller changes may mean faster adoption
- negotiation pulled out into a sibling protocol - (nobody using negotation? Subhasis referenced use.)
- propose message moves to different family.
- Document the short-circuted use of the protocol that starts at issuance directly, depending on needs of credential type.
- we need to be careful not to match protocol to UX human steps on a 1 to 1 basis
- abandoned state - if a user declines to present, what should happen between the holder and verifier?
- problem report sent (or no message, see below) on decline - should be documented
- explicit 'no' messages instead of a problem report when it's an explicit no, instead of an error.
- document use of timeout for offers (didcomm v2 friendly, perhaps a field within the protocol.Credential Protocols for DIDComm v2
- Any Volunteers?
- (Notes from previous weeks)
- Basis for common identifiers
- Long time since discussion
- Governance has come a long way: https://github.com/decentralized-identity/credential-trust-establishment
- 530 - human readable verifiable identifier
- 535 - email access governance framework
Other Business
Future Topics
- Niels Klomp offered a deeper dive into the openid4vc related flows
- decorator for redirection after proofs. - existing?
- in the Aug 9 call there was talk about EUDI compatibility. Maybe tracking the progress every now and then in these calls? Has there been any discussion about adding SD-JWT and OID4VC stuff to Aries Interop test suite?