2025-06-10 - ACA-Py Users Group Community Meeting

Summary:

Call Time: 8:00 Pacific / 17:00 Central Europe

Zoom Link:

https://zoom-lfx.platform.linuxfoundation.org/meeting/96618113800?password=3fb31a65-606d-4765-8f89-ce7c857dc049

Call Recording:

https://zoom.us/rec/share/-z0tJ-P9bTGUSIV7EeUO7a3WYFACgfGL89zpOACky7a43ZCRZlDR0x8LgMx11gc5.GWyKmOLCwBw6efdb

Demo about Kanon:

Welcome, Introductions and Announcements

Announcements:

• Wallet Interop SIG: [WISIG] Wallet Interoperability SIG – NOW ON MONDAYS -- 8:00 Pacific / 17:00 Central Europe

  • Yesterday: Bifold Wallet

  • Next Week: DID Method Standardization Working Group

  • Want to present? Sign up here

Attendees:

• Stephen Curran (BC Gov/Cloud Compass Computing Inc.) swcurran@cloudcompass.ca

•  

Documentation:

• ACA-Py documentation: https://aca-py.org

• ACA-Py Plugins: https://plugins.aca-py.org

Agenda

• Release 1.31.rc1 out – feedback?

  • Still need an LTS Job Fix – try 1 and 2 didn’t work… Jamie is working on it. Will be a GHA that is disabled on main, enabled on LTS branches.

• Issue from 4Sure: URL character limit with certain OS and industry tools, impacting the use of OOB Credential Issuance/Verification

  • Issue: When an OOB connection-less issuance, URL with the query parameters – the URL does not get resolved.

    • Doing URL-shortening, so the QR code size is reasonable. But on the redirect, the URL size is very large, as it includes the credential offer as well. Is there something else that could be done here – e.g. return the value vs. a redirect.

    • 80k character limit on iOS – not sure of Android.

    • With AWS and using a load balancer, the limit is 20K.

• Potential RevReg handling optimizations – recap from yesterday’s AnonCreds meeting

  • Presentation

    • Reuse the same tails file for every RevReg related to CredDef. Issuer only change – reduces the load on the Issuer.

      • Still need to publish each RevRegDef object and initial RevRegEntry, but RevReg creation is trivial.

    • In did:webvh (for a start), combine many RevRegEntries into a single file per timestamp.

      • Logistics of the identifier and ledger resource contents.

      • Should be a minor variation on what we are doing today.

    • Double the size of RevRegs by compressing Tails File 768Kb for a 3k Credential RevReg

      • Challenge – ensuring holders in an ecosystem can handle the change before issuers start to use it.

      • Addresses at least a part of the Phone Home challenge as it manifests in AnonCreds.

    • Next steps:

• Kanon Updates – Starts at 28:47 in the recording.

  • Video of demo of Kanon Normalized – using a normalized database structure to store non-key ACA-Py data.

    • Demo about Kanon:

  • Support for Mongo DB is close to completion, so we will have SQLite, Postgres and MongoDB in the final version.

  • Plan is to work on a PR to be ready Real Soon Now.

  • Current documentation about Kanon, including the development status:

• Concurrency challenges in ACA-Py, such as Issue #3738 – Let’s discuss…

  • Presentation

  • Next steps:

    • Evaluate the possible locking solutions, including the one that DIDx is using in the interim.

    • Select and implement a solution that provides both a good abstraction, and the ability to add implementations based on the capabilities available in any given deployment.

    • Identify other places in the codebase where a lock is needed.

• Open Discussion

Requests

• ACA-Py NEWS? The OWF Newsletter goes out on the third Thursday of each month (in 2 days). If there is ACA-Py news, please send a note to community-architects@openwallet.foundation
  
  

Upcoming Meeting Topics:

Important Links: