VeriAgent

Claw-to-Claw (C2C) Verifiable Micro-Procurement Protocol
Built on X Layer Powered by OKX OnchainOS

Build X Season 2 Submission Entry (VeriVerse Major Update)

This repository is the official submission repository for Build X Season 2. In this submission scope, VeriVerse is positioned as a first-of-its-kind full lifecycle Agent launch-invest-challenge-graduate stack on X Layer.

VeriVerse is a major update of VeriTask (also referred to as VeriAgent in external materials), not a separate split project. Season 2 focuses on the integrated launchpad loop:

• Launch Agent on X Layer
• Invest USDT into escrow with strategy automation
• Run challenge and trust update
• Graduate via Semaphore authorization + atomic on-chain settlement
• Operate a three-role economic loop (Agent Provider / Backer / DAO Verifier)

Season 2 Main Path

• Main project folder: MAJORUPDATE2-VeriVerse
• Main technical README: MAJORUPDATE2-VeriVerse/README.md

Hackathon Required Fields (Quick Index)

• Project intro and architecture: MAJORUPDATE2-VeriVerse/README.md
• 4-dimension KPI snapshot for judge review: MAJORUPDATE2-VeriVerse/README.md
• Deployment addresses (X Layer): MAJORUPDATE2-VeriVerse/addresses.json
• OnchainOS/Uniswap usage and mechanism: MAJORUPDATE2-VeriVerse/README.md
• Economic loop (three roles, three earning paths): MAJORUPDATE2-VeriVerse/README.md
• Team members and ecosystem positioning: MAJORUPDATE2-VeriVerse/README.md

Season 2 Submission Docs Navigation

• Public docs manifest: MAJORUPDATE2-VeriVerse/docs/public/Public-Docs-Manifest.md
• Public design overview: MAJORUPDATE2-VeriVerse/docs/public/VeriVerse-Architecture-and-Product-Design.md
• P3 acceptance report (public copy): MAJORUPDATE2-VeriVerse/docs/public/P3-Challenge-Acceptance-Report.md
• P4 semaphore authorization design (public copy): MAJORUPDATE2-VeriVerse/docs/public/P4-Semaphore-Authorization-Design.md
• Product closure diagrams (public copy): MAJORUPDATE2-VeriVerse/docs/public/VeriVerse-Product-Closure-Diagrams.md
• Skills (public, lightly desensitized): MAJORUPDATE2-VeriVerse/skills

中文说明：本次 Build X Season 2 参赛主体为 MAJORUPDATE2-VeriVerse，属于 VeriTask/VeriAgent 的重大版本升级，二者是一体化演进关系。

VeriTask (Build X Season 1)

Live Demo • Architecture • On-chain Proof • Quick Start • Reproducibility • Design Doc • PCEG Design • Dispute Anchor Demo

What is VeriTask?

VeriTask lets AI agents outsource data tasks to TEE-isolated workers and pay them with gasless USDT on X Layer — every byte verified by zkTLS + Intel TDX, every payment settled by OKX x402.

A Client Agent delegates a data task to a Worker Agent running on Phala Cloud CVM (Intel TDX TEE). The Worker fetches data from public APIs, wraps it in a dual-layer cryptographic proof (zkTLS + Intel TDX), and returns a ProofBundle. The Client verifies the proof and pays the Worker via OKX x402 — gasless, on-chain, zero human intervention.

This is Claw-to-Claw (C2C): two AI agents completing a verifiable micro-transaction, end-to-end.

Since v3.5.8, VeriTask includes a Proof-Conditioned Endorsement Graph (PCEG) — an on-chain reputation layer that anchors endorsement and dispute edges to X Layer via VTRegistry, enabling trust-weighted Worker selection through VeriRank (weighted PageRank).

Why VeriTask?

VeriTask is the first protocol that cryptographically binds data provenance + execution integrity + on-chain payment into a single autonomous agent flow.

Architecture

VeriTask Protocol — a trustless data procurement pipeline where every layer is cryptographically verifiable.

