Interoperability Task Force

Goals

• Participants will collaborate in a joint-testing-project whereby each development team will:
  • Pair with developers of other participants to work through agreed upon test plans.
  • Partake in joint communications pertaining to the results of this effort.

Methods

Each layer of the Trust over IP technology stack will have  a set of Trust over IP Interoperability Profiles (TIPs), as explained in the ToIP Deliverables repository.

Each TIP represents the needs of a different group of stakeholders.

The work on each TIP is done in a GitHub repository, and coordinated in a GitHub wiki.

TIPs

Saturn-V 

• GitHub repo and wiki: https://github.com/trustoverip/TIP0028-saturn-v
• Use cases: Issuing, Holding, Verifying including connection-less Verification
• Design principles: Designed for privacy (ZKPs and selective disclosure)
• Technology stack: Aries Interoperability Profile (AIP) and Hyperledger Indy
• Test suites:
  • Aries Protocol Test Suite (APTS)
    • Takes a one agent under test approach
    • Has tests specific to AIP 1.0
    • Backchannels available for driving tests with an Enterprise Agency
      • IBM Verify
      • Aries-VCX
  • Aries Agent Test Harness
    • Tests two agents against each other
    • Backchannels available for driving tests with an Enterprise Agency
      • ACA.py
      • Aries-VCX
• Wave 1 (in progress)
  • Validation against Aries Protocol Test Suite for AIP 1.0
  • AIP 1.0 (RFC 302):
    • DIDComm (did:sov)
    • Connection
    • Credentials
    • Proofs
  • Receiving ephemeral proofs using the service decorator
    • Needed for VC-Authn-OIDC (used by BC.gov)
  • Receiving DIDComm with message types defined as https
• Wave 2 (planning)
  • Aries Interop Profile 2.0
    • Out-of-band protocol
      • Ephemeral proofs: send / receive
    • Sending and receiving DIDComm with message types defined as https
  • New MIME Types
  • Validation against both Aries Protocol Test Suite and Aries Agent Test Harness

Vendor Setup Instructions

If you have trouble while testing, please reach out in the Slack channel (see above).

Add your products as:

Vendor

• Mobile holder app
• Issuer / verifier app
• Problem reporting process
• Notes

Evernym

• Mobile app access:
  • demo site with links to downloads
• Issuer / verifier access:
  • Documentation
  • Sign-up
• Problem reporting process
  • Preferred approach is the "Sandbox support"
  • Escalations can be made to richard.esplin@evernym.com
•  Notes:
  • Verity Sandbox defaults to Sovrin StagingNet.
  • Connect.Me defaults to Sovrin MainNet, but during installation there is a toggle switch at the bottom of the screen for switching to Sovrin StagingNet.

IBM

• Mobile app access: 
  • Developer Documentation
  • Account Registration which will send an email with info about the mobile app
  • Contact Dan Gisolfi for the agent Invitation code
• Issuer / verifier app access:
  • Account Registration
  • Developer Tutorial to learn APIs
  • Contact Dan Gisolfi for the agent invitation code

LISSI

• Mobile app access:
  • Lissi Wallet
• Issuer / verifier app access:
  • Currently unavailable

esatus

• Mobile app access:
  • iOS
  • Android
• Issuer / verifier app access
  • Currently unavailable

idRamp

• Mobile app access:
  • iOS
  • Android
• Issuer / verifier app access
  • API demo for testing

iGrant.io (TDA team)

• Mobile app access
• Developer Documentation (release end of January, only documentation)
• Registration (not open yet)
  
• Issuer / verifier app access:
• Developer Tutorial
• Registration performed with SovrinStaging
• Reporting issues
• Contact ssi@igrant.io or Jan Lindquiston Slack channel
  
• Alternatively register comments through Trello board