| Table of Contents |
|---|
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.
...
The work on each TIP is done in a GitHub repository.
TIPs
Saturn-V
- GitHub Repo: 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
- Aries Protocol Test Suite (APTS)
- 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
- Out-of-band protocol
- New MIME Types
- Validation against both Aries Protocol Test Suite and Aries Agent Test Harness
- Aries Interop Profile 2.0
...