What is TOC?

TOC (Truth On Chain) is modular infrastructure for financially-backed, verifiable prediction resolution. It introduces the Prediction Option Protocol (POP) - a standardized unit of truth that can be created, resolved, disputed, and consumed by any protocol.

The Problem

DeFi protocols need verified external data, but current solutions have significant gaps:

Oracles lack accountability

Traditional oracles like Chainlink and Pyth provide data feeds, but when things go wrong, there's no clear accountability. Who compensates users when an oracle reports incorrect data? The answer is usually "no one."

Prediction markets are limited

Existing prediction markets handle binary outcomes well, but struggle with numeric values, arbitrary data, and complex resolution logic. Building custom resolution systems requires significant engineering effort.

Custom solutions don't scale

Teams building DeFi applications often implement their own truth verification systems. This duplicates effort across the ecosystem and creates fragmented, inconsistent approaches to the same fundamental problem.

Key insight: The missing piece isn't better oracles - it's a standardized way to know who is accountable for the data you're using, and how much financial backing stands behind that accountability.

The Solution

TOC separates the concerns of lifecycle management (how predictions are created, disputed, and finalized) from resolution logic (how answers are determined). This enables:

Architecture Overview
CONSUMERS
Prediction Markets Insurance Derivatives DAOs
POPRegistry
Lifecycle Bonds Disputes Results
RESOLVERS
Pyth Oracle Optimistic Custom

Pluggable Resolvers

Any smart contract can become a resolver by implementing a simple interface. Use Pyth for price data, build an optimistic resolver for subjective outcomes, or create custom logic for your specific needs. The registry doesn't care how truth is determined - only that it follows the standard lifecycle.

Explicit Accountability Tiers

Every answer comes with a clear accountability tier, computed at creation time and immutable thereafter:

SYSTEM

Protocol-backed resolvers with whitelisted TruthKeepers. Maximum trust, suitable for high-value settlements.

TK_GUARANTEED

TruthKeeper stakes their reputation backing a resolver. Balanced risk and reward for prediction markets.

PERMISSIONLESS

Any resolver, any TruthKeeper. Maximum flexibility for experimental use cases.

Two-Round Dispute System

Incorrect resolutions can always be challenged. Round 1 goes to a TruthKeeper (domain expert). If needed, Round 2 escalates to admin arbitration. Bond economics ensure disputes are serious while incentivizing accuracy.

TOC vs. Alternatives

See how TOC compares to existing solutions:

Feature Oracles
(Chainlink, Pyth)		 Prediction Markets
(UMA, Polymarket)		 TOC
Answer Types Price feeds only Mostly binary ✓ Boolean, Numeric, Any bytes
Dispute Mechanism ✗ None Single round ✓ Two-round escalation
Accountability Tiers ✗ Hidden/implicit ✗ Single tier ✓ 3 explicit tiers
Pluggable Data Sources ✗ Fixed providers ✗ Limited ✓ Any resolver
Configurable Timing ✗ Fixed Limited ✓ Per-POP windows
Permissionless ✗ Closed Partial ✓ Anyone can build resolvers

What TOC Is — And Isn't

TOC IS
  • Infrastructure for verified truth that any protocol can integrate
  • A standard for how predictions are created, resolved, and disputed
  • Modular - use existing resolvers or build your own
  • Accountability-first - every answer has a known trust level
TOC IS NOT
  • An oracle - it uses oracles as one resolver type
  • A prediction market - it powers prediction markets
  • A governance tool - though DAOs can use it for inputs
  • A data feed - it's a resolution and accountability layer

Who Uses TOC?

TOC is infrastructure for protocols that need verified external data:

Ready to integrate? Check out the Quick Start guide for code examples, or dive into How It Works to understand the full POP lifecycle.