Two thousand years of the oracle problem. Insights from Ancient Delphi on the future of blockchain oracles
This paper bridges ancient Delphic and modern blockchain oracles by developing a comparative framework and analyzing Delphic queries to propose strategies for enhancing the reliability and security of decentralized blockchain oracles.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you have a super-smart robot (a blockchain) that can make promises and keep them automatically. But there's a catch: this robot lives in a sealed room and has no eyes or ears. It can't see the weather, check the stock market, or know if a sports team won. To function, it needs a messenger to bring it information from the outside world. In computer science, this messenger is called an Oracle.
The problem? How do you know the messenger isn't lying, getting confused, or being bribed? This is the "Oracle Problem."
This paper argues that we've been trying to solve this problem with fancy new technology, but we should actually look back 2,000 years to the Oracle of Delphi in ancient Greece. The authors, a historian and a computer scientist, decided to compare the ancient Greek messengers with modern digital ones to see if the old ways can teach us something new.
Here is the breakdown of their findings using simple analogies:
1. The Two Messengers: A Priestess vs. A Data Feed
- The Ancient Messenger (Delphi): A priestess named the Pythia sat in a temple. People asked her questions about the future or big decisions. She would go into a trance (maybe from gas fumes) and speak in riddles. A priest would translate her words for the person asking.
- The Modern Messenger (Blockchain Oracle): A computer program that fetches data (like the price of Bitcoin) and feeds it to a smart contract.
- The Connection: Both are just bridges. The Pythia bridged humans and the gods; the Oracle bridges the computer and the real world. If the bridge is shaky, the whole system fails.
2. The Big Problems (and Ancient Solutions)
The paper compares specific challenges faced by both systems:
- Who is the source? (Attributability)
- Ancient: Everyone knew the source was Apollo (the god). You didn't need to check his ID; you just trusted the system.
- Modern: Blockchains try to be "trustless" (no one is trusted). But the authors suggest we might be better off if we knew exactly who the data reporter was, just like we knew who the priestess was.
- Who is to blame if it's wrong? (Accountability)
- Ancient: If the Pythia said "You will win the war" and you lost, it wasn't the god's fault. It was your fault for misinterpreting the riddle or asking the wrong question. The oracle didn't get fired; your reputation took a hit.
- Modern: If a blockchain oracle gives bad data, the people using the data usually lose money. The paper suggests we should adopt the ancient mindset: The user is responsible for picking a good oracle and understanding the answer.
- Is the message real? (Authenticity)
- Ancient: You couldn't verify the message immediately. You had to wait and see if the prediction came true. Time was the only test.
- Modern: Some modern blockchains already do this! They wait a few days before finalizing a result to make sure it's not a glitch or a lie. The paper says this "waiting game" is actually a very smart, ancient idea.
- Was the message changed? (Integrity)
- Ancient: The priestess spoke out loud. There was no signature. To stop people from changing the message on the way, the Athenians once put their questions in sealed jars. The god would point to the right jar without opening it.
- Modern: The authors propose a new digital idea based on this "sealed jar" method. You could lock your data in a digital box, have a random number generator pick which box to open, and then reveal the answer. This prevents anyone from peeking or cheating before the decision is made.
3. The "Riddle" Factor (Query Types)
The authors analyzed 167 ancient questions and found a pattern:
- Simple Questions: When people asked clear, factual questions (e.g., "Is it raining?"), the answers were short, direct, and very reliable.
- Vague Questions: When people asked complex, philosophical, or "what if" questions (e.g., "What is the best path for my life?"), the answers were long, confusing, and full of riddles.
- The Lesson for Computers: Modern blockchains work best when asking simple, clear questions about public data (like "What is the price of gold?"). If you ask a computer oracle a vague, philosophical question, it will likely give you a confusing or unreliable answer, just like the Pythia did.
4. The Main Takeaway
The paper concludes that technology alone hasn't solved the Oracle Problem. We are trying to build perfect, decentralized, anonymous systems, but the ancient Greeks had a simpler, more human approach:
- Trust a known source (like a specific oracle network) rather than trying to be anonymous.
- Make the user responsible for choosing the right messenger and understanding the message.
- Use time to verify truth.
- Keep questions simple. If the question is clear, the answer is reliable. If the question is a riddle, the answer will be a riddle.
The authors suggest that by mixing the "wisdom of the ancients" with modern code, we can build blockchains that are less prone to hacking and more reliable. They even propose a new way to handle random numbers in computers (like for lotteries) using the "sealed jar" method from ancient Athens.
In short: We don't need to reinvent the wheel; we just need to remember how the ancient Greeks managed their messengers, because the problems of trust and truth haven't really changed in 2,000 years.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.