Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Add examples of real world use

...

  • Sufficient real world use
    The project should be used in real applications and not just in demos. Because not all real applications may be discussed publicly, in such cases statements providing as much details as possible should be made.

    • Response: Government of British Columbia's OrgBook is in production using multiple instances of ACA-Py to issue verifiable credentials to an enterprise holder (wallet).
    • Response: SecureKey uses aries-framework-go in several TrustBloc projects as a verifiable credential agent & wallet framework and for verifiable credential handling. Aries Framework Go is used within servers, within mobile (via gomobile build) and within the browser (via WASM build). SecureKey has also built DID method integration for Hyperledger Fabric, used the framework with other DID methods, and are also working towards a new ledger-agnostic DID method (did:orb) that we plan to integrate to aries-framework-go. We have also included components that consume Aries-Framework-Go in an interoperability plugfest (example: w3c ccg). 
    • Response: Evernym has implemented AIP 1.0 in its Connect.Me mobile credential wallet app (currently available for download on Android and iOS).
    • Response: Evernym has implemented AIP 1.0 in its Verity verifiable credentials platform product, which currently serves 300+ production customers.
    • Response: Lumedic has begun issuing COVID-19 vaccination credentials within the Providence Healthcare Organization using AIP 1.0.
    • Response: The National Health Service in the UK is issuing Aries-compatible vaccinator certification credentials to healthcare and military personnel as part of their push to vaccinate the public for COVID-19.
    • Response: Credit unions in the US have been using the MemberPass mobile credential wallet app, implements AIP 1.0, to issue credit union membership credentials to their members since late 2020.
  • Sufficient scalability
    The project must demonstrate sufficient scalability and document its scalability over various dimensions such as:

    • Maximum number of transactions per second

      • Response: Current highest transactions rate is 1200 issued verifiable credentials per minute, however, multiple options for scaling are available.
    • Maximum number of transactions per chain

      • Response: N/A
    • Maximum size of a block

      • Response: N/A
  • Minimum test code coverage expected, such as, for example:

    • Minimum coverage for Security & cryptography

      • Response: Some Aries frameworks embed Hyperledger Ursa for cryptography. Other cryptographic components are embedded libraries. No cryptographic components are developed in Aries implementations.
      • Response: A great deal of the focus of the lowest level Aries protocols (DIDComm) was built based on security best practices using guidance from a number of experts in a variety of organizations.
    • Minimum coverage for other functionality

      • Response: As noted, ACA-Py has about 99% unit test coverage (per codecov) and a full integration test library at the Aries protocols level covering AIP 1.0.
    • Minimum coverage for Business logic/smart contract

      • Response: N/A