Page History

...

Discussion Topics

• did:tdw followup
  • https://bcgov.github.io/trustdidweb/
  • https://github.com/bcgov/trustdidweb/issues
• Charter Review:url
  Widget Connector
  • LFDT: https://www.linuxfoundation.org/press/linux-foundation-announces-intent-to-form-lf-decentralized-trust
  • Charter Draft:
  • https://docs.google.com/document/d/1F6RbR7xDaBt5CDJhqLJzR4c1pDJtyPGshp9fy6eVtSM/edit

  
  

  
  

  • 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
    • https://hyperledger.github.io/aries-rfcs/latest/features/0496-transition-to-oob-and-did-exchange/
    • Step 1 (Accept OOB Invitations) needs confirmation - Please Do This.
      • Bifold using OOB, but then connections (allowed for transitions)
    • Step 2 - use OOB and implement DID Exchange
    • Known systems possibly still using Connection Invitations
      • Lissi 
      • Dock
      • GlobalID
      • Trinsic
    • PRs for adoption status welcome
  • 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.
  • Interopathon?
    • Discuss post EIC
    • Virtual
    • potential target end of july
    • participants
      • Aries /  ACA-Py
      • Credo
      • Veramo
    • 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
      • Harmonize Chat
        • https://github.com/decentralized-identity/didcomm.org/pull/106/files
      • Sub connection-Ariel
        • new DID for the connection.
    • QR code short URLs / redirect to large invitations / deep linking in a way that works with iOS and Android
      • https://github.com/hyperledger/aries-rfcs/blob/main/concepts/0700-oob-through-redirect/README.md
      • BCGov working on something similar.
  • 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.

  ...