Versions Compared

Key

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

...

Welcome / Introductions

Announcements

...

  • Aries Protocol Test Suite
    • One agent under test
    • Issue, credential, and proof tests are merged.
  • Aries Agent Test Harness
  • Aries Shared:
    • Aries Shared:
      • indy-vdr (Andrew Whitehead)
        1
        • 0.
      0
        • 6(?) - most work complete that was needed: Design doc, FFI, testing, CI / CD
          • CI - GitHub actions runs unit tests and basic integration tests
          • CD not there
          • No design doc, but crate docs
    • As an Aries interface becomes standardized, will add that API layer
      • Do we hold off on setting the version until this is in place.  Maybe 0.8
          • Rich Schema merged and behind a feature flag
          • Refactoring PR not merged - cleanup, internal simplification, crate docs
      VON Tails Server created based on indy-vdr created.andrewwhitehead
      • bcgov/indy-credx
        • need to move ASAP to at least BC Gov repo - Andrew Whitehead
            • Experimental ACA-Py branch created that can do credential exchange with indy-credx
          Next up: adding revocation 2.0 support
        • Integrating upgraded PyO3 library
        • home for revocation support?  Or at least shared set membership proof handling?Does
              • (but not
          have
              • anoncreds 1 attribute encoding
          .
              • )
            • Can make a non-revocable credential and create proofs
          .
        • Tagging will be moved to the KMS.
        • Mike will be working on revocation registry 2
            • .
          0 repo?  features?
        • Working on Postgres storage; will need help on lox
        • Something out the end of the week.
            • aries-kms-vostok - indy-wallet capabilities moved to an Aries base
              • Andrew also working on that
      • Aries-CloudAgent-Python (bc.gov)
        • Release 0.5.1 is on PyPi.
        • Revocation support added and tested with Streetcred and esatus Mobile Agents; major/minor version handling
      • Aries-Framework-Go (Troy) #aries-go
        • Implementing the Out-Of-Band protocol
        • Implementing issue-credential and present-proof protocols
        • Edge agent in work based aries-framework-go using WASM with support for DIDs, VCs and DIDComm support being added
      • Aries-SDK-Ruby (Jack)
      • Aries-Framework-DotNet (Tomislav)
        • Release last week for Aries compatibility with ACApy and LibVCX (RFC 0094)
      • Aries-StaticAgent-Python
      • Aries-Toolbox
      • Aries-SDK-Java
      • Aries-Framework-JavaScript
      • Rich Schemas and W3C Verifiable Credentials (Brent & Ken)
        • Some work has been done to support the W3C Verifiable Credentials Data Model specification
      • Aries-MobileAgent-Xamarin (Aries MAX)
      • Ursa
        • 0.4.0 scheduled for late March
          • Improved hash to curve algorithm
          • Updates to AMCL wrapper
        • To replace libsodium, need to have a replacement for the anoncrypt / authcrypt sealed box for pack / unpack.
          • Can be done in Ursa with two steps, but might add as a single function call.

      Agenda:

      Chained credentials (delegated credentials) - Aries RFC 0104: Chained Credentials

      • Substantial update since the last version
      • Chained credential solves the delegation problem but that is not the only one
      • There is no specific requirements to change anything in the VC spec at all. is just about adopting convection
      • VC are head for a problem - same problem as the certificate authorities at the beginning of the web, this what we are trying to avoid is to keep the list of all trusted parties. Instead of small list of entities to trust and cover whole space. 
      • If everyone can be issuers, the problem appears how to keep truck who I can trust. 
      • Data provenance → side the sources into VC
      • We need clever way to do the revocation (wip)
      • logic in verifier code is needed to support chained credentials
      • how nonce is used in embedded proofs: 
        • verifier checks old nonce to verifiy that this happened in the past
      • Does I have to disclose privacy by just letting someone walk up the history upstream of the credentials?:
        •  ZKP veriants and their privacy implications
      • Cross correlation through multiple use - offline
      • Anonymous of the entities in the chain can be achieved. 
      • Late and strong anonymity - is up to the case

      Aries toolbox

      • base Intention: "Postman" for Agent - to help developers to develop agents. 
      • Development tool
      • Administrator tool - to control the agent
      • Demo purposes
      • UI module - corresponds to one or more protocols in the backend
      • Discussion will be continued on the Call B .

      RFC Progress

      Other Business

      ...