For the complete documentation index, see llms.txt. This page is also available as Markdown.

Oracles: real-time data feeds

What it is

Oracles bring real-world data, prices above all, onto the chain. If your product needs to know what an asset is worth right now, for lending, trading, synthetic assets, or liquidations, an oracle is the data layer that tells it. Any verified oracle integration qualifies if your case holds up.

What you could build

  • A lending protocol using live price feeds for collateral valuation and liquidation triggers

  • Synthetic assets tracking real-world prices; prediction markets integrations

  • An integration with DEX or trading product with accurate, manipulation-resistant pricing

  • Bringing real-world events on chain like weather in certain areas or events

  • Combining oracles with identity verification to enable smart contract validation

What the pilot expects

Leveraging an oracle means mainnet transactions where your contract actually consumes your declared feed. Only fees paid by wallets other than your own count toward your target (Standard §5.2), so your users, not your team, must be the ones transacting. Floors and target guidance for the Oracles category are in the Transaction Integrity Standard (§3.1, §3.3). Whichever provider you choose, name the feed and its on-chain consumption pattern in your proposal.

Get building

Readiness & constraints

Pyth runs in production on Cardano. The integration pattern: subscribe to the Pyth Pro websocket, include the signed price update in your transaction via a zero-withdrawal from the Pyth withdraw script. For any other oracle provider, readiness varies and the diligence is yours: verify current feed coverage and the on-chain consumption pattern against your use case before you commit your build plan.

Last updated