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

Trusted Execution Environment (TEE)

  • Tee permissions can only be added by the admin of the service contract.

  • Attestations can only be reported by those with tee permissions who have staked the required minimum amount of Bluwhale.

  • Staked Bluwhale by tees is converted into veBluwhale and stored in the Vault contract. Subsequent slashing and unstaking funds are in veBluwhale.

  • Malicious Attestation: If more than half of the verifiers deem an attestation malicious (i.e., Malicious > Valid), anyone can initiate a penalty against the tee for that attestation.

  • Penalty for Tees: When penalized, a portion of the staked veBluwhale is deducted and allocated to the respective verifier.

  • Excessive Penalties: If a tee is penalized multiple times and the staked funds are insufficient, the tee will be prohibited from reporting further attestations until additional staking is done.

Unstaking: Tees can cancel their stake after the lock-in period (7 days since the last attestation report). Upon unstaking, the remaining veBluwhale Tokens are returned, and the tee can no longer report attestations

PreviousBluwhale Protocol ServiceNextVerifier Node

Last updated 10 months ago