zPass docs
  • zPass
    • Introduction
    • Quickstart
    • Background
    • Benefits & Use Cases
    • Technical Foundations
    • System Participants
    • Powered by Aleo
  • Fundamentals
    • Issuer
    • Holder
    • Verifier
    • Off-chain flow
    • On-chain flow
    • Local Execution with WASM
  • ZPass Programs
    • Background
    • Verify offchain program
    • zPass issuance program
    • zPass hiding program
    • zPass invalidate program
    • zPass invalidate hiding program
    • zPass merkle tree size 8 program
  • ZPass SDK
    • Methods References
      • constructor
      • setNewHost
      • issueZPass
      • getZPassRecord
      • proveOnChain
      • proveOffChain
      • verifyOnChain
      • verifyOffChain
      • signCredential
      • initThreadPool
      • createAleoWorker
      • getMerkleRoot
      • getMerkleTree
      • getMerkleProof
      • getLeavesHashes
      • signMerkleRoot
  • Example Usage
    • Step-by-step Guide
Powered by GitBook
On this page
  • Core mechanics
  • Aleo and zero-knowledge proofs
  • Aleo's role in privacy
  • Aleo's record model
  • Decentralized private computation
  1. zPass

Technical Foundations

Core mechanics

The backbone of zPass relies on zero-knowledge proofs and, more specifically, zk-SNARKS. The shift to general-purpose zero-knowledge proofs ensures greater privacy and programmability than traditional identity verification systems. Aleo's infrastructure is secure and scalable, providing a strong foundation for zPass.

Aleo and zero-knowledge proofs

zPass is powered by Aleo, a developer platform extending the capabilities of traditional blockchains using the concept of ZEXE.

Aleo's role in privacy

Aleo's infrastructure ensures three critical forms of privacy in zPass: private inputs, private outputs, and user privacy.

Aleo's record model

  • Enables storage and encryption of user data while keeping it private in the user's hands

  • Extends from Zcash's UTXO model, allowing for complex privacy-preserving applications

  • Supports private inputs and outputs

Decentralized private computation

  • Control shifts from centralized databases to end users

  • Combines zero-knowledge proofs with off-chain execution for verifications that do not compromise data privacy

  • User identity stays private

PreviousBenefits & Use CasesNextSystem Participants

Last updated 4 months ago

Page cover image