Whitepaper · v0.9Draft · May 2026

Passiv: A protocol for monetizing onchain behavioral signal

Passiv turns the public history of a Base wallet into a continuously updated, anonymized behavioral profile that AI agents can query and pay for via x402 micropayments in USDC. Wallet owners keep 80% of every query.

1. Abstract

AI agents are emerging as a primary class of consumers for behavioral signal: trader patterns, DeFi habits, liquidity preferences, dip reaction times, and sector rotation. Today this signal is locked inside proprietary indexers and sold by analytics vendors — the wallets that generated the data earn nothing. Passiv inverts this: the wallet that produced the behavior receives 80% of every query, settled instantly in USDC on Base via the x402 standard.

2. Architecture

Four off-chain layers, one on-chain settlement leg. The indexer reads public Base history. The fingerprint layer computes ~40 behavioral dimensions. The privacy layer strips identifiers (ZK attestations are planned — see the roadmap). The x402 oracle accepts agent requests and routes USDC back to wallet owners.

Status. The x402 oracle, the buyer SDK, k-anonymity enforcement, and on-chain settlement are built and running in preview. The indexer and fingerprint layers are in development — today the network serves a synthetic preview dataset, not real wallet data — with mainnet beta on the roadmap below.

Base RPC
  │
  ▼
[ Indexer ] ── reads public tx history
  │
  ▼
[ Fingerprint ] ── trader_type, risk, rhythm, reactivity (~40 dims)
  │
  ▼
[ Privacy ] ── strip addr / hash · random ID · ZK proofs (planned)
  │
  ▼
[ x402 Oracle ] ── agent query → match → settle USDC (Base)
  │
  ▼
80% owner  ·  20% protocol

3. Privacy model

  • Wallet addresses are never returned. Profiles are listed under random identifiers, never the wallet address (scheduled rotation is planned).
  • No transaction hashes are exposed. Buyers receive computed pattern vectors, not raw history.
  • k-anonymity (k ≥ 50). Every cohort served has at least 50 members; sub-floor cohorts are suppressed. Enforced server-side today.
  • ZK threshold proofs (planned). Agents will verify "volume > X" or "swing trader = true" without learning which wallet matched (roadmap, Q1 2027).
  • Owner-side controls. Categories can be toggled and protocols excluded; full profile deletion is on the roadmap.

4. Economics

Every agent query carries an x402 micropayment denominated in USDC. The protocol splits revenue 80/20 in favor of wallet owners and settles in ~200ms on Base. There is no token, no inflation, and no claim flow.

Standard query$0.02 USDC
Filtered cohort query$0.03 USDC
Premium fingerprint query$0.05 USDC
Wallet owner share80%
Protocol share20%
Settlementx402 · USDC · Base · ~200ms

5. Roadmap

  1. Q3 2026 — Mainnet beta. Indexer + console for early wallets.
  2. Q4 2026 — Agent SDK. Public x402 endpoints and TypeScript client.
  3. Q1 2027 — ZK proofs GA. Threshold attestations across all profile dimensions.
  4. Q2 2027 — Multichain index. Extend fingerprinting beyond Base.