RedStone Oracles — RedStone Basics

What RedStone is

RedStone separates data collection from data delivery so the same feeds can serve many chains without redeploying a whole network of nodes each time. It already powers 100+ dApps across 70+ networks.

Three integration modes (you pick)

• Pull (Core): injects signed data directly into the user's transaction, so you read fresh prices in the same tx—very gas-efficient.

• Push: stores data on-chain at a cadence or on deviation; dApps set their own update rules (e.g., heartbeat every X seconds or when price moves Y%).

• Hybrid (ERC-7412): the best of both—contracts read from an on-chain feed, and when data is stale the client auto-updates and then executes the user's call.

Why it's different

The pull model is "storage-less": data rides in calldata only when needed, avoiding expensive storage writes—great for gas and latency.

💡 Visual idea: Side-by-side of Pull vs Push vs Hybrid with one-line when-to-use.