# Core Workflow Overview

The end-to-end process of ValidNet involves four seamless stages, leveraging AI Anchors, DePIN, and blockchain to deliver personalized, verifiable, and efficient AI outputs:

### 1. Query Initiation

Process:

* Users submit requests through ValidNet dApps, SDK, or directly to AI Anchors.
* AI Anchors parse the user’s intent and requirements, including output style, domain-specific rules, compute needs, and privacy preferences.

Technical Details:

* Anchors utilize natural language processing (NLP) to extract query parameters, converting them into a standardized JSON-based rule set.
* Users can specify task urgency, cost budgets, or preferred node locations, stored on-chain for transparency.

### 2. DePIN Resource Allocation

Process:

AI Anchors interact with the ValidNet decentralized compute marketplace to select optimal DePIN nodes for task execution, based on:

* Cost: Real-time bidding mechanism, inspired by Akash Network’s auction model, ensures cost-effective node selection.
* Capability: Hardware attestation via Trusted Execution Environment (TEE) verifies node specs.
* Reputation: On-chain performance history, including past validation accuracy and uptime, determines node reliability.

Technical Details:

* Smart contracts match Anchor requirements with node profiles, prioritizing nodes with high reputation scores and low latency.
* Nodes stake VAT tokens to participate, ensuring commitment and reducing malicious behavior.

### 3. Execution & Validation

Process:

Parallel Processing: The query is distributed to at least three DePIN nodes for redundancy, ensuring robust execution and fault tolerance.

Output Generation: Each node processes the query using multi-model AI, producing an inference output.

Cryptographic Validation: Nodes generate a hash-based commitment to prove correct processing, verified via multi-party computation (MPC) for integrity.

Proof-of-Validation (PoV) Consensus:

* Validators (a subset of DePIN nodes) compare outputs and commitments using a Byzantine Fault Tolerant (BFT) consensus mechanism.
* Matching outputs are finalized on-chain, marked as “verified.”
* Discrepancies trigger slashing of staked VAT tokens from malicious nodes, with tasks re-routed to new nodes.

Technical Details:

* MPC ensures that nodes cannot tamper with outputs without being detected, thereby achieving distributed trust.
* BFT consensus requires at least 2/3 node agreement, balancing speed and security.
* On-chain reputation scores are updated based on validation success, incentivizing honest behavior.

### 4. Output Delivery & Monetization

Process:

Verified results are returned to the user via dApps or SDK, accompanied by a trust score.

Micro-payments in VAT tokens are automatically distributed via smart contracts:

* DePIN node operators: 70% for compute and validation contributions.
* Anchor NFT owners: 15% royalty for creating and sharing high-quality Anchors.
* Protocol treasury: 15% to fund ecosystem growth.

Technical Details:

* Payments are settled on Layer-2 Network to minimize gas fees and ensure scalability.
* Users can monetize Anchors by listing them on the ValidNet marketplace, where community validation enhances their value.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://validnet.gitbook.io/docs/introduction/core-workflow-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.