flowchart LR
    subgraph Client["🤖 Client Agent (OpenClaw)"]
        TD["task-delegator<br/><i>Orchestrator</i>"]
        V["verifier<br/><i>zk + TEE check</i>"]
        P["okx-x402-payer<br/><i>Gasless USDT</i>"]
        GA["graph-anchor<br/><i>Reputation Anchor</i>"]
        BA["bidding-agent<br/><i>VeriRank Selection</i>"]
    end

    subgraph OnchainOS["⚡ OKX OnchainOS (5 Skills)"]
        WP["wallet-portfolio"]
        DS["dex-swap"]
        DM["dex-market"]
        DT["dex-token"]
        OG["onchain-gateway"]
    end

    subgraph Worker["🔒 Worker Agent (Phala CVM · Intel TDX)"]
        DF["defi-scraper<br/><i>DefiLlama API</i>"]
        PG["proof-generator<br/><i>zkTLS + TDX</i>"]
    end

    subgraph Chain["⛓️ X Layer Mainnet"]
        X402["OKX x402 Settlement<br/><i>EIP-712 + EIP-3009</i>"]
        VTR["VTRegistry<br/><i>PCEG On-chain</i>"]
    end

    TD -- "1️⃣ TaskIntent" --> DF
    DF --> PG
    PG -- "2️⃣ ProofBundle<br/>(zkTLS + TDX Quote)" --> V
    V -- "3️⃣ ✅ Verified" --> P
    P -- "4️⃣ Gasless USDT" --> X402

    TD <--> WP
    TD <--> DS
    TD <--> DM
    TD <--> DT
    TD <--> OG

    V -- "3.5️⃣ Endorse/Dispute" --> GA
    GA -- "Anchor Edge" --> VTR
    BA -- "Read Rankings" --> VTR

Protocol Flow:

1. TaskIntent → Client delegates a data task to the Worker (e.g., "fetch Aave TVL")
2. ProofBundle ← Worker returns data + dual-layer cryptographic proof (Reclaim zkTLS + Intel TDX)
3. Verification → Client validates zkTLS signature + TDX quote + optional OnchainOS cross-verification
4. Settlement → Client pays Worker via OKX x402 — gasless, on-chain, zero human intervention

LLM-Powered Smart Routing

VeriTask uses a Dual-Model LLM architecture for intelligent verification:

The Pro model dynamically generates a cross-verification plan for each protocol — no hardcoded rules. This means VeriTask can verify any DeFi protocol's TVL by reasoning about its on-chain token structure.

OKX OnchainOS Integration

VeriTask Skills

OKX OnchainOS Skills (5/5)

x402 Payment Flow

1. Client signs EIP-712 TransferWithAuthorization (EIP-3009)
2. OKX verifies the signature: POST /api/v6/x402/verify
3. OKX settles on-chain: POST /api/v6/x402/settle
4. OKX pays gas as facilitator — Client holds only stablecoins (USDT/USDC)

Live Demo

Real conversations between a human user and VeriTask via OpenClaw Gateway. Two demos showing protocol evolution: Spark (cross-verify) and Aave (PCEG reputation anchor UPDATE). For the Dispute Anchor demo (failed proof → payment aborted → negative reputation edge), see DEMO.md.

On-chain Proof

All transactions are verifiable on OKX X Layer mainnet (chainIndex=196). Gas = 0 (OKX facilitator pays).

Transaction #2 was the first with real Reclaim zkTLS proof. Transaction #3 added OnchainOS cross-verification (sUSDC/spWETH market cap vs TVL). Transaction #4 is the first with PCEG reputation anchor — the Graph Anchor writes a verified edge to VTRegistry on X Layer after payment. Transaction #5 is the first Dispute Anchor — proof verification failed, payment was aborted, and a negative reputation edge was written on-chain to penalize the Worker (−76% final score).

Acceptance Records

Public PCEG REST API

The reputation graph is publicly queryable — no API key required. Runs inside the Worker's Phala CVM.

Base URL: https://2d29518d31fd53641b70a1754c79dce1450188b2-8001.dstack-pha-prod9.phala.network

Every edge includes a data_source field (live or preseed_demo) and an edge_type field (endorsement or dispute) for full transparency. See DEMO.md for sample API responses and the full Dispute Anchor acceptance test.

Raw Evidence

