TICKRDocs
RoadmapOpen app

Smart contracts

The onchain components and where to verify them.

Network

The current public build runs on Base Sepolia. Confirm the network and active addresses in the app before sending any transaction. The backend and frontend each carry deployment configuration, which can change between releases.

Core components

SeasonRegistry defines the fixture schedule and records settlement state. PriceOracle accepts price snapshots. ResultEngine derives scorelines and outcomes. PredictionPool holds TICK stakes, settles pools and handles claims. TeamRegistry and TickToken support team metadata and the staking token.

  • SeasonRegistry — fixtures and season state
  • PriceOracle — submitted prices
  • ResultEngine — match scoring
  • PredictionPool — stakes, fees, claims and refunds
  • TickToken — TICK balances

Essential Base Sepolia addresses

These addresses match the checked-in frontend and backend deployment examples. Only contracts needed to trace the token, prices, result calculation and fixture payouts are listed here. The active app configuration is the final reference before a transaction.

Verifying a result

Start at the fixture page and note the fixture ID and chain. Open the relevant verified contract on the chain explorer, inspect its recorded prices and settlement events, then compare the contract result with the app's final score.