Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Summary:

Planned Topics:

  • Status Check: ACA-Py Release 0.7.0
  • Performance Issue Update – Public DID Handling
  • Discussion: What's next/getting to Release 1.0.0
  • AMA (as time permits)

Recording from the call:

  • Full recording: 

Hyperledger is committed to creating a safe and welcoming

community for all. For more information

please visit the Hyperledger Code of Conduct.

Welcome and Introductions

Attendees

  • Name (Organization) <email>
  • Stephen Curran Stephen Curran (Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>

Announcements

Deployments and Work Updates

  • BC Gov Team
    • Aries-VCR/OrgBook BC Deployment
      • In progress: a multi-tenant OrgBook Issuer
    • Issuer Kit - VCs for OIDC Issuer Service - Safe Entry BC PoC - VCs for Physical Access Points
    • Verification Tutorial – multi-purpose verifier aimed at the general population receiving their first verifiable credential
    • Aries Agent Test Harness work - Results page: https://aries-interop.info
    • BPA - Business Partner Agent for B2B use of VCs
    • AIP 2.0
    • Aries Shared Components – indy-vdr, indy-shared-rs and aries-askar

Agenda

  • Status Update – ACA-Py 0.7.0 Release – Andrew Whitehead
    • What's left?
  • Performance issue addressed – redundant Public DID Queries – Andrew Whitehead
  • Discussion: What's next in ACA-Py/Getting to 1.0.0
    • Support for did:orb
    • Support for multiple Indy ledgers
    • Support for revised did:sov
    • AIP 2.0 Features (list below)
  • Questions – AMA:

Next Meeting

Future Topics

  • Queues – Daniel Bluhm
    • Actions:
      • Daniel Bluhmto do a hackmd doc design to meet mediator-centric requirements, ideally with a narrative on push notification handling
      • Andrew Whiteheadto do a hackmd doc design to meet scalabilty requirements - https://hackmd.io/OF5o0idQTwi_T_3eWkDvmw
      • Ideally, incorporated into the above, but if not, a third design doc, covering the use of the event bus with the outbound queuing
  • Double Signature with eIDAS?
  • Performance with Shared Components enabled (Aries Askar et al.)
  • AIP 2.0 Features:
    • --version 2.0 flag to enable "breaking changes" features/completed community updates
    • RFC 0557 Discover Features V2 – Added AIP 2.0 features / potentially dynamic based on loaded modules
    • RFC 0519 Goal Codes in specific protocols (RFC 0453/0454 - Credential Exchange V2), OOB, DID Exchange
      • Generalized support?
    • RFC 0627 Static Peer DID Support
    • RFC 0183 Revocation Notification – flag on API to notify user (+ connection_id?)
    • RFC 0587 Encryption Envelope V2
    • Review and update as needed all AIP 1.0 RFCs – to be added: a diff link for each "updated" RF

Action items


  • No labels