Hey you!
Welcome back to “that’s what she said”, the newsletter which breaks down web3 fundamentals without melting your brain or making you Google “what the hell is a blockchain". Last time, we explored smart contracts — those tireless digital referees that execute agreements without lawyers or middlemen (if you missed that piece, pause here and catch up before we dive into today's topic).
Today, we're tackling a critical yet often overlooked component of the blockchain ecosystem — oracles. Blockchains are incredibly secure precisely because they're isolated from the outside world, but this isolation creates a problem. How can a smart contract betting on football match outcomes know who won? How can a DeFi protocol know Bitcoin's current price? How can an insurance contract verify that a flight was delayed?
The answer is oracles: the information highways connecting blockchain's isolated networks to the messy, unpredictable real world. These are sophisticated systems that bridge the gap between on-chain code and off-chain reality.
Let's explore how blockchains learned to see beyond themselves. Ready?
🧠 Definition
Imagine you and your friend bet on a football match. You put $50 on Team A, they put $50 on Team B, and you both deposit the money into a smart contract. The deal is simple: when the match ends, the winner takes all. There's just one problem: your smart contract has no idea who won the game. It's like being locked in a soundproof room with no TV.
A blockchain oracle is a service that connects blockchains to external systems, enabling smart contracts to execute based on real-world inputs and outputs. Think of oracles as blockchain's eyes and ears: they're the part of the infrastructure layer that queries, verifies, and authenticates external data sources, then relays that information onto the blockchain in a format smart contracts can understand.
Here's what makes this tricky: oracles aren't the data sources themselves. They don't create the weather data, stock prices, or sports scores. Instead, they're the bridge that retrieves this information from the outside world, validates it, and delivers it to smart contracts in a trustworthy manner.
The name oracle is fitting. Just as ancient oracles were intermediaries between gods and mortals, blockchain oracles are intermediaries between the real world and the blockchain. The key difference is that modern oracles use cryptography and consensus mechanisms instead of prophecy and interpretation.
💪 Importance
Without oracles, blockchain would be like a supercomputer locked in a room with no Internet connection — incredibly powerful, but fundamentally limited to processing only the information already inside.
Oracles solve what's known as the oracle problem — a fundamental limitation of smart contracts. Blockchains are purposely isolated from external systems to maintain their most valuable properties: strong consensus, prevention of double-spending, and resistance to network downtime. This deterministic architecture means every node must reach the same result given the same input, which is impossible if different nodes are accessing different external data sources.
This isolation would severely restrict blockchain's usefulness. Consider what wouldn't exist without oracles:
- DeFi needs oracles to survive. Lending protocols like Aave and Compound require constant price feeds to monitor collateral. Trading platforms like dYdX need accurate pricing for their pairs. Without trustworthy oracle data, billions in DeFi transactions couldn't happen safely.
- Prediction markets can't function without them. Platforms like Polymarket must verify real-world outcomes — sports results, election winners, and weather events.
- Insurance automation requires real-world verification. Parametric insurance pays out when measurable conditions are met — flight delays, crop failures, and natural disasters. Oracles verify these events, enabling instant payouts instead of lengthy traditional claims processes.
- Supply chains need the connection. Smart contracts can track digital tokens, but oracles connecting to IoT sensors and logistics systems verify that physical goods actually moved as claimed.
Here's the catch: because oracles determine what smart contracts "see," they become critical attack vectors. Manipulate the oracle, and you manipulate every contract depending on it. This makes oracle security one of blockchain's most pressing challenges.
🔍 How Oracles Work
Oracles operate through a multi-step process that balances speed, security, and decentralisation. Let's check it out.
- Request. Everything starts when a smart contract needs external information. The user or dApp (decentralised application) triggers a data request to an on-chain oracle contract. This request specifies what data is needed (for example, the ETH/USD price), which sources to use, and how to process multiple responses into a single value.
- Bridge. The on-chain oracle contract acts as the bridge between the blockchain and the outside world. It receives the data request and produces a log event, essentially posting a message that says "I need this information".
- Off-Chain Network. Off-chain oracle nodes monitor the blockchain for these log events. When they detect a data request, these nodes spring into action. Multiple independent oracle nodes simultaneously fetch the requested data from external sources. They might query APIs, scrape websites, access IoT sensors, or pull from traditional financial data providers. Importantly, this happens off-chain, so it's not limited by blockchain constraints like gas costs or block sizes.
- Consensus and Validation. The oracle nodes don't just grab data and immediately send it back. They must reach a consensus on what the correct answer is. Different oracle networks use different consensus mechanisms, but the goal is the same: to ensure the data is accurate even if some nodes are malicious or mistaken. For instance, if ten oracle nodes check the ETH price and nine say $2,000 while one says $200,000, the system recognises the outlier and excludes it.
- Delivery. Once consensus is reached, the oracle nodes reformat the data into a blockchain-compatible format and submit it back to the on-chain oracle contract through a transaction. The oracle contract then passes this verified data to the original smart contract that requested it.
- Execution. Finally, the smart contract receives the data it needs and can execute its programmed logic. The insurance contract can check if the flight was delayed. The lending protocol can verify collateral values. The prediction market can settle bets on match outcomes.
The beauty of this system is that it maintains decentralisation throughout. No single entity controls what data the smart contract receives. Instead, multiple independent nodes must agree, creating a trustworthy information flow from the real world to the blockchain.
⚡️ Types of Oracles
Oracles come in many flavours, each designed for specific use cases and trust models.
Based on the Data Source:
- Software oracles aggregate data available on the internet: price feeds from exchanges, weather data from meteorological services, or sports scores from official sources. These are the workhorses of the oracle world, powering most DeFi applications.
- Hardware oracles connect to physical sensors and devices. They might read RFID tags in supply chains, monitor IoT temperature sensors for cold storage verification, or process barcode scans for proof of delivery. These bridge the digital-physical divide, enabling blockchain applications in logistics, manufacturing, and real-world asset tracking.
- Human oracles involve people providing data based on real-world events or specialised knowledge. A dispute resolution process might require human judgment on whether contract terms were met. Certain prediction markets use human reporters to confirm event outcomes when automated verification isn't possible.
Based on Data Flow Direction:
- Pull-based/inbound oracles are the most common type. They fetch data from the real world and deliver it onto the blockchain for smart contract consumption. These are perfect for applications needing periodic updates, like DeFi protocols requiring price feeds every few minutes.
- Push-based/outbound oracles work in reverse: they allow smart contracts to send commands to external systems. When a rental payment is confirmed on-chain, a push oracle might trigger an IoT system to unlock a car door. When a cross-border transaction completes, it might instruct a banking network to release funds.
- Cross-chain oracles specialise in moving information between different blockchains. They can read data from one blockchain and write it to another, enabling interoperability. This allows you to use data from Ethereum to trigger actions on Solana, or bridge assets between chains so they can be used outside their native blockchain.
- Compute-enabled oracles provide decentralised computation services that are impractical to perform on-chain due to cost or technical limitations. This includes running complex calculations, generating verifiable randomness for gaming applications, or computing zero-knowledge proofs for privacy.
Based on the Update Pattern:
- Immediate-read oracles provide data instantly upon request, ideal for static or infrequently changing information (for example, country codes, KYC verification statuses, or one-time lookups).
- Publish-subscribe oracles maintain continuously updated data feeds that smart contracts can access anytime. These are perfect for dynamic data like token prices that change constantly. Instead of requesting a price every time, contracts can simply read from the always-current feed.
- Request-response oracles follow a traditional query model where contracts request specific data fragments only when needed. This is optimal when the full dataset is too large to store on-chain or when data is needed sporadically.
Based on the Trust Model:
- Centralised oracles operate under single-entity control. They're efficient and can provide specialised datasets, but they introduce a single point of failure. If that one oracle lies, gets hacked, or goes offline, every smart contract that depends on it fails.
- Decentralised oracles distribute control across multiple independent entities operating in a peer-to-peer network. They achieve consensus on data before submitting it on-chain, eliminating single points of failure. Multiple nodes must collude to feed bad data, making manipulation much harder. This comes with higher complexity and potentially slower response times, but the security benefits typically outweigh these costs.
The choice of oracle type fundamentally shapes what your smart contract can do and how securely it can do it. Most sophisticated dApps use multiple oracle types to balance speed, cost, security, and functionality.
⚠️ Limitations
Oracles are powerful but imperfect. Understanding their limitations is crucial for anyone building with or investing in blockchain applications.
- Trust paradox. Blockchains are trustless, but oracles require trust. You've built a decentralised system where no single party has control, then you add an oracle that becomes a potential point of failure. If the oracle provides false information, all that blockchain security becomes worthless. Even decentralised oracle networks don't fully solve this; they distribute trust across multiple parties, but you're still trusting that consensus mechanism and those node operators.
- Attack vectors and manipulation. Oracles create new attack surfaces. Hackers can manipulate data sources, compromise oracle nodes, or exploit communication channels between oracles and blockchains. Common manipulation techniques include flash loan attacks that distort prices, front-running oracle updates, spoofing with fake trade volumes, and cross-market manipulation where traders influence one exchange to affect oracle readings (we'll cover the topic of attacks in the upcoming articles).
- Data quality and latency. Not all data sources are reliable. Oracles pulling from a few sources or low-liquidity markets may not reflect the broader reality. Real-world data also takes time to verify and reach consensus on, and even seconds of delay can create exploitable arbitrage opportunities (a strategy that profits from small, temporary price differences for the same asset in different markets by simultaneously buying it at a lower price and selling it at a higher price) in fast-moving markets.
- Cost considerations. Oracle updates cost gas fees. Frequent updates across multiple assets get expensive quickly, creating tension between data freshness and economic feasibility.
- Real-world enforcement gap. Oracles bring information onto blockchains but can't enforce physical actions. A smart contract can verify that goods should be delivered, but can't force delivery. It can determine whether insurance should pay out, but if the provider's wallet is empty, code can't conjure funds.
- Immutability. Once an oracle feeds data to a smart contract and that contract executes, there's no appeals process. What if the oracle was wrong? What if the official sports score was later corrected? Traditional systems have mechanisms for handling errors and disputes. Smart contracts with oracle data do not, at least not without adding complex governance layers that reintroduce centralisation.
- Regulatory uncertainty. As oracles facilitate real-world economic activity on blockchains, they're increasingly subject to regulatory scrutiny. The legal framework is still evolving, creating uncertainty for oracle projects and the applications depending on them.
The limitations don't make oracles unusable; they make thoughtful oracle selection and implementation critical. The best projects acknowledge these limitations and build with appropriate safeguards, redundancy, and risk management.
🔥 Popular Blockchain Oracles
The oracle landscape has evolved from a handful of experimental projects to a competitive ecosystem with specialised solutions. Here are the major players:
- Chainlink. Founded in 2017 and launched in 2019, Chainlink is the undisputed industry leader. It has enabled over $25 trillion in transaction value and remains the standard oracle solution across web3. Chainlink offers a comprehensive suite: Price Feeds for DeFi, VRF for gaming randomness, automation for smart contract maintenance, Proof of Reserve for asset verification, and CCIP for cross-chain interoperability. Its security model uses multiple layers of decentralisation: data from multiple sources, validated by independent node operators. Major partnerships with traditional finance institutions like Swift signal its evolution beyond pure crypto infrastructure into bridging traditional finance with blockchain.
- Chronicle. Launched in 2023 and developed by MakerDAO (one of DeFi's oldest protocols), Chronicle focuses on transparency and efficiency. Its "scribe" system cryptographically signs data, allowing anyone to verify exactly where data came from and who validated it. This radical transparency appeals to protocols wanting clear data provenance. Chronicle specialises in price feeds for DeFi lending and derivatives, positioning itself as a transparent alternative to established oracle providers, all while leveraging MakerDAO’s deep experience in building reliable oracle infrastructure.
- RedStone. Founded in 2021, RedStone represents the new generation of oracle design built for flexibility and cost efficiency. It supports pull, push, and hybrid models: instead of constantly pushing expensive data on-chain, RedStone stores signed data off-chain and only brings it on-chain when needed. This architecture drastically reduces costs and enables support for custom assets that don’t justify frequent updates. It now serves 100+ chains and rollups, used by more than 170 projects, and integrates restaking mechanisms (e.g. EigenLayer) to strengthen network security. RedStone is gaining traction among newer high-performance chains and RWA-focused protocols as a cost-effective, modular alternative.
- Pyth Network. Launched in 2021 on Solana, Pyth partners directly with first-party data providers — the actual exchanges, market makers, and financial institutions creating the data. Instead of scraping public APIs, Pyth receives data directly from sources like Jane Street and Jump Trading, enabling ultra-low-latency and high-fidelity feeds. Initially dominant in Solana DeFi, Pyth has now expanded to 100+ blockchains using a pull-based mechanism. In 2025, it introduced Pyth Lazer for millisecond-level updates and serves hundreds of real-time feeds across asset classes. It remains the go-to oracle for high-frequency trading and on-chain derivatives requiring near-real-time data.
Different oracles optimise for different priorities:
- Maximum security and ecosystem: Chainlink (oldest, most battle-tested);
- Transparency: Chronicle (MakerDAO pedigree);
- Cost efficiency and flexibility: RedStone (a modern model);
- Ultra-low latency: Pyth (first-party data sources).
Most serious protocols use multiple oracle providers and aggregate their data, ensuring that even if one fails, they have fallback options. This oracle diversification represents the best practice in smart contract security.
Key Takeaways
- Oracles are blockchain's bridge to reality. Without them, smart contracts are isolated programs with no connection to the world they're supposed to serve. Oracles transform blockchain from a closed system into an infrastructure that can coordinate real economic activity.
- The oracle problem is fundamental. Adding oracles to trustless systems introduces trusted components, creating potential points of failure and manipulation.
- Security through decentralisation. The strongest oracle solutions don't rely on single entities but rather aggregate data from multiple independent sources and node operators. No oracle is perfectly secure, but decentralised oracles are significantly harder to manipulate than centralised ones.
- Different use cases need different oracles. A high-frequency trading platform needs different oracle properties than a quarterly insurance payout. Understanding the trade-offs between cost, speed, decentralisation, and data quality is crucial for choosing the right oracle solution.
- Oracle diversity matters. Just as investors diversify portfolios, smart contract developers should diversify oracle dependencies. Relying on a single oracle provider creates systemic risk. The strongest protocols use multiple oracle sources and have fallback mechanisms.
Final Thought
Here's the beautiful irony of blockchain oracles: we built trustless systems to eliminate middlemen, then immediately realised we needed to trust new middlemen to make those systems useful.
The oracle problem isn't really about technology; it's about the reality that pure code can't capture everything. A blockchain can perfectly execute "if X then Y," but someone still needs to tell it what X is. And in that gap between mathematical certainty and reality lies both the challenge and the opportunity.
As we push blockchain toward mainstream adoption, oracles will become invisible infrastructure. Until then, remember: every time you interact with a DeFi protocol, place a prediction market bet, or use any smart contract touching the real world, you're trusting an oracle. So, choose wisely.
If you learnt something new today, pass it on. Share it with your community. Let’s spread the knowledge and level up together.
That's a wrap, normies. Next time, we're finally diving into Bitcoin — separating the truth from the myths. Get ready 👻
Cookies She Left Behind
If you'd love to dig deeper into the topic, I'd also recommend reviewing the below:
- What are Oracles in Crypto? by Whiteboard Crypto