Summary:
Excerpt |
---|
Topics:
|
...
Call Time: 8:00 Pacific / 17:00 Central Europe
Recordings From the Call: :
Widget Connector | ||
---|---|---|
|
Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct. |
---|
Welcome, Introductions and Announcements
...
- Stephen Curran (BC Gov/Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>
- Emiliano Suñé (BC Gov/Quartech) <emiliano.sune@quartech.com>
- Wade Barnes (BC Gov / Neoteric Technologies Inc.) <wade@neoterictech.ca>
Documentation:
- ACA-Py documentation: https://aca-py.org
...
- Status Updates:
- AnonCreds RS in ACA-Py
- PRs for AnonCreds+CredX concurrently – after the 0.12.0 release
- Upgrade script – PR in draft – still being worked.
- did:peer and AFJ Interop
- Connection reuse for did:peer:2/4
- Credo/ACA-Py defined need to support 1.0 and 1.1 of DID Exchange. Need to get the implementation done.
- Respond in kind being done as well.
- In the extraordinarily capable hands of Daniel Bluhm
- DID Rotation – PR #2816 – Akiff Manji Merged.
- Status of DRPC – working, adjustment to the protocol to support a problem reportMerged.
- AnonCreds RS in ACA-Py
- Status of ACA-Py 0.12.0
- Additional PRs to go into the release? Yes – list:
- VC-API Endpoint – need to re-add VerificationMethod
- VC-API question:
- Old: Verkey to sign and issuer as input
- New: Issuer provided, resolve key to sign
- Propose: Additional way, create a DID, publish it twice (Indy, did:web), choose the one to be used for signing – either resolves to the same public key.
- Current way – use the same seed for two DIDs.
- DID Alias? "alsoKnownAs" – need additional metadata to use the alsoKnownAs as searchable metadata
- post 0.12.0
- Additional concepts? No
- Additional PRs to go into the release? Yes – list:
- Status of ACA-Py 1.0.0 Release:
- Checklist Issue, labelled Issues and PRs
- Other issues/PRs to be added?
- Should we wait on the AnonCreds RS work?
- LTS Considerations per Aries RFC 0799 Long Term Support
- Other considerations?
- Checklist Issue, labelled Issues and PRs
- ACA-Py Traceability Traction Test Suite Controller – being deployed
- JSON-LD credentials with did:web, interact with other implementations – ed25519 signature
- POST requests to exchange – with OAUTH2 tokens, including an implementation of StatusList2021
- Specific to supply chains use cases and traceability vocab defined at W3C.
- Compatibility with the VC-API
- Potential to add ACA-Py/Traction Controller to the https://canivc.com/ interoperability test suite.
- Repo available to use with docker, now adding k8s helm charts being added and an ongoing interop testing.
- Same priniciples as AATH – all implementations can talk to one another.
- Hyperledger Mentorships – Indy (Read Replicas) and AnonCreds (Revocation Manager implementation)
- Other PRs Ready for Review and Issues to Discuss
- Multi-instance ACA-Py by default.
- Redis or kafka plugin for message queuing
- Redis for cache handling.
- Biggest issue was in connection establishment – caching disabled for that now – biggest risk eliminated
- Makes local only viable – DID Rotation is exception.
- Need for a "cluster-wide event bus" – e.g, redis event bus to notify events.
- Currently using the database for polling for events that may happen on other instances.
- Revocation is a primary user of this.
- Trade-off – need to have a third-party dependencies.
- Need this for Mediator based on ACA-Py using SocketDock.
- Multi-instance ACA-Py by default.
Upcoming Meeting Topics:
- Multi-architecture containers
- Issue with BBS+ package – doesn't support ARM containers – need an update to their CI
- Solution: A third container published that includes BBS+ package, but is single architecture
- Others are Askar
...