oracles.ink

Chronicle vs Pyth Network

Chronicle (Gas-efficient, fully verifiable oracle born inside MakerDAO ) versus Pyth Network (Low-latency pull oracle sourced straight from 120+ first-party trading firms and exchanges) — how they differ on type, coverage and what they’re built for.

ChroniclePyth Network
TypePushPull
Update modelScribe: Schnorr signature aggregation decouples validator count from verification cost, so updates stay cheap as the validator set grows.Publishers stream prices to Pythnet → relayed via Wormhole → pulled on-demand by the consuming chain. Updates ≈ every 400 ms.
ChainsEthereum + L2s90+
Feeds160+1,300+
SecurityTransparent validator set with cryptographic (Schnorr) aggregation; every update is independently verifiable.Aggregates 120+ first-party publishers (exchanges, market makers) on Pythnet with confidence intervals.
TVS*~$7.5B~$3.1B
TokenPYTH
Best atLowest gas cost in the market (≈63% cheaper than Chainlink on Ethereum), with a strong RWA / institutional focusHFT-grade latency and real-world assets (equities/FX/commodities); pull means you only pay gas when you read

* Approximate total value secured — dated market snapshot (DefiLlama / provider reports, 2026).

Chronicle

  • Cheapest on-chain updates (Schnorr aggregation)
  • Fully transparent and verifiable
  • Institutional pedigree (Maker/Sky)
  • Smaller feed catalogue than Chainlink/Pyth
  • Push-only (no on-demand pull yet)

Pyth Network

  • Lowest latency (≈400 ms)
  • First-party data from real trading firms
  • Huge non-crypto coverage (equities, FX)
  • Pull integration adds contract complexity
  • Relies on Wormhole cross-chain messaging

Bottom line

Pick Chronicle when lowest gas cost in the market (≈63% cheaper than chainlink on ethereum), with a strong rwa / institutional focus matters most; pick Pyth Network when hft-grade latency and real-world assets (equities/fx/commodities); pull means you only pay gas when you read matters more.