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. Trust Models

Computation Integrity Trust Model

Imagine you're playing a high-stakes poker game, and you want to make sure that the deck isn't stacked against you. In the world of zkPass, the role of an impartial dealer is played by something called a Zero Knowledge Virtual Machine, or ZKVM for short. This special "dealer" ensures that the game—here, the process of creating a secure proof—is completely fair and above board.

The beauty of this ZKVM dealer is that it operates on what's known as the Trustless Model. This means you don't have to take anyone's word that the game is fair; you can see it for yourself. The dealer's actions are so transparent that you, as the Verifier in this poker analogy, can confidently confirm that the proof you're given is valid. You don't have to trust the zkPass service or any other third party; the integrity of the game stands up to scrutiny all on its own.

So, with zkPass and its ZKVM engine, you're not just hoping for a fair game; you're guaranteed one. And that assurance comes not from trust, but from verifiable, transparent actions.

PreviousData Integrity Trust ModelNextzkPass Module

Last updated 1 year ago

🤝