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

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

Summary:

  • Release planning and update on recent PRs and Issues

  • ACA-Py Name and Logos

  • New DIDComm Protocols – Workflow, Payments, Signing and Vault

  • 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/AVOp9603875cm8376024feIVyNA5_9Qc0egwSCUDBoztTzaaso7Dh0AqEsH-QhlI.3hPJ09v-p6f_Lu6M

 

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

Welcome, Introductions and Announcements

Announcements:

Documentation:

Agenda

  • Status of 1.4.0 release – what needs to be included?

  • New name and logo – discuss – ACA-Py Issue 3929:

    • Proposed Name: Adaptive Cloud Agent - Python (ACA-Py). From Patrick St. Louis:

      • When ACA-Py moved to Open Wallet Foundation, we definitely wanted to keep the name ACA-Py, but obviously Aries wasn't applicable anymore. So we were left with ACA-Py, which was what used to be an acronym, and now it was just a name. So I was thinking how we could create an acronym, that keeps ACA-Py.

        Obviously the “Cloud Agent” part should remain, so I was trying to find a word that starts with A that could replace the first word.

        I think is the best option was the word adaptive, making ACA-Py Adaptive Cloud Agent – Python.

        Adaptive works because it shows a progression, and that this is a Cloud Agent that can adapt to different standards and different technologies that come about.

      • Yes or No?

      • After discussion, the group decision was YES.

        • Issue to be updated, documentation updates to be made.

    • Proposed Logos – choice? After discussion, the feedback was that the first is “too busy”, and needs to be adjusted into a square to work better as a favicon and the like, and the second was “not busy enough”. We’ll see about finding someone to work from these proposals and feedback to come up with a refined design (or not). If not, the leaning is to the second.

      • From Patrick St. Louis:

        • The idea is that you have the shape of a cloud with multiple arrows moving forward, which represent different work items for people to bring the project forward. Kanon is a good example, WebVH another. Whatever things that people contribute to the project, and all these contributions are moving the project forward – making it adaptive.

          Another analogy that could be derived from this logo is that if you look at the cloud section, it's separated in three different sections, and you can picture these as the three core roles of SSI: issuer, holder, and verifier, which are all being brought forward by new implementation, showing that the project adapts to new and emerging standards.

          image-20250916-152847.png
      • From John Jordan :

        • The following ACA-Py logo embodies the principles of decentralized trust and interoperability. Three independent arcs form an implied triangle — a visual metaphor for the trust triangle between issuer, holder, and verifier. Each element stands apart, emphasizing autonomy, yet their alignment conveys mutual confidence and shared integrity. The design’s open geometry reflects ACA-Py’s protocol-agnostic architecture and future-oriented scalability, while the bold orange accent represents proof and verification in motion. The result is a mark that is technically precise, minimalist, and human-centered — mirroring ACA-Py’s role as a foundational, flexible component in the verifiable data ecosystem.

        image-20251014-144942.png
  • Presentation from the VeriDID team on their new DIDComm protocols – Workflow and Payments.

  • Open Discussion.

 

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

Important Links:

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