Summary:
Excerpt |
---|
|
...
(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
...
- 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
- Release 0.4.0 soon/this week(?) (0.4.0.dev.12 most recent)
- 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.8 soon/this week(?) (0.2.8.dev.6 most recent)
- AnonCreds Rust - https://github.com/hyperledger/anoncreds-rs
- Release 0.1.0 soon/this week(?) (0.1.0.dev.11 most recent)
- Shared Rust Library/CredX (AnonCreds) https://github.com/hyperledger/indy-shared-rs - being replaced by AnonCreds Rust
- Release 0.3.2 tagged
- 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
- 0.8.1 released – focused on the upgrade command, most relevant to multi-use invitations – including mediators.
- New documentation site: https://aca-py.org
- Aries-Framework-JavaScript https://github.com/hyperledger/aries-framework-javascript, Meetings: Framework JS Meetings
- Version 0.3.3 released - https://github.com/hyperledger/aries-framework-javascript/releases
- Version 0.4.0 in progress - https://github.com/hyperledger/aries-framework-javascript/releases/tag/v0.4.0-alpha.87
- Aries VCX (https://github.com/hyperledger/aries-vcx, Meetings: Aries-VCX Meetings
- Release 0.53.0 https://github.com/hyperledger/aries-vcx/releases/tag/0.53.0
- Picos as Aries agents (https://github.com/Picolab/aries-cloudagent-pico)
- Phil Windley has students working on a DIDComm v2 version of ACA-Pico
- Less active repos:
- Aries-Framework-Go (Troy) #aries-go (https://github.com/hyperledger/aries-framework-go, Meetings: aries-framework-go)
- Aries-Framework-DotNet (https://github.com/hyperledger/aries-framework-dotnet)
- 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
- Bifold Summit Happening now – Bifold Summit 2023
- BCGov has realeased an Aries Bifold version, rebranded w/ BC blue/theme/etc (BC wallet)
- 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
- aries-endorser-server – an Indy Endorser in a Box (in development)
- Aries-Toolbox
- Ursa (https://www.hyperledger.org/use/hyperledger-ursa, https://github.com/hyperledger/ursa)
...
- DID Peer 2/3 – processing approach – is this the plan:
- Identifiers:
- Long Identifier – as defined today, entire encoded DIDDoc in identifier
- Short identifier is the first 22(?) characters of 64 character string sha256 of long identifier (or something else?)
- On receipt of a did:peer:3<identifier>, process as follows:
- Detect length of identifier — short or long (assumption: long peer:did:2 will never be less than 23(?) bytes)
- If short - resolve DID locally to get DIDDoc - on success, exit
- If short and resolution failed — error, exit
- If long
- Convert long DID to short DID - resolve DID locally to get DIDDoc - on success, exit
- If long and short DID resolution failed
- Resolve long DID locally to get DIDDoc — on success, exit
- if both short and long DID resolution fails
- If on a “create DID” step (e.g. receiving DID Exchange “request” or “response” or DIDComm 2 new protocol step)
- Extract DIDDoc from long DID, store short DID and DIDDoc, get DIDDoc — on success, exit
- Otherwise —
- erroryes
- If on a “create DID” step (e.g. receiving DID Exchange “request” or “response” or DIDComm 2 new protocol step)
- Identifiers:
Other Business
Future Topics
...