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

Service-based Proof System

PreviousWhat's AheadNextMain Features

Last updated 1 year ago

To address the , we introduce zkPass Service, a service-based proof system operating as a Proof-as-a-Service platform.

The defining characteristic of zkPass is the offloading of ZKP computations to a server operating within a Trusted Execution Environment (TEE). Users only need to initiate a service request through the zkpass-client SDK library, which then delegates the heavy computational tasks to the server side.

It should be noted that this server-centric approach has its downside. Most notably, the user's sensitive input data is no longer confined to their device but is instead processed in a centralized server. This shift necessitates a degree of trust to ensure the confidentiality of the user's input. To alleviate this concern, we run the zkPass server within a Trusted Execution Environment (TEE). This secure and isolated environment aims to provide an additional layer of protection, safeguarding the privacy of user's data while allowing for the efficient execution of ZKP computations. In other words, zkPass can still protect data confidentiality through the trusted privacy model.

๐ŸŒค๏ธ
limitations of the client-based proof system architecture