Haze Documentation

The behavioral data protocol on Robinhood Chain. Earn passive USDG from onchain data you're already creating.

Haze is a protocol that lets wallet owners monetize their anonymized onchain behavioral data by selling it to AI agents via x402 micropayments. Analytics firms like Nansen, Arkham, and Dune already scrape wallet data and sell it for hundreds of dollars a month. The wallet owner gets nothing. Haze reverses that flow.

You connect your Robinhood Chain wallet. Haze indexes your public transaction history, computes an anonymized behavioral fingerprint, and serves it to AI agents who pay per query. You keep 80% of every payment. No uploads, no configuration, no ongoing effort.

How it works

The Haze pipeline has five stages. The entire setup takes approximately 30 seconds. After that, the protocol operates autonomously with zero user input.

Blockchain data is already public. Haze does not access anything that isn't already visible to anyone running a block explorer. The value-add is the behavioral computation layer and the monetization infrastructure.

Quickstart

curl -X POST https://api.haze.com/v1/query \
  -H "Content-Type: application/json" \
  -d '{ "filters": { ... } }'

Behavioral fingerprint

The fingerprint is an anonymized behavioral profile computed from a wallet's full onchain history on Robinhood Chain. It contains no raw transactions, no wallet addresses, and no personally identifiable information. Only computed behavioral patterns.

Fingerprints are recomputed daily as new transactions come in. Profile accuracy and value increase over time as more behavioral data is accumulated.

Privacy model

Privacy is the foundation of Haze, not a feature. The protocol is designed so that data buyers never learn who the wallet owner is.

Guarantees

• No wallet addresses are ever exposed to buyers. Profiles use random identifiers only.
• No raw transactions — no hashes, no counterparty addresses, no specific stock positions, no exact amounts. Only computed behavioral patterns.
• User-controlled sharing — toggle individual data categories on or off at any time. Exclude stock data entirely if desired.
• Cohort responses — queries return batches of anonymized profiles by default (50-500 per query), not individual users.
• ZK verification — optional zero-knowledge proof layer lets buyers verify a profile represents a real wallet with real volume, without revealing which wallet.
• Instant deletion — delete your profile and all associated data at any time. One tap. Permanent and irreversible.

Data controls

Users have granular control over what behavioral data their profile includes. Each dimension can be toggled independently from the dashboard.

Disabling a data category removes that dimension from your fingerprint. Queries that require that dimension will no longer match your profile. This may reduce your earning rate but gives you full control over your data exposure.

Earnings & revenue

Revenue split

Every x402 payment from an AI agent is split 80/20:

• 80% goes to the wallet owners whose profiles were included in the query response
• 20% goes to $HAZE buyback and burns

Query pricing

Withdrawal

Earnings accumulate in your Haze balance denominated in USDG. Withdraw to your connected wallet at any time. Settlement is gasless — the protocol covers withdrawal gas fees.

Architecture

Layer 1: Indexer

Reads wallet transaction history from Robinhood Chain via RPC and indexer APIs. Processes both DeFi interactions (Uniswap swaps, Morpho deposits/borrows) and tokenized stock trades. Computes behavioral metrics including trading frequency, hold duration, cross-asset rotation patterns, risk behavior, volume, and equity sector preferences. Recomputes daily. All computation runs off-chain.

Layer 2: Privacy layer

Strips wallet addresses and all identifying information. Assigns random profile IDs. Runs an optional ZK proof circuit that proves a profile represents a real wallet exceeding volume and transaction count thresholds without revealing which wallet. User-controlled data sharing toggles are enforced at this layer.

Layer 3: x402 data oracle

HTTP API that receives queries from AI agents. Applies filters (trader type, volume range, protocol usage, risk profile). Returns matching anonymized profiles as JSON. Each query triggers an x402 micropayment settled via Meridian in USDG on Robinhood Chain. Handles revenue distribution: 80% to profile owners, 20% to protocol.

Layer 4: Earnings engine

Tracks which profiles were included in each query response. Accumulates micro-earnings per user in real time. Processes withdrawals gaslessly. Dashboard serves real-time earning ticker, historical totals, and query analytics.

┌─────────────┐     ┌──────────────┐     ┌────────────────┐
│  User wallet │────▶│   Indexer    │────▶│ Privacy layer  │
│  (RH Chain)  │     │  (off-chain) │     │ (anonymize +   │
└─────────────┘     └──────────────┘     │  ZK optional)  │
                                          └───────┬────────┘
                                                  │
                                          ┌───────▼────────┐
┌─────────────┐     ┌──────────────┐     │  x402 Oracle   │
│  AI Agent   │────▶│   Meridian   │────▶│  (query API)   │
│  (buyer)    │◀────│  (settlement)│◀────│                │
└─────────────┘     └──────────────┘     └───────┬────────┘
                                                  │
                                          ┌───────▼────────┐
                                          │ Earnings engine│
                                          │ (track + pay)  │
                                          └────────────────┘

x402 & Meridian settlement

Haze uses the x402 payment protocol for all agent-to-protocol micropayments. x402 embeds payment directly into HTTP requests — no accounts, no API keys, no subscriptions. Agents pay per query at the moment of request.

How x402 works in Haze

1. AI agent sends a query to api.haze.com/v1/query
2. Server returns HTTP 402 Payment Required with pricing in the response header
3. Agent constructs an x402 payment using USDG on Robinhood Chain
4. Agent re-sends the query with the X-402-Payment header
5. Haze verifies payment via Meridian facilitator (~200ms settlement)
6. Query results are returned. Revenue is split and credited to profile owners.

ZK proof layer

The optional zero-knowledge proof layer allows data buyers to verify profile authenticity without learning the wallet's identity.

What the proof verifies

• The profile represents a real wallet on Robinhood Chain (not fabricated)
• The wallet exceeds a minimum volume threshold (configurable per query)
• The wallet exceeds a minimum transaction count
• The wallet has been active for a minimum duration

What the proof does NOT reveal

• The wallet address
• The exact volume, balance, or transaction count
• Any specific transaction or position
• Any link between the profile ID and the real wallet

ZK proofs are generated off-chain using a Groth16 circuit and verified on-chain by any smart contract that needs to confirm profile authenticity. Proof generation is handled by the protocol — users do not need to run any software.

Token model

No token is required for Haze v1. The protocol generates real USDG revenue from day one. A governance token may be introduced post-launch.

Planned token mechanics (if launched)

• $HAZE — launching on Pons
• Buy-back-and-burn — 20% protocol revenue funds continuous token burns
• Deflationary — more protocol usage = more revenue = more burns = less supply

FAQ

Is my wallet address ever shared with data buyers?

No. Your wallet address is stripped during anonymization. Buyers receive only behavioral patterns attached to a random profile ID. There is no way for a buyer to determine which wallet generated a profile.

How much can I earn?

Earnings depend on profile completeness, activity level, and query demand. A fully active cross-asset profile earning from ~200 queries per day would generate approximately $1-2 per day. Earnings scale with the number of AI agents operating on and querying from the protocol.

Does Haze access my private keys?

No. The wallet signature during setup authorizes profile creation only. Haze reads publicly available blockchain data via standard RPC calls. It has no access to private keys, seed phrases, or off-chain data.

What chains does Haze support?

Haze launches on Robinhood Chain. Multi-chain expansion (indexing activity from Ethereum, Base, Arbitrum) is planned for future phases.

Do I need to hold any token to use Haze?

No. Haze v1 operates entirely in USDG. No native token is required to connect, earn, or withdraw.