Oracle FAQ

A blockchain oracle is infrastructure that brings off-chain data (like asset prices) on-chain so smart contracts can use it. Blockchains can’t fetch external data on their own, so oracles are the bridge between the real world and DeFi.

A push oracle writes data on-chain on a schedule (every heartbeat or when the price moves past a threshold) — the protocol always finds a fresh value waiting, but someone pays gas to keep it updated. A pull oracle keeps data off-chain and only writes it when an app requests it in the same transaction — cheaper and lower-latency, but the integrating contract must fetch and verify the update itself.

Chainlink secures by far the most value — roughly $33B in total value secured (≈59% of the tracked market as of June 2026), ahead of Chronicle (~$7.5B), RedStone (~$3.6B) and Pyth (~$3.1B). Figures move; treat them as a market-position snapshot, not a live number.

For blue-chip collateral, Chainlink is the safe default. For liquid-staking/restaking (LST/LRT) collateral, RedStone usually ships support fastest. Chronicle wins on gas cost and verifiability, and Pyth wins on latency for perps. The right answer depends on which assets you list and how latency-sensitive you are.

Chronicle is the gas-cost leader — its Scribe design uses Schnorr signature aggregation, reportedly making Ethereum updates ~63% cheaper than a comparable Chainlink feed. Pull oracles (Pyth, RedStone, Switchboard) also save gas because you only pay when you read.

UMA’s optimistic oracle is purpose-built for it: it can settle arbitrary, subjective claims (not just prices), which is why it powers Polymarket. Some markets now combine it with price oracles like Chainlink or Pyth to reduce settlement risk.

Some do, some don’t. Chainlink (LINK), Pyth (PYTH), RedStone (RED), API3, UMA and DIA have tokens. Chronicle, Chaos Labs, eOracle and Switchboard currently have no public oracle token. A token isn’t a quality signal on its own — it reflects the security/incentive design.