Introducing Bluwhale
  • Introducing Bluwhale
  • Architecture
    • Overview
    • ERC-7231
    • Data Authentication
    • Bluwhale Link
    • Data Provider
    • Third-party Verification
    • On-chain Attestation
    • Trusted Execution Environment Cluster
    • About Trusted Execution Environments
    • Zero-Knowledge Proof
  • Verifier Nodes
    • Verifier Node Sale
    • Purpose of Verifier Nodes
    • Verifier Node Operations & App
    • Node Rewards & Projections
    • Node Licenses
    • Node Delegration
    • Node FAQs
  • Tokenomics
    • Utility
    • Distribution/Vesting
    • Staking
  • Bluwhale Community
    • Community Activations
    • Social & Community Links
    • Distributor & Referral Programs
    • Media Coverage
  • Resources
  • General FAQs
  • Brand Guidelines
  • Media Kit
  • Contact Us
  • Personalization Protocol
    • Overview
    • Architecture
      • Overview
      • Identity Layer
      • Data Storage Layer
      • Computation & Training Layer
      • Execution Layer
      • Verification Layer
  • How to Purchase Nodes
    • How to Purchase Nodes on Solana
  • Buyback Program
  • Why Verifier Nodes
  • How do Verifier Nodes Work
  • Bluwhale NFT License
  • Bluwhale Protocol Service
  • Trusted Execution Environment (TEE)
  • Verifier Node
  • Attestation
  • Delegation
  • SGX Attestation Verification
  • Verifier Node Sale Dynamics
  • Smart Contract Addresses
  • License Key (NFT)
  • Delegation
  • Node Rewards
  • Join Alphanet Verifier Nodes
  • Prerequisites
  • Delegation Tutorial
  • Operating a Verifier Node
  • Running in VPS
  • Running in CLI
  • Running in Desktop App
  • Explorer
Powered by GitBook
On this page
  1. Architecture

Zero-Knowledge Proof

PreviousAbout Trusted Execution EnvironmentsNextVerifier Nodes

Last updated 10 months ago

: ZK (Zero-Knowledge) Proof is the mechanism that validates and verifies the data in Bluwhale Protocol. Verifying a proof is a computational operation that is logarithmic in the worst case to the mathematical statement, and the proof process does not require interaction between the prover and the verifier, only the proof needs to be passed to the verifier (non-interactive).

Through zk-SNARK, Bluwhale Protocol can verify and prove users' on and off chain data, while ensuring minimal disclosure of user data, achieving privacy-preserving.

Note that Bluwhale accommodates both ZK (Zero-Knowledge) Proof and non-ZK proof data. Utilizing ZK Proof as input minimizes the risk of data exposure throughout the end-to-end data flow. Nevertheless, non-ZK proof data can still be verified and processed privately, by the integration with TEE.

The execution layer ensures that all data transactions are recorded and verifiable on the blockchain, enabling participants to share rewards in a decentralized manner.

This layer operates within a multi-chain framework, tasked with orchestrating value distribution across the protocol's components. It leverages smart contracts implemented on various consensus layers, including both Layer 1 and Layer 2 networks. It allows data providers across various networks to share, contribute, and receive rewards for the data they supply on their preferred network.

The Execution Layer's primary functions include recording TEE attestations and verifier reports on-chain, and, following verifier consensus, allocating on-chain rewards to data providers and infrastructure while levying charges on data consumers. This structure ensures a decentralized, secure, and efficient process for managing transactions and interactions within the Bluwhale ecosystem.

zk-SNARK