RedStone Oracles — RedStone Basics
A 5-module primer on oracles and RedStone's modular design, modes, data flow, and security—5–10 minutes total.
Under the hood: how RedStone's data flows
Sources and signing
Prices are aggregated from many venues (CEXs, DEXs, aggregators—150+ sources) by independent nodes. Data is cleaned, signed, and broadcast via RedStone's open distribution layer.
Delivery and verification
During a user's transaction, RedStone attaches a compact data package to calldata. On-chain, contracts verify signatures and timestamps, then aggregate values (default: median) across unique signers before returning a result.
Data availability you can audit
Instead of bloating on-chain storage, RedStone persists packages off-chain with permanent availability (e.g., Arweave) so anyone can later verify what was served—cheap, durable, and auditable.
💡 Visual idea: Sequence diagram—Sources → Providers (sign) → Distribution → User tx (calldata) → Contract (verify + median).