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. Core Components
  2. Service Architecture

zkPass Query Host

PreviousRESTful API Web ServiceNextzkPass Client Roles

Last updated 1 year ago

Now, the zkPass Query Host is where the real magic happens. Picture it as a vault, nested within another vault, sitting in a Trusted Execution Environment (TEE). This is the Fort Knox of zkPass, shielded and isolated from the outside world. Communication with the outside, even with the REST API Web Service, happens only through a secure, specialized channel.

Inside this vault is a specialized engine, a component known by the intriguing name of <zkvm>-zkpass-query, where <zkvm> denotes the specific ZKVM (Zero Knowledge Virtual Machine) engine in use. Given the and inputs, this engine crafts something quite valuable—a secure proof, the zkPass Proof.

So, when you make that initial RESTful call to generate_zkpass_proof, what you get back is this zkPass Proof, fresh from the secure confines of the zkPass Query Host's vault. And there you have it, the tale of how zkPass takes your user data and DVR on a journey from a humble reception desk to a high-security vault, only to return to you a valuable proof. Armed with this understanding, you're now ready to make the most of zkPass in your own engineering endeavors.

🏛️
user data
DVR