zkPass
zkPass User's Guide
zkPass User's Guide
  • Getting Started
    • 🔊Introduction
      • What is zkPass?
      • How does it work?
      • How zkPass can help you
      • What's Ahead
    • 🌤️Service-based Proof System
      • Main Features
      • zkPass Workflows
      • Deployment Options
        • Public-Cloud Hosting
        • Private-Cloud Hosting
        • On-Premise Hosting
    • 🗝️Key Concepts
      • User Data
      • DVR
      • zkPass Proof
  • Core Components
    • 🏛️Service Architecture
      • RESTful API Web Service
      • zkPass Query Host
    • 👥zkPass Client Roles
    • 🤝Trust Models
      • Data Privacy Trust Model
      • Data Integrity Trust Model
      • Computation Integrity Trust Model
    • 👩‍💻zkPass Module
  • Use Cases
    • 🩸Employee Onboarding
      • “Blood Test Result” User Data
      • "Employee Onboarding" DVR
      • zkPass Integration
      • Call Sequence
    • 🚘Loan Application Screening
      • “BCA Customer Profile” User Data
      • Loan Screening DVR
      • zkPass Integration
      • Call Sequence
    • 🛒Sharing OIDC Users Securely
      • "ShopSphere ID Token" User Data
      • "ShopSphere Account Holder" DVR
      • zkPass Integration
        • Integration Guidelines for ShopSphere OIDC Provider
        • Integration Guidelines for Krisna Service
        • Integration Guideline for ShopSphere App
      • Call Sequence
  • FAQ
    • How is verifiable computing implemented by ZKP?
  • Glossary
    • Client-based Proof System
    • DVR
    • User Data
    • zkPass Proof
Powered by GitBook
On this page
Export as PDF
  1. Getting Started

Key Concepts

PreviousOn-Premise HostingNextUser Data

Last updated 1 year ago

The concepts of User Data, Data Verification Request (DVR), and zkPass Proof are central to understanding how zkPass works. The diagram below illustrates the relationship among the three:

The user data and the DVR, which contains the query, are inputs to the zkPass Service, which are needed to create the zkPass proof object.

🗝️