...
- BC Gov Code With Us – AnonCreds in W3C Format – Application Period open until October 20, 2023.
- AnonCreds Rust Updates – Awarded to DSR Corporation – https://github.com/hyperledger/anoncreds-rs
- AnonCreds Rust Changes Deployed in ACA-Py – Awarded to What's Cookin' Inc.
- AnonCreds Rust Changes Deployed in Aries Framework JavaScript and Aries Bifold – Animo Solutions
- Adding DIDComm to the VC Playground issuer exchange services - considering using ACA-Py
- Enabling CHAPI initiated credential exchange to be stored in an Aries agent (considering aca-py, afj or vcx)
...
- Stephen Curran (BC Gov/Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>
- Alexander Shcherbakov (DSR Corporation) <alexander.sherbakov@dsr-corporation.com>
- Warren Gallagher (AffinitiQuest) <warren@affinitiquest.io>
- Colton Wolkins (Indicio) <colton@indicio.tech>
- Patrick St-Louis (IDLab) <patrick.st-louis@idlab.org>
- Emiliano Suñé (BC Gov / Quartech) <emiliano.sune@quartech.com>
- Daniel Bluhm (Indicio PBC) <daniel@indicio.tech>
- Kim Ebert (Indicio PBC) <kim@indicio.tech>
- Jamie Popkin (BC Gov / Little Earth Spatial Programming Inc.) <popkinj@littleearth.ca>
Announcements
- ACA-Py documentation: https://aca-py.org
...
- Release 0.11.0 status
- Status: Moving AnonCreds RS Branch into Main
- Created branch, manually pulling across code net new and integration – all unit tests passing
- Endpoints hooked up – new /anoncreds endpoints – not the existing endpoints
- New wallet type "--wallet-type askar-anoncreds"
- Status: Load Generator – moving along – migrating to Askar for the load agent
- Status: AnonCreds in W3C VC Format
- Demo: Traction Sandbox – a new utility for the ACA-Py community
- AnonCreds Traction Workshop
- Create Tenant
- Make Issuer
- Create Schema
- Create CredDef
- Generate Invitation
- Establish Connection
- Issue Credential
- Present Proof
- Use the API – the important part!!
- Traction Issuer Example
- AnonCreds Traction Workshop
- Update on Please Ack "~please_ack":
- One party can request an
Ackon any message – either to be returned on receipt, or on outcome of the message. - Other party MAY send an extra
Ackmessage. - Tricky to implement:
- Generic ACA-Py
on receiptis not as easy as it could be. Possible, but requires some rework.- Is the message a generic Ack or an adopted Ack
on outcomedefinitely requires per protocol updates at least, plus logic for determining when the outcome of a message is known.- Isn't required on many messages, as once the message outcome is determined, a message is immediately generated and sent. What help is sending another message in parallel?
- Where it is most likely to be useful – at the end of a protocol when there is no other message – making it useful may mean altering the protocol.
- Issue Credential – should it be sent when the protocol "completes" or after the controller/business process decides to keep the credential.
- Present Proof – should it be sent when the credential is cryptographically verified, or when the controller/business process decides the credential satisfies the business need?
- If ACA-Py deletes the protocol state object automatically when the controller is sent the verification result, how can the protocol be kept for an optional "Ack"?
- Basic Message – could (in theory) be used to enable "received" and "read" notifications of basic messages, but the "read" notification would extend the protocol lifetime from when the controller received the message, to when an event happened inside the controller. Tricky!
- Requesting
~please_ack:- The configuration or the admin API would have to be updated to add the ability for the controller to say, "Hey, I want a
~please_ackadded in these places..." - How do applications (wallets, etc.) want to use the
~please_ackfeature?
- The configuration or the admin API would have to be updated to add the ability for the controller to say, "Hey, I want a
- Generic ACA-Py
- One party can request an
- Other PRs Ready for Review and Issues to Discuss
...