{
  "task_id": "test-v317",
  "data": {
    "protocol": "aave",
    "tvl_usd": 26854107510.0,
    "fetched_at": "2026-03-09T07:18:25.923113+00:00",
    "source_url": "https://api.llama.fi/tvl/aave"
  },
  "zk_proof": {
    "type": "reclaim_zkfetch",
    "hash": "698d8cc39d145877eb952e529ef7ed21ed18145c7e59b54097c16c0b1782336a",
    "proof": {
      "claimData": {
        "provider": "http",
        "parameters": "{\"url\":\"https://api.llama.fi/tvl/aave\",\"method\":\"GET\",...}",
        "owner": "0x95c8c603977827846109784e44e73d79214b0fd6",
        "timestampS": 1773040716,
        "context": "{\"extractedParameters\":{\"data\":\"26959869967\"},...}"
      },
      "signatures": [
        "0x722f3c8ba19fb215e056320e10d6e679324a490210d56068d946d1c698f4a4bf..."
      ],
      "witnesses": [
        {
          "id": "0x244897572368eadf65bfbc5aec98d8e5443a9072",
          "url": "wss://attestor.reclaimprotocol.org:444/ws"
        }
      ]
    },
    "response_body": "26959869967",
    "note_on_values": "⚠️ response_body (zkTLS fetch) vs tvl_usd (regular fetch) differ by ~$105M because they are TWO separate API calls at different timestamps. TVL fluctuates in real-time. The zkTLS proof binds to response_body, not tvl_usd.",
    "note": "zkProof generated successfully"
  },
  "tee_attestation": {
    "type": "intel_tdx",
    "report_data": "698d8cc39d145877eb952e529ef7ed21ed18145c7e59b54097c16c0b1782336a",
    "quote": "<7515 bytes Intel TDX Quote with SGX PCK Certificate Chain>",
    "event_log": "[...26 TDX event log entries including app-id, compose-hash, instance-id...]",
    "note": "Real Intel TDX attestation from Phala Cloud CVM"
  },
  "worker_pubkey": "0x871c98e2b2f22b6a215493a96d9eb76ccc0015cb",
  "timestamp": "2026-03-09T07:18:38.560819+00:00"
}

Trust Chain

flowchart LR
    A["📡 Data Source<br/><i>DefiLlama API</i>"] -->|"Raw data"| B["🔐 zkTLS Proof<br/><i>Reclaim Protocol</i>"]
    B -->|"Signed by attestor"| C["🛡️ TEE Attestation<br/><i>Intel TDX · Phala CVM</i>"]
    C -->|"Quote embeds hash"| D["💰 Payment<br/><i>OKX x402 · X Layer</i>"]

    style A fill:#e8f5e9
    style B fill:#e3f2fd
    style C fill:#fff3e0
    style D fill:#fce4ec

Each layer cryptographically binds to the data hash. Tamper with any layer and the chain breaks.

Reproducibility

VeriTask is designed to be fully reproducible. Here's how to verify each component:

1. Worker CVM (Live)

The Worker runs on Phala Cloud CVM with Intel TDX attestation:

Health: https://2d29518d31fd53641b70a1754c79dce1450188b2-8001.dstack-pha-prod9.phala.network/health
Docker: skottbie/veritask-worker:v3.1.7

2. On-chain Transactions

All 3 payment transactions are publicly verifiable on OKX X Layer Explorer. Gas cost = 0 for every transaction (OKX facilitator pays).

Latest MCP Phase 1 acceptance transaction (all crypto layers real, zero mock):

• Date: 2026-03-21
• Flow: MCP request -> Worker delivery -> proof verification -> x402 settlement -> receipt retrieval
• Protocol: Aave TVL ($25,479,162,974)
• ZK Layer: reclaim_zkfetch — Reclaim Protocol zkTLS, attestor-signed
• TEE Layer: intel_tdx — Phala Cloud CVM real TDX Quote (7515 bytes)
• Amount: 0.01 USDT on X Layer mainnet
• txHash: 0x819c0c984abc8cfe804d7023331f44dff9d439d9507584fb0138eeb7bfdd138f
• Explorer: https://www.oklink.com/xlayer/tx/0x819c0c984abc8cfe804d7023331f44dff9d439d9507584fb0138eeb7bfdd138f

3. Reproduce Locally

# Start Worker
cd worker_node && uvicorn server:app --host 127.0.0.1 --port 8001

# Run full demo (Windows PowerShell)
.\run_demo.ps1

# Run without payment
.\run_demo.ps1 -SkipPayment

4. Test Scripts

python test_worker.py      # Test Worker endpoint
python test_verify.py      # Test proof verification
python test_api.py         # Test full API flow
python test_mcp_server.py  # Test MCP stdio export discovery
python test_x402_endpoints.py  # Test x402 payment endpoints

Quick Start

Prerequisites

• Python 3.12+
• Node.js 20+ (required by @reclaimprotocol/zk-fetch)
• OpenClaw (WSL): npm install -g openclaw@latest

Setup

# Clone and install
git clone https://github.com/veritask/veritask.git
cd veritask
python -m venv .venv && .venv/Scripts/activate  # Windows
pip install -r worker_node/requirements.txt
npm install

# Configure
cp .env.example .env
# Edit .env with your OKX API keys + wallet private keys

# Run demo
.\run_demo.ps1 -SkipPayment

Run MCP Export (stdio)

# Install client-side dependencies for the MCP adapter
pip install -r client_node/requirements.txt

# Start the MCP stdio server
python client_node/veritask_mcp_server.py

