2026-06-23 - ACA-Py Users Group Community Meeting

2026-06-23 - ACA-Py Users Group Community Meeting

Summary:

  • Status, Plugins Dependabot Process Again, Plugins vs. Core, AnonCreds Cryptosuite, Open Discussion

Call Time: 8:00 Pacific / 16: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/xxsTfICfACzeMXw7cr1qFt_mkHdOU0uiJk797_p3rOtUhXyxw-yGu-QKKZAd9SOP.1SqFULC1gJIporeF

image-20241112-180131.png
image-20241112-180041.png

Welcome, Introductions and Announcements

Announcements:

  • Big Bifold Meeting

  • Pydentity Wallet demo updated

Documentation:

Agenda

  • Status

  • Plugins Dependabot Process - another update with the help of Claude:

    • Process from last two meeting, plus:

      • Updated the “7” option (update all libraries for a given library) to:

        • Automatically scan the open dependabot issues to find the libraries to update

        • Run the update for all of those.

      • Added an option “9” that deals with dependabot updates that update pyproject.toml files

        • Scans all dependabot PRs to find ones that update the pyproject.toml

        • Checks all pyproject.toml files that have an exact match of the library version being updated from.

        • Flags all pyproject.toml files that have a different version of the file – left of a manual update

        • Runs the update lock file update process on this instances.

      • Propose we drop the “8” option – close PRs, as better to let dependabot close them, so we can see if any are missed in a weekly update.

  • Plugins vs. Core – any thoughts:

    • Kanon

    • OAuth access to Admin API

      • Preference is plugin – faster to develop, easier. Likewise maintainability.

      • But, cannot be “just a plugin” – needs hooks on every API call.

        • What is the hook that can be added? Clever ideas welcome!!

      • OAuth should have been there from day 1…

    • HSM support

      • Same as above – need a hook into the wallet.

      • Approach should be

  • AnonCreds Data Integrity support in AnonCreds W3C VC Support

    • type vs. cryptosuite

    • Recall the process:

      • Issuer – generates “native” AnonCreds proof, and moves data around to format as DI proof.

      • Verifier – received DI proof, moves data around to format as AnonCreds proof, verifies “native” AnonCreds proof

  • Open Discussion

  • Housekeeping

Important Links:

Discord: https://discord.com/invite/yjvGPd5FCU (Click Accept Invite, check out the #aca-py channel)