VerdiktX Layer · Exchange OS

Demo mode — sample data

An AI oracle that renders verifiable verdicts for on-chain outcome markets.

Designated third-party oracle provider · X Layer Exchange OS

Verdikt turns a plain-language market question into a verifiable on-chain verdict — not a black-box yes/no.

A verified verdict sealed in a cube, fed by independent evidence sources

AI resolution engine

Outcome
WIN
Confidence
0%
Justification
View

Evidence sources

  • Official sites
  • News outlets
  • APIs
  • On-chain data
  • Community signals

On-chain flow

  • Propose Resolution
  • Dispute Window
  • Finalize
  • Settle & Payout
  • Evidence-backedMultiple independent sources
  • Confidence-scoredOutcome, score, justification
  • On-chain verifiableProposed, disputed, finalized

Why a third-party oracleExchange OS outcome markets “do not depend on continuous price feeds; event outcomes are resolved by designated third-party oracle providers” — and no provider is pre-integrated by the protocol.

Network
X Layer · 195
Categories
Sports · Crypto

How it works

  1. 01

    Question submitted

    A market question and its resolution criteria enter the engine.

  2. 02

    Evidence gathered

    Multiple independent sources are fetched and snapshotted.

  3. 03

    AI resolution pass

    Outcome, confidence score and justification — not a bare boolean.

  4. 04

    Proposed on-chain

    proposeResolution writes the verdict and opens a dispute window.

  5. 05

    Finalized & consumed

    finalize() settles the market and pays the winning pool.

Resolution console

engine v0.1.0 · mock fixtures · latency simulated

01 · Questionready

resolution criteria: binary YES / NOid 0x7f3a…d20c

Pipeline log—

$ awaiting submission…

02 · Verdictidle

no verdict yet
submit a question to run the resolution pass

Contract callVerdiktOracle · 0x7A3e…c19B

// step 04 — proposeResolution(bytes32,bool,uint16,bytes32)

questionId0x7f3a…d20c

outcome—

confidence—

evidenceHash—

// step 05 — finalize(bytes32) after disputeWindow

disputeWindow8s (demo) · 3600s (prod)

statusawaiting verdict

03 · Demo marketlocked

A minimal stake-and-settle market consuming the verdict — mirrors DemoOutcomeMarket.sol in miniature.

YES POOL

0OKB

NO POOL

0OKB

verdict required before proposing

Trust surface

  • Every verdict carries its evidence set and a confidence score, not a bare boolean.
  • Evidence is hashed and committed with the proposal, so the inputs are auditable after the fact.
  • A dispute window sits between proposal and finalization — the AI never writes a verdict unchallenged.

Live on X Layer testnet

real contracts · real reads · everything above this section is a client-side simulation — this is not

Live · VerdiktOracle0x0738…2B38

reading chain…

Proof trail6 / 6 steps on-chain
View DemoOutcomeMarket on the explorer ↗
Live · stake real testnet OKBwallet disconnected

A second, always-open DemoOutcomeMarket — separate from the finalized proof market above, so it never locks. Stakes 0.001 testnet OKB, real gas, real tx.

YES POOL

0.000OKB

NO POOL

0.000OKB

No wallet detected — get one →View this market on the explorer ↗

What the oracle guarantees

A verdict a market can settle on

  • Evidence before opinion

    Every resolution ships the sources it read. They are hashed and committed with the proposal, so the inputs stay auditable after the fact.

  • Confidence, not a bare boolean

    A basis-point score travels with the outcome. Below the threshold the verdict is held rather than proposed.

  • Dispute-windowed finality

    A proposal sits open for the window before finalize() writes it. The AI never lands a verdict unchallenged.

  • Runs without credentials

    Mock mode resolves against canned evidence, so the whole loop is testable with no funded wallet and no API key.

Architecture

  • oracle-engine/01

    Node.js + TypeScript

    Gathers evidence from independent sources, runs the DeepSeek resolution pass, submits the result on-chain.

  • contracts/02

    Solidity + Hardhat

    VerdiktOracle holds proposals through the dispute window; DemoOutcomeMarket consumes the finalized verdict.

  • web/03

    React + Vite

    Create a market question, watch it resolve, see the payout — the demo you are reading now.

Network
X Layer testnet · chainId 195
Chain client
viem
Resolution model
DeepSeek API
Categories
Sports · Crypto
Dispute window
3600s in production
Oracle interface
proposeResolution() · finalize()

FAQ

What happens when the AI gets it wrong?
The proposal is not the verdict. It sits in the dispute window, and a challenged proposal never finalizes. The committed evidence hash means the inputs it read can be checked, not guessed at.
What if the evidence disagrees?
Confidence falls below the threshold and the question comes back unresolved instead of resolved wrongly. A market would rather wait than settle on a coin flip.
Why not use a price feed?
Exchange OS outcome markets resolve events, not prices — the whitepaper puts resolution in the hands of designated third-party oracle providers, and pre-integrates none.
What is mocked in this build?
The evidence, the AI pass and the chain calls. The flow, the confidence scoring and the pro-rata payout math are the real design.

Resolve a question end to end

Submit, watch the pipeline, stake, finalize. Nothing to install.

Open the console →See the architecture