Retrieving the Data Verification Request (DVR) from the Proof Verifier
From Data Holder perspective, no integration with the Dvr module client SDK library is needed for this step.
The Data Holder first gets the DVR by calling the REST API provided by the Proof Verifier.
The zkPass call sequence diagram, specifically steps 1–3, corresponds to the DVR retrieval process.
Retrieving the User Data from the Data Issuer
From Data Holder perspective, no integration with the Dvr module client SDK library is needed for this step.
The zkPass call sequence diagram, specifically steps 4–6, corresponds to the User Data retrieval process.
The User Data retrieves the user data that is needed by the DVR by calling the provided by the Data Issuer.
Sending the ZkpassProof object to the Proof Verifier for verification
From Data Holder perspective, no integration with the Dvr module client SDK library is needed for this step.
Once the Data Holder receives the Zkpass Proof from the zkPass Service, it will pass it along to the Proof Verifier for verification. The Proof Verifier provides a REST API for this purpose.
The zkPass call sequence diagram, specifically steps 10–12, corresponds to the proof verification process.
Calling zkPass Service's generate_zkpass_proof REST API to create the ZkPass Proof
To generate the ZkPass Proof, the Data Holder needs to use the zkpass-client SDK library. The following section illustrates how the coding is done.
The zkPass call sequence diagram, specifically steps 7–9, corresponds to the proof generation process.
The Data Holder generates the proof by using the Dvr module client SDK library, as shown here.