# Optional offline smoke test: verifies server initialize + tools/resources discovery
python test_mcp_server.py

Notes:

• python test_mcp_server.py does not require the Worker to be online.
• Real task execution through submit_defi_tvl_task still depends on WORKER_URL being reachable.

Live acceptance status (all crypto layers real, zero mock):

• MCP Phase 1 acceptance validated end-to-end on 2026-03-21 with all three cryptographic layers fully real.
• Crypto layers: reclaim_zkfetch (Reclaim zkTLS) + intel_tdx (Phala CVM TDX) + OKX x402 (mainnet USDT)
• Verified loop: vt_request_task -> vt_get_task_status -> vt_get_task_result -> vt_verify_result -> vt_settle_payment -> vt_get_settlement_receipt
• Real settlement receipt:
  • payer: 0x012E6Cfbbd1Fcf5751d08Ec2919d1C7873A4BB85
  • payee: 0x871c98e2b2f22b6a215493a96d9eb76ccc0015cb
  • txHash: 0x819c0c984abc8cfe804d7023331f44dff9d439d9507584fb0138eeb7bfdd138f
  • explorer: https://www.oklink.com/xlayer/tx/0x819c0c984abc8cfe804d7023331f44dff9d439d9507584fb0138eeb7bfdd138f
  • detailed design-side acceptance record: MCP_VERIFIABLE_TOOL_EXPORT_DESIGN.md section 16.3

Deploy to OpenClaw (WSL)

bash deploy_to_openclaw.sh
npx skills add okx/onchainos-skills
openclaw skills refresh
openclaw gateway --port 18789 --verbose

Project Structure

VeriTask/
├── AGENTS.md                  # OpenClaw multi-agent routing rules
├── CLAUDE.md                  # AI assistant project instructions
├── design.md                  # Detailed design document (v3.5.0)
├── run_demo.ps1               # Windows PowerShell demo
├── deploy_to_openclaw.sh      # WSL deployment script
├── .env.example               # Environment variable template
├── schemas/                   # JSON schemas (TaskIntent, ProofBundle)
├── contracts/
│   └── VTRegistry.sol         # PCEG on-chain contract source
├── MAJOR UPDATE1-Proof-Conditioned Endorsement Graph/
│   ├── DEMO.md                # PCEG demo transcript (endorsement + dispute)
│   └── design_PCEG.md         # PCEG architecture design
├── client_node/
│   ├── openclaw.json          # Client Agent config
│   └── skills/
│       ├── task-delegator/    # C2C orchestrator (entry point)
│       │   ├── task_delegator.py
│       │   └── swap_and_broadcast.py  # Auto-swap + broadcast
│       ├── verifier/          # ProofBundle validator
│       ├── okx-x402-payer/    # OKX x402 payment
│       │   └── okx_x402_payer.py
│       ├── graph-anchor/      # PCEG reputation anchor (endorsement/dispute)
│       │   └── graph_anchor.py
│       └── bidding-agent/     # VeriRank Worker selection (PageRank)
│           ├── bidding_agent.py
│           └── edge_cache.json   # Pre-baked Edge event cache (26 edges)
├── worker_node/
│   ├── openclaw.json          # Worker Agent config
│   ├── server.py              # FastAPI (POST /execute, /health, /pceg/*)
│   ├── pceg_api.py            # PCEG REST API (/graph, /rankings, /worker)
│   ├── Dockerfile             # Docker for Phala Cloud CVM
│   ├── docker-compose.yml     # Local dev compose
│   └── skills/
│       ├── defi-scraper/      # DefiLlama TVL fetcher
│       └── proof-generator/   # zkTLS + TEE proof engine
│           └── zkfetch_bridge.js  # Node.js bridge for Reclaim zkFetch
└── .agents/skills/            # OKX OnchainOS Skills (5 skills)

Tech Stack

Hackathon Submission

• Hackathon: OKX OnchainOS "AI松" 2026
• Claw Type: OpenClaw (latest)
• LLM: Gemini 3 Flash/ Gemini 3.1 Pro
• OnchainOS Skills: All 5 OKX skills integrated into C2C pipeline
• Custom Skill: okx-x402-payer (gasless payment via OKX x402 REST API)
• TEE: Phala Cloud CVM (Intel TDX) — Live Worker
• Docker Image: skottbie/veritask-worker:v3.5.8
• Novel Contribution: First C2C protocol combining real zkTLS + real TEE + x402 gasless payments for an AI agent data marketplace
• Design Document: design.md — full technical specification (v3.5.0, 1090 lines)
• Author: @eazimonizone · Skottbie

License

MIT