Here's a strange fact about blockchains: they can't actually see anything outside themselves. A blockchain doesn't know the price of Bitcoin, who won a match, or what the weather is. Oracles are how that outside information gets in — and once you understand them, a lot of DeFi suddenly makes sense.
The problem oracles solve
A blockchain is a closed, self-contained system. It's brilliant at agreeing on what happened inside it — who sent what to whom — because every computer in the network can check the same internal records. But it has no built-in way to know facts from the outside world.
That's a problem, because many of the most useful applications need real-world data. A lending app needs to know the current price of the coin you put up as collateral. A prediction market needs to know the result of an election. An insurance app needs to know whether a flight was actually delayed. Without a trustworthy way to bring outside facts in, none of these apps can function.
What an oracle is
An oracle is a service that fetches real-world information and delivers it onto the blockchain in a form apps can use. It's the bridge between the outside world and the closed system — the messenger that carries facts across the wall.
The most common job by far is price feeds. Oracles constantly report the market price of assets to DeFi apps, so those apps know, for example, when a loan has become undercollateralized and needs to be automatically closed to protect the lender.
Why this matters (and where it breaks)
Oracles are critical, which also makes them a dangerous point of failure. If an app trusts an oracle for its prices, then whoever controls or corrupts that oracle can fool the app — and the app will follow its instructions perfectly while doing something disastrous.
A whole recurring category of DeFi hacks works exactly this way. An attacker manipulates the price an oracle reports — often by briefly distorting a small market that the oracle reads from — and tricks a lending app into letting them borrow far more than they should, or into unfairly liquidating other users. The app behaved "correctly" according to its code; it was just fed bad data by a compromised messenger.
This is why the design of an oracle matters so much, and why it's worth a beginner knowing to ask about:
- Multiple sources are safer. An oracle that averages many independent price sources is much harder to fool than one reading a single, easily manipulated market.
- Reputable, decentralized oracle networks are preferred over a single company quietly feeding numbers that no one can check.
- "Where does this app get its prices?" is a genuinely important safety question about any DeFi app, even if the answer takes some digging.
The takeaway
Blockchains are blind to the outside world, and oracles are the eyes that feed them real data — most importantly, prices. They make DeFi possible, and a compromised oracle sits behind an entire class of DeFi disasters. You don't need to run one or fully understand the plumbing, but knowing they exist explains both how these apps work and one of the main ways they quietly fail.
DeFi stacks risks on top of an already volatile market. Only put in what you can afford to be wrong about.