> For the complete documentation index, see [llms.txt](https://bluwhale.gitbook.io/bluwhaleai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bluwhale.gitbook.io/bluwhaleai/ai-nodes/purpose-of-ai-nodes.md).

# Purpose of AI Nodes

#### Overview

Bluwhale is dedicated to creating applications, and a modular AI protocol called the Bluwhale Protocol. This protocol transforms end-to-end user data flow into a graph structure and user embeddings to combine identity aggregation (Bluwhale Profile), data contextualization (Bluwhale KG), storage (Bluwhale DB), processing, and AI model training and inference. The outputs of these parts are recorded on Oceanum (OXN), Bluwhale’s own TEE-native confidential EVM Layer 1, to ensure fair value distribution.

#### Importance of Verifier Nodes

Community-operated verifier nodes are essential to ensure the entire user data network's privacy, security, and decentralization. These nodes validate outcomes at each protocol layer, ensuring data integrity and compliance with established standards.

Verifier nodes primarily focus on verifying results from the data contribution and AI model training/inference modules. Computations and model training are performed within Trusted Execution Environment (TEE) clusters to protect user data privacy. The results are recorded on Oceanum (OXN), accompanied by TEE attestation. Division of labor within the Bluwhale stack: Confidentiality is enforced at the Oceanum (OXN) base layer — Oceanum (OXN) is Bluwhale’s own L1, and every smart contract executes inside the Intel SGX enclave of each Oceanum (OXN) validator, with contract state, calldata, return values, and event logs encrypted; remote attestation proves that the enclave is running unmodified, correct code. This is chain-level, hardware-enforced confidential execution. Bluwhale verifier nodes do NOT duplicate this enclave — they operate as a higher business-verification layer of the same Bluwhale system: they verify on-chain the attestations produced by Oceanum (OXN) (and its TEE clusters), confirming that the results of each Bluwhale protocol layer (data contribution, AI model training/inference) were indeed computed inside a legitimate enclave, thereby supporting fair value redistribution. In short, Oceanum (OXN) handles “confidential execution + hardware attestation,” while Bluwhale verifier nodes handle “business verification of those attestations.” The two are layers of one stack, not two overlapping TEE systems.

\
Third-party verification of TEE attestations is critical to avoid system manipulation and ensure fair data value distribution. This requirement drives our continuous effort to involve the community in operating these verifier nodes.

#### Protocol Security and Scalability

While a single honest node can detect fraudulent activity, ensuring effective enforcement against misbehaving TEE nodes and protecting user data requires that at least half (50%) of the nodes operate honestly; thus, Bluwhale's token incentives are structured around node operation performance, participation, and up-time. Establishing a decentralized network of community nodes is crucial for securing the protocol and ensuring scalability. 

The future roadmap of Verifier Nodes will assume additional responsibilities, including verifying Rebuild Bluwhale DB’s verification on Oceanum (OXN) (Bluwhale’s own L1 with its own validators and finality) and remove the EigenLayer dependency.This will ensure reliable content storage for each operator.

The scope of verifier nodes will broaden to include securing Bluwhale KG, an on-chain graph structure that contextualizes user data from web2 and web3 sources into the Bluwhale Protocol. This expansion will enrich the Bluwhale Profile, increasing the network's value for users and businesses.