VERO · The Oracle

VERO

Verification Engine for Resolution Outcomes — a multi-source oracle system with AI routing + evaluation.

What Is VERO?

VERO is the oracle system that produces a single on-chain outcome for a statement: YES, NO, or VOID. The current implementation uses a three-step pipeline: (1) route the statement to the most appropriate data source, (2) fetch scoped data (Twelve Data, Exa, or Visual Crossing), then (3) evaluate the statement against that data. This structure reduces payload size, improves relevance, and keeps the oracle deterministic under Chainlink Functions limits.

Routing Step

AI selects the best data source per statement

Evaluation Step

xAI (Inference)

Market Data

Twelve Data (prices, markets)

Web Evidence

Exa (Search)

Weather Data

Visual Crossing (historical + forecast)

Resolution Outcomes

YES · NO · VOID

Execution Layer

Chainlink Functions (DON)

Failure Policy

Default-to-VOID on errors/timeouts

How Does The DAO “Choose” VERO?

Think of VERO as a role: the DAO can appoint a new “VERO” by updating the oracle configuration (endpoint/model/source) through on-chain governance with a built-in timelock.

Governance-controlled updates: VERO changes are staged on-chain and applied through on-chain governance.
Timelock mode: once VERO timelock is activated, oracle updates require 30-day notice (and can’t be turned off).
Transparency window: the timelock provides advance notice and accountability before oracle configuration changes take effect.
Operational necessity: secrets rotation (API keys) can happen without changing oracle behavior.

Why “VOID” Exists

If the oracle cannot verify a statement (ambiguity, missing data, provider failure, timeout), it can return VOID. This keeps resolution deterministic and minimizes incentives to exploit edge cases.