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

Architecture

PreviousIntroducing BluwhaleNextOverview

Last updated 10 months ago

The Bluwhale Protocol fits seamlessly between the application layer as well as protocols plus L1/L2 chains passing on crucial aggregated user insights to dApps and individuals without them needing to manually do the analysis or write the technical queries.

The personalization layer can further be broken down into core 3 modules

  1. Data Verification Module

This layer consists of verifiers from the community as well as social interactions and circles, tasked with validating the attestation to confirm the layers secure and accurate operations including the data contributed and identities established in Bluwhale’s AI network.

  1. Identity Emedding Module

This layer authenticates users via both traditional (web2) like social accounts and blockchain (web3) like social reference mechanisms, aggregated under the embedding. It integrates identities and data through knowledge links, weigths, rankings and other identity contextualization models.

  1. Privacy Inference Module

Established on a Zero-Knowledge foundation, it interprets and shadows data consumers reveal and release allocating rewards according to the demand from enterprises or individuals as well as amount of processing and queries required to extract the full understanding and insights around the wallet/user.

Each of the modules are critical for the entire personalization layer to become trustless, decentralized and secure. The Data Verification Module ensures that contributed internal, external, on-chain/off-chain data seamlessly integrates with each other by leveraging a reference verification approach through nodes. The Identity Embedding Module contextualizes user behavior and continuously optimizes incoming references and data which make the profile as wholistic as possible. Then it passes the embeddings with its descriptive surrounding data to a zk-layer that only allows enterprises to access if the individual wallet holder gives permission to its data in exchange for financial rewards.

Data Verification Module

In order to decentralize our AI network we developed a mechanism to involve our community in the verification process through verifier nodes that are operated by individuals or delegators. Anyone can run the nodes to ensure data is secured and processed so our AI structure is optimized in a safe and scalable environment. However, only license holders of the main node sale will have authority to reach consensus and penalize misbehaving nodes. They are responsible for making sure that the contributed data has value to the overall network and should be available for distribution on-chain.

Identity Embedding Module