🔮 VERO · The Oracle

VERO

Verification Engine for Resolution Outcomes — the protocol’s oracle system.

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 two-step pipeline: (1) search for relevant evidence, then (2) evaluate the statement based only on that evidence. This approach reduces payload size, resists prompt injection, and improves reliability under oracle execution limits.

Search Step

Exa (Search)

Evaluation Step

xAI (Inference)

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.