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

Attestation

Attestation Verification Process:

  • When a tee submits an attestation, the service contract requests a random number from Chainlink VRF. Upon receiving the random number, it selects up to 200 nodes from the active online node list as verification nodes for the attestation.

  • Random Node Selection Rules:

    • Determine the number of verification nodes C based on the current number of online nodes.

    • If the number of online nodes is greater than 100, the verification nodes will be 10% of the online nodes.

    • If the number of online nodes is between 10 and 100, the verification nodes will be 10 nodes.

    • If the number of online nodes is fewer than 10, all online nodes will be verification nodes.

    • Using the random number R obtained from VRF, calculate the starting index:

    • 𝐼𝑛𝑑𝑒𝑥𝑏𝑒𝑔𝑖𝑛=𝑅𝑚𝑜𝑑𝐶

    • Index

    • begin

    • ​

    • =RmodC.

    • From the starting index, select the next C nodes in the active node list as verification nodes (wrapping around to the beginning of the list if necessary).

The selected verification nodes must submit their verifications within the specified time frame. If more than half of the selected nodes submit their verifications, and a majority validate the attestation as valid, the attestation is approved.

PreviousVerifier NodeNextDelegation

Last updated 10 months ago