Explanations > Architecture

Architecture

Explain Quovra's system architecture and data path.

Architecture

Quovra has three layers:

  1. Frontend: Next.js app for markets, receipts, faucet, wallet actions, and docs.
  2. Settlement kernel: Anchor program on Solana that escrows, settles, and pays.
  3. Proof source: TxODDS TxLINE API and txoracle program.
mermaid
flowchart TB
  subgraph Browser
    UI[Next.js UI]
    Wallet[Solana wallet]
  end
  subgraph AppServer[Next.js server]
    Faucet[/api/faucet]
    Reads[market/account reads]
  end
  subgraph Solana[Solana devnet]
    Program[Quovra program]
    Vault[USDC vault PDA]
    TxOracle[TxODDS txoracle]
  end
  subgraph TxLINE[TxODDS TxLINE]
    API[Proof API]
    Roots[Daily score roots]
  end
  UI --> Reads
  UI --> Wallet
  Wallet --> Program
  Faucet --> Solana
  API --> Keeper[Keeper]
  Keeper --> Program
  Program --> TxOracle
  TxOracle --> Roots
  Program --> Vault

Design choices

ChoiceReason
Pull payoutsSettlement proof verification stays separate from token transfers
Stored market termsCallers cannot change fixture/stat/threshold during settlement
Txoracle CPIProof verification happens on-chain
Devnet test USDCSafe public demo without real-money wagering
Metadata fallbackRPC flakiness should not crash public pages

Related pages

Search keywords

architecture, Next.js, Anchor, TxLINE, txoracle, Solana

Last updated: [YYYY-MM-DD]