@@ -35,18 +35,19 @@ npm i
3535
3636## Setup
3737
38- In order to integrate with this test suite, you will need to use a
38+ To integrate with this test suite, you will need a
3939[ VC-API compatible] ( https://w3c-ccg.github.io/vc-api/ ) issuer and verifier that
40- is capable of issuing and verifying verifiable credentials and verifiable
40+ are capable of issuing and verifying verifiable credentials and verifiable
4141presentations. If your implementation is not VC-API compatible, it is possible
42- to "wrap" the implementation in a minimal VC-API implementation. Example code
43- for which is available at https://github.com/Wind4Greg/Server-for-VCs
44- Additionally your verifier will need to be able to verify Verifiable Credentials
45- and Verifiable Presentations signed with ` eddsa-rdfc-2022 ` . We also recommend
42+ to "wrap" the implementation in a minimal VC-API implementation, example code
43+ for which is available at < https://github.com/Wind4Greg/Server-for-VCs > .
44+ Additionally, your verifier will need to be able to verify Verifiable Credentials
45+ and Verifiable Presentations signed with ` eddsa-rdfc-2022 ` . We recommend
4646that any issuer endpoints submitted to this test suite also issue using
47- ` eddsa-rdfc-2022 ` . VerifiablePresentations will be submitted for verification
48- both signed and unsigned. Signed VPs from this suite will have a domain and challenge set.
49- The domain should be the test repo and the challenge is static.
47+ ` eddsa-rdfc-2022 ` . Both signed and unsigned Verifiable Presentations will
48+ be submitted for verification. Signed Verifiable Presentations from this suite
49+ will have a domain and challenge set. The domain should be the test repo, and
50+ the challenge is static.
5051
5152The issuer endpoint will need to conform to the
5253[ VC Issuer API] ( https://w3c-ccg.github.io/vc-api/#issue-credential ) .
0 commit comments