2024-09-18 Aries Working Group Call not held, OWF Meeting about Aries
Summary:
- OWF Meeting (Meeting Page) about the Project Proposals related to Aries
Zoom: https://zoom.us/j/93803916577?pwd=UWdLSTJ2b0kvZTRyc1hZTUdQQ3ZFZz09
OWF Meeting Recording: https://zoom.us/rec/share/FR0KhJVyIOqyJ1NANu0iM6iZRYhghRdScAj-8Dga1OM4xyz3wcFAJx_W4vEVQPX5.mZnwv-4bxqgukjFA
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.tech) <sam@indicio.tech>
Welcome / Introductions
Announcements
- Aries BBS Go has been created, and a VC-DI-BBS Go implementation has been added as a Hyperledger Lab
- did:tdw - Moved to DI. Regular meetings start tomorrow.
- Meeting Agenda and Zoom link: https://hackmd.io/k4cIK9vQSlaeg2pdHE51IQ?view
Release Status and Work Updates
- Implementations:
- Aries Cloud Agent Python https://github.com/hyperledger/aries-cloudagent-python, Meetings: ACA-Pug Meetings, Documentation: https://aca-py.org
- Credo https://github.com/openwallet-foundation/credo-ts, Meetings: Credo Meetings
- Bifold Wallet -- https://github.com/openwallet-foundation/bifold-wallet Meetings: Bifold Meetings
- Aries VCX (https://github.com/hyperledger/aries-vcx, Meetings: Aries-VCX Meetings
- Proposal to move Aries VCX to the Open Wallet Foundation - https://github.com/hyperledger/aries-vcx/discussions/1285
- Are you using the Indy SDK for Aries VCX, please let us know, as we're looking to remove support from Aries VCX - https://github.com/hyperledger/aries-vcx/issues/1250
- 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)
- 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
- Aries Askar secure storage - https://github.com/bcgov/aries-askar
- AnonCreds Rust - https://github.com/hyperledger/anoncreds-rs
- Shared Rust Library/CredX (AnonCreds) https://github.com/hyperledger/indy-shared-rs - being replaced by AnonCreds Rust
- aries-mediator-service – a DIDComm Mediator in a Box
- aries-endorser-service – an Indy Endorser in a Box (in development)
- Aries Akrida - Load Testing DIDComm based protocols
Discussion Topics
- Future of Aries Discussion--Project Proposals accepted by OWF
- https://lists.hyperledger.org/g/aries/message/1117
- Context -- Presentation from last week to facilitate discussion
- Presentation to facilitate for this week's discussion - extended to summarize the conversation from last week
- Google Doc of draft proposals from BC Gov for OWF
- 2024-9-03 Aries VCX Community CallAries VCX discussion applying to move to OWF
- Discussed at the Sept. 3 Aries VCX Community Call
- Leave RFCs in a 'frozen' state - updates allowed that point to new work.
- AIPs move forward in OWF
- DIDComm related RFCs move forward in DIF DIDComm UG
- Combine AATH with Mobile Test harness and Akrida
- Draft Project Message
- Process
- Planning/ Submission
- Docs ← We are Here
- PRs
- Messaging Draft
- Discussion/approval
- Meetings and TAC voting
- Execution
- Meeting adjustments
- Actually Moving Repos
- Pipeline adjustments
- Marketing - Sam to drive prep
- ACA-Py 1.0 announcement
- BC Announcement Moratorium next week or so until at least early November
- Planning/ Submission
- PR Review
- Mid-Transition Work Items
- Continued project advancement
- No need to adjust code contributions
- Community Coordinated Updates
- Continued project advancement
- Unqualified DIDs
- https://hyperledger.github.io/aries-rfcs/latest/features/0793-unqualfied-dids-transition/
- Progress?
- ACA-Py working on 1.0, this will be the SECOND major release (0.12.1) of ACA-Py that has accomplished step 1
- Ongoing successful testing with Credo.
- did:indy handling
- unqualified anoncreds objects being rejected
- did:indy changes the unique identifier within the DID. both the old method and the new method should work.
- Credo is using did:indy only, cannot resolve unqualified asset identifiers.
- Rushed work to address within AnonCreds RS ( ? ) and ACA-Py.
- quicker fix in Credo, longer fix in everything.
- PRs for adoption status welcome
- OOB Invitation / DID Exchange CCU
- https://hyperledger.github.io/aries-rfcs/latest/features/0496-transition-to-oob-and-did-exchange/
- Step 1 (Accept OOB Invitations) needs confirmation - Please Do This.
- Bifold using OOB, but then connections (allowed for transitions)
- Step 2 - use OOB and implement DID Exchange
- Known systems possibly still using Connection Invitations
- Lissi
- Dock
- GlobalID
- Trinsic
- PRs for adoption status welcome
- DIDComm v2 adoption
- ACA-Py progress shared last week
- PR made for initial support. first round trip support.
- Any other updates?
- Credo has the beginnings of DIDComm v2, but does need some attention.
- ACA-Py progress shared last week
- In person offline presentation
- Transport
- BLE DIDComm transport
- ISO/mDL
- Caching Strategies
- Knowing what to cache
- Credential Trust Establishment spec
- Keeping things cached, and use cached state
- verifier decides if it's new enough
- revocation check
- don't include proof of non-revocation if not asked
- can't be ignored?
- Knowing what to cache
- don't do indy edits on cred defs and schemas
- is this already a rule? if not, it should be.
- edit rule does exist. but why?
- Transport
- Interopathon?
- Discuss post EIC
- Virtual
- potential target end of july
- participants
- Aries / ACA-Py
- Credo
- Veramo
- Identus
- scope
- unqualified DIDs gone
- did rotation
- v1 - v2
- DIDComm v2
- trust ping?
- discover features?
- basicmessage?
- did rotation after connection
- didcomm demo interaction
- advanced tasks
- credential issuance / presentation
- unqualified DIDs gone
- Open Discussion
- Validation of printed OOB Invitations
- DID must be present in governance file?
- Proof provided according to matching governance files.
- prove well known dids other than the current connection.
- JSON-LD creds impl within ACA-Py no longer working with Credo 0.5.0
- Sphereon library using for Presentation Exchange objects is not expecting quite the same things, additional fields.
- Daniel working through and testing, will report / create issues on the appropriate repos.
- Updates?
- Fix merged into ACA-Py.
- funny interactions between the speheron libraries and credo about presentation exchange. - issues raised to Timo et. al.
- Protocol RFC
- Harmonize Chat
- Sub connection-Ariel
- new DID for the connection.
- QR code short URLs / redirect to large invitations / deep linking in a way that works with iOS and Android
- https://github.com/hyperledger/aries-rfcs/blob/main/concepts/0700-oob-through-redirect/README.md
- BCGov working on something similar.
- Validation of printed OOB Invitations
- Mediator Reconfig revisit
- (from last week)
- 3 new messages
- updatedconfig - new routing DID
- note about timing or avoiding causing a traffic stampede as a result.
- ack- received by
- updated downstream (keylist updates as alternative?)
- updatedconfig - new routing DID
- need for this:
- anytime a mediator needs to change the routing DID
- static DID, but also other cases.
- loss of data at the mediator
- all routes lost.