RedStone Oracles — RedStone Basics
A 5-module primer on oracles and RedStone's modular design, modes, data flow, and security—5–10 minutes total.
What you can build (and which mode to choose)
Use cases that benefit
Money markets need conservative, robust feeds; perps care about latency; RWAs and new primitives (LST/LRT, BTCFi) need custom validation and asset-specific rules. RedStone's modular design supports "non-standard" feeds beyond plain spot prices.
Picking a mode (rules of thumb)
• Pull/Core: Trading, perps, vaults, and apps that want fresh reads inside the same transaction at minimum gas.
• Push: Markets that want a familiar on-chain feed and explicit update policies (heartbeat/deviation).
• Hybrid (ERC-7412): If a user hits stale data, the client first updates the feed, then executes—all in one flow. Great for UX on apps that want push semantics most of the time.
Developer note
Integration is minimal: extend a base consumer contract and wrap your ethers/viem call so the payload gets injected when you need it. You get the gas savings of storage-less reads without losing on-chain verification.
💡 Visual idea: Decision tree—latency vs. persistence → Pull / Push / Hybrid.