Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Summary:

...

Excerpt

  • Progress

...

  • of the move to OWF

  • Release 1.1.0rc0

  • Next Release – PRs and Issue

  • Preparing a Webinar about ACA-Py – What to cover?

Call Time

Zoom Link:

https://zoom-lfx.platform.linuxfoundation.org/meetings/openwalletfoundation?view=week&occurrence=1729004400

Call Recording: Recording of Meeting / Transcript

YouTube: https://youtu.be/m3YrU29T-0M

Welcome, Introductions and Announcements

...

Documentation:

...

  • Progress on move to OWF

    • Almost there…PyPi publication is the only hold up – new release candidate to test that out.

    • Plugins – run actions only on OWF branch – all working. Pending release of ACA-Py to complete the actions.

  • Release 1.1.0rc0

    • 1.1.0rc1 will be today.

    • Will complete and push out 1.1.0 as soon as the PyPi issue is resolved.

  • Next Release – PRs and Issues

  • Preparing a Webinar about ACA-Py – What to cover?

    • Overview

    • Demo – Traction and schema

    • Architectural Overview and Features Tour

      • Blocks, Lines and Concepts

      • Configuration

      • Secure Storage

      • OpenAPI

      • DIDComm

    • Business Use Cases / Governance

    • Flexibility:

      • DIDs – supported, adding more

      • OpenID4VCs and SD-JWTs

      • VC-API and Publishing Credentials

    • Roadmap

  • Hardcoded DIDs – eliminating them!!

    • Making it easier to use new DID methods, new AnonCreds objects.

    • E.g. Updating ACA-Py to use the Cheqd, Hedera, did:tdw, did:web, or Indy on Besu ledgers

      • AnonCreds endpoints currently only support Indy

      • Issue Credential 2.0 – somewhere you get a ledger transaction – code assumptions of using ledger object vs. registry.

      • Work to do there – let’s get coordinated on getting that done for

      • Change from a pre-registered registry vs. dynamically based on the DID being used (did:web, did:cheqd, etc.).

      • Public DID currently must be a did:sov – that HAS to change. It has to be published somewhere, but that is all.

        • Used in OOB when a connection is being established – if something else is not specified.

Upcoming Meeting Topics:

  • Codespaces

  • Logo

  • Hardcoded DIDs – eliminating them!!

Future Topics:

Action items

...