[Paper Review] A Study of Blockchain Oracles

Abdeljalil Beniiche|arXiv (Cornell University)|Mar 19, 2020

Blockchain Technology Applications and Security1 references88 citations

TL;DR

The paper surveys blockchain oracles, categorizing their types and architectures, and analyzes leading systems like Oraclize/Provable and ChainLink, including human oracles and design patterns for oracle integration with smart contracts.

ABSTRACT

The limitation with smart contracts is that they cannot access external data which might be required to control the execution of business logic. Oracles can be used to provide external data to smart contracts. An oracle is an interface that delivers data from external data outside the blockchain to a smart contract to consume. Oracle can deliver different types of data depending on the industry and requirements. In this paper, we study and describe the widely used blockchain oracles. Then, we elaborate on his potential role, technical architecture, and design patterns. Finally, we discuss the human oracle and his key role in solving the truth problem by reaching a consensus about a certain inquiry and tasks.

Motivation & Objective

• Explain why oracles are needed for smart contracts to access off-chain data.
• Categorize blockchain oracles by data source, direction, and trust model.
• Describe prominent oracle services (Provable/Oraclize, ChainLink) and their architectures.
• Discuss human oracles and their role in truth consensus for complex queries.
• Present common oracle design patterns used in DApps.

Proposed method

• Classify oracle types by source (software, hardware, human) and by direction (inbound/outbound) and trust (centralized/decentralized).
• Describe concrete oracle types: software, hardware, human, computation, inbound/outbound, contract-specific, and consensus-based.
• Explain centralized vs decentralized oracle architectures and their implications for trust and resilience.
• Provide case analyses of Oraclize/Provable and ChainLink architectures, including on-chain/off-chain components and workflow.
• Introduce and discuss human oracles, prediction market applications, and truth consensus mechanisms.
• Outline general oracle design patterns (immediate-read, publish-subscribe, request-response).

Experimental results

Research questions

• RQ1 What are the different types and classifications of blockchain oracles?
• RQ2 How do centralised and decentralised oracle models compare in terms of trust and resilience?
• RQ3 What are the architectural components and workflows of leading oracle services (e.g., Provable, ChainLink)?
• RQ4 What is the role of human oracles and truth consensus in oracle design?
• RQ5 Which design patterns are commonly used to implement oracles in DApps?

Key findings

• Oracle types span software, hardware, human, computation, inbound/outbound, contract-specific, and consensus-based categories.
• Decentralized (consensus) oracles mitigate single-point-of-failure risks inherent in centralized oracles.
• Provable/Oraclize provides authenticity proofs to verify off-chain data without requiring trust in the data source.
• ChainLink introduces on-chain/off-chain architecture with SLA-based oracle selection, off-chain data gathering, and weighted result aggregation.
• Human oracles enable truth consensus but introduce latency and scalability challenges; they are mainly used in prediction markets.
• Oracle design patterns include immediate-read, publish-subscribe, and request-response for diverse application needs.