How DeFi Protocols Choose Oracle Providers: Evidence on Sourcing, Dependence, and Switching Costs

TL;DR

This paper investigates how DeFi protocols select oracle providers, revealing that technological dependencies and switching costs significantly influence their sourcing decisions, with a preference for outsourcing when feasible.

Contribution

It provides empirical insights into the decision-making processes of DeFi protocols regarding oracle sourcing, highlighting the impact of dependence and switching costs.

Findings

Protocols prefer outsourcing when third-party solutions are available.

Immutability of smart contracts increases switching costs and lock-in.

Technological dependencies influence oracle provider choices.

Abstract

As data is an essential asset for any DeFi application, selecting an oracle is a critical decision for its success. To date, academic research has mainly focused on improving oracle technology and internal economics, while the drivers of oracle choice on the client side remain largely unexplored. This study addresses this gap by gathering insights from leading DeFi protocols, uncovering their rationale for oracle selection and their preferences regarding whether to outsource or internalize data-request mechanisms. Data are collected from founders, C-level executives, and oracle engineers of 32 DeFi protocols, whose combined total value locked (TVL) exceeds 55% of the oracle-using DeFi segment. The study leverages a one-time mixed-method survey, using tailored question paths for in-house versus third-party oracle users. Quantitative answers are summarized, compared across groups, and examined through Spearman rank-order correlations to explore pairwise associations among evaluation dimensions, while open-ended responses are inductively coded into keywords and broader themes to triangulate common selection motives and switching challenges. Insights support the view that protocol choices are tied to technological dependencies, in which the immutability of smart contracts amplifies lock-in, hindering agile switching among data providers. Furthermore, when viable third-party solutions exist, protocols generally prefer to outsource rather than build and maintain internal oracle mechanisms.