Versions Compared

Old Version 1

changes.mady.by.user Stephen Curran

Saved on

compared with

New Version Current

changes.mady.by.user Stephen Curran

Saved on

Key

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

Summary:

Excerpt
  • Future of Aries Discussion Part III
  • Open Discussion


Zoom: https://zoom.us/j/93803916577?pwd=UWdLSTJ2b0kvZTRyc1hZTUdQQ3ZFZz09

Recording: :
Widget Connector
urlhttp://youtube.com/watch?v=WHagD5vfz-Q

Date

(7AM Los Angeles, 10AM New York, 3PM London, 4PM CET, 18H Moscow)


move


Hyperledger is committed to creating a safe and welcoming

community for all. For more information

please visit the Hyperledger Code of Conduct.

Attendees

  • Sam Curren  (Indicio) <sam@indicio.tech>Stephen Curran (Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>
  • James Ebert  (Consultant / Instnt) <james@jamesebert.dev>
  • bruce_conrad@byu.edu (Pico Labs) <picolabs@sanbachs.com>
  • Steve McCown (Anonyome Labs) <smccown@anonyome.com>
  • Kim Ebert (Indicio) <kim@indicio.tech>

Welcome / Introductions

Announcements

...

...


  • Unqualified DIDs 
    • https://hyperledger.github.io/aries-rfcs/latest/features/0793-unqualfied-dids-transition/
    • Progress?
      • ACA-Py working on 1.0, this will be the SECOND major release (0.12.1) of ACA-Py that has accomplished step 1
      • Ongoing successful testing with Credo.
    • did:indy handling
      • unqualified anoncreds objects being rejected
      • did:indy changes the unique identifier within the DID. both the old method and the new method should work.
      • Credo is using did:indy only, cannot resolve unqualified asset identifiers.
      • Rushed work to address within AnonCreds RS ( ? ) and ACA-Py. 
      • quicker fix in Credo, longer fix in everything.
    • PRs for adoption status welcome
  • OOB Invitation / DID Exchange CCU
  • DIDComm v2 adoption
    • ACA-Py progress shared last week
      • PR made for initial support. first round trip support.
    • Any other updates?
    • Credo has the beginnings of DIDComm v2, but does need some attention.
  • In person offline presentation
    • Transport
      • BLE DIDComm transport
      • ISO/mDL
    • Caching Strategies
      • Knowing what to cache
        • Credential Trust Establishment spec
      • Keeping things cached, and use cached state
        • verifier decides if it's new enough
        •  
      • revocation check
      • don't include proof of non-revocation if not asked
        • can't be ignored?
    • don't do indy edits on cred defs and schemas
      • is this already a rule? if not, it should be.
      • edit rule does exist. but why?
  •  Interopathon?
    • Discuss post EIC
    • Virtual
    • potential target end of july
    • participants
      • Aries /  ACA-Py
      • Credo
      • Veramo
      • Identus
    • scope
      • unqualified DIDs gone
        • did rotation
        • v1 - v2
      • DIDComm v2
        • trust ping?
        • discover features?
        • basicmessage?
        • did rotation after connection
        • didcomm demo interaction
      • advanced tasks
        • credential issuance / presentation
  • Open Discussion
    • Validation of printed OOB Invitations
      • DID must be present in governance file?
      • Proof provided according to matching governance files.
      • prove well known dids other than the current connection.
    • JSON-LD creds impl within ACA-Py no longer working with Credo 0.5.0
      • Sphereon library using for Presentation Exchange objects is not expecting quite the same things, additional fields.
      • Daniel working through and testing, will report / create issues on the appropriate repos.
      • Updates?
      • Fix merged into ACA-Py. 
        • funny interactions between the speheron libraries and credo about presentation exchange. - issues raised to Timo et. al.
    • Protocol RFC
    • QR code short URLs / redirect to large invitations / deep linking in a way that works with iOS and Android
  • Mediator Reconfig revisit
    • (from last week)
    • 3 new messages
      • updatedconfig - new routing DID
        • note about timing or avoiding causing a traffic stampede as a result.
      • ack- received by 
      • updated downstream (keylist updates as alternative?)
    • need for this:
      • anytime a mediator needs to change the routing DID
      • static DID, but also other cases.
    • loss of data at the mediator
      • all routes lost.

...