On-Chain Archaeology of Bitcoin Oracles: Evidence of Use under Limited Observability

arXiv:2610.11439 · cs.CR, cs.CY, cs.IR · Submitted 2026-10-08 · Read on arXiv

Listen

Radio episode about this paper

Transcript

Introduction to the show: ident: Security Radio. Generated commentary on the latest security and cryptography papers.

Nadia: Today's paper: "On-Chain Archaeology of Bitcoin Oracles".

Elias: The gist The study traces how Bitcoin oracle use has evolved from early services to modern discreet log contracts,

Nadia: First, who's behind it and why it matters.

Paper summary: Nadia: So to recap, this paper is titled "On-Chain Archaeology of Bitcoin Oracles: Evidence of Use under Limited Observability," and its main thesis is that tracing the evolution of oracle use—from early feeds to modern discreet log contracts—shows that protocol design and data preservation are huge factors in what we can observe or measure about these services >

Elias: They claim they did this by combining a census of Counterparty betting with a deep analysis of the Bitcoin chain up to block nine hundred fifty-eight thousand six hundred twenty-eight and searching for documented keys from projects like Reality Keys, Orisi, Oraclize, and Bitrated in a huge public-key index > <ref:2610.11439#pg1>

Priya: So the core claim is that there are two results emerging from this work. One is that early contracts remain on-chain but event descriptions have disappeared because of protocol encoding issues >

Nadia: And the second result is about modern discreet log contracts where public oracle announcements can survive even if the contracts using them cannot be found on-chain >

Elias: This matters because they look at how different designs make information public, and how that affects what we can actually track using on-chain data >

Priya: It’s about making sense of the uneven documentation across all these different oracle designs, showing where things are well documented and where they are not >

Conclusion: Nadia: The authors, Giulio Caldarelli from the University of Turin, are essentially trying to reconstruct the history of oracle activity on Bitcoin by looking at these different types of records across time >

Elias: They conclude that preserving this material—the transaction records and the publication announcements—is what keeps those connections alive so we can interpret what happened later >

Priya: For someone listening, it means that even if a specific oracle service or application goes quiet on-chain, if the documentation survives elsewhere, it still leaves a trace of its past use >

Nadia: That’s the practical implication: we need to keep looking at both the on-chain stuff and external documentation when trying to understand how decentralized data feeds operate >

Elias: So it’s less about finding one single answer and more about understanding that what you see on-chain is only part of the story if you don't also account for how the contract was designed or where the data was published >

Giulio Caldarelli

University of Turin

cs.CR, cs.CY, cs.IR

Submitted: 2026-10-08

Updated: 2026-10-08

Code: https://github.com/nostr-protocol/nips

License: http://creativecommons.org/licenses/by/4.0/

The gist: The gist The study traces how Bitcoin oracle use has evolved from early services to modern discreet log contracts, revealing that protocol design and data preservation significantly shape what can be

Key concepts

Counterparty betting
This refers to betting activities related to oracle services. The analysis showed these activities were concentrated in a few specific services, generating modest fees and limited value matching, despite most contracts reaching settlement.
DLC oracle publications
These are announcements made by oracles through the DLC (Decentralized Lending Contract) system. Analyzing these publications revealed that price and finance topics dominate the announcements, largely due to recurring series like Deribit-BTC.
On-chain archaeology
This is the process of digging into historical Bitcoin data, specifically block 0 through 958,628. The research uses this method to reconstruct past oracle activity by examining script-revealing spends and documented keys to understand how services have changed over time.

Terminology

Summary

The gist The study traces how Bitcoin oracle use has evolved from early services to modern discreet log contracts, revealing that protocol design and data preservation significantly shape what can be observed and measured

How it works

The research combines a census of Counterparty betting with analysis of the Bitcoin blockchain through block 958,628 and searches for documented keys from various oracle projects in an 854-million-row public-key index

** The study examines three main components: Bitcoin blockchain, Reality Keys, Orisi, Oraclize, and Bitrated arbitration, Counterparty Oracle feeds used by the betting protocol, and DLC oracle publications **

How it works

The analysis of Counterparty activity showed that activity was concentrated in a small number of services and applications, with modest fee revenues and limited matching of offered value, even though most matched contracts reached settlement

** The study found that Sport dominates Counterparty’s matched volume, while a daily price series dominates the archived DLC announcements **

How it works

The analysis of Bitcoin blockchain revealed that 450,015,065 script-revealing spends were identified across blocks 0–958,628

** The study measured the annual opacity index to track changes in script disclosure, noting that the share of Taproot key-path spends within the selected spending categories rose to 81.9% in 2024 after excluding inscription-related spends **

How it works

The analysis of DLC oracle publications through the Suredbits explorer and Nostr relays yielded 911 distinct announcements from the production domain

** The topic distributions across the three collections showed that Price and finance represent 71.2% of Suredbits announcements, largely due to the recurring Deribit-BTC series **

How it works

The discussion highlights that contract design affects both the information published on-chain and its usefulness for identifying applications

** The study suggests that Revealed scripts and documented keys can connect transactions to particular services, while shared script structures and spending paths that disclose no script affect attribution **

How it works

The conclusion emphasizes the need to distinguish publication activity from the contracts that consume it and consider how the relationship between the two changes across implementations

** The final finding is that Interpreting this evidence requires distinguishing publication activity from the contracts that consume it and considering how the relationship between the two changes across implementations **

The study reconstructs Bitcoin oracle activity across early services and more recent DLC publications, showing how contract design shapes the evidence available for measuring use

How it works

Counterparty findings illustrate the distinction between matching and settlement made by Clark et al. in their design of decentralized prediction markets

** The modest fees recorded show that the realized financial reward for oracle provision remained small even though most matched contracts reached settlement **

How it works

The analysis of Bitcoin blockchain revealed that matching documented public keys against the chain index identified 179 transactions associated with Orisi, Oraclize and Bitrated

** The study found that Orisi, seven of the ten keys recovered from the repository and documentation appeared in 17 mainnet transactions between 12 June and 14 October 2014 **

How it works

The analysis of DLC oracle publications through Suredbits and Nostr collections provided a complementary record of the information published by oracles

** The Nostr collection returned 219 distinct Nostr messages, comprising 167 announcement messages and 52 attestation messages using kinds 88 and 89 of the historical DLC proposal **

How it works

The study concludes that preserved service documentation maintains the connections needed to interpret activity later

** The paper notes that Preserving these materials alongside transaction and publication records maintains the connections needed to interpret them later **

Future research could extend this historical comparison to additional oracle services and publication channels, focusing on linking public announcements and attestations to contract records voluntarily shared by service providers

The processed datasets supporting this study are provided in the Supplementary Material released upon journal publication

Appendix A provides currency conversion references and calculations for the illustrative exchange rate used in the analysis

Table A1 shows Counterparty amounts converted at USD 2.40 per XCP, with an approximate equivalent of 6,300 USD for matched value

Table 3 summarizes the direct matching of documented service keys against the Bitcoin public-key index, showing matches for Orisi, Oraclize and Bitrated

Figure 7 presents Bitrated profile keys by year of earliest recovered archive capture, indicating that all matched keys belonged to early cohorts

Figure 8 shows the Taproot key-path share among selected spends from 2014–2026, with the share peaking at 81.9% in 2024 after excluding inscription-related spends

Table 5 details Lightning attribution among spent 2-of-2 P2WSH outputs, showing that the unattributed group accounted for at least 96.05% of the annual totals

Figure 9 illustrates Lightning attribution among spent 2-of-2 P2WSH outputs, with a high percentage of unassociated spending

Table 6 summarizes topic distributions in the recovered collections, showing that Sport accounts for 83.5% of Counterparty bets with identified feeds

Figure 10 shows the composition of the recovered Suredbits announcements, where Price and finance account for 71.2% of announcements

Figure 5 displays broadcast sources and betting activity, showing that only a small fraction of sources were referenced by bets

Figure 6 shows Wayback Machine search results, indicating that the July 2026 search returned no captures for several xbet.io feed URLs

Figure 8 shows the Taproot key-path share among selected spends from 2014–2026, with a share of 70.1% in the partial 2026 record

Table 4 shows annual spend counts and Taproot key-path shares, detailing the change in script disclosure across years

Table 5 shows Lightning attribution among spent 2-of-2 P2WSH outputs, with a high percentage of unassociated spending in recent years

Table 6 summarizes topic distributions in the recovered collections, showing that Test and demonstration accounts for 56.

Improvements for AI systems

  1. Bold analysis of oracle activity can be improved by distinguishing between consumption and provision, as For practitioners, they clarify which indicators describe the provision of oracle information and which describe its consumption. This allows for more nuanced understanding of protocol design effects on observed data.

  2. Improved AI systems can accurately predict the historical value of decentralized applications by incorporating measures like matched value and analyzing how it relates to fee revenue, as the paper shows that the realized financial reward for oracle provision remained small even though most matched contracts reached settlement.

  3. The system can better identify specific oracle implementations by matching documented service keys against blockchain data, as the analysis showed that for Orisi, seven of the ten keys recovered from the repository and documentation appeared in 17 mainnet transactions between 12 June and 14 October 2014.

  4. AI can model the impact of contract design on historical observability by comparing different data sources, such as transaction records versus external documentation, to understand how protocol design and data preservation shape the historical record of Bitcoin oracle use.

  5. The system can differentiate between script disclosure types to improve attribution accuracy, as it tracks how Taproot key-path spends disclose a signature without revealing a spending script and notes that this share peaked at 81.9% in 2024 after excluding inscription-related spends.

Abstract

Before Ethereum made the "oracle problem" a household term, Bitcoin already had oracles serving as feeds, key-release services, federated signers, and arbiters that carried real value on the main chain. This study traces their use and the changing evidence of oracle activity from early days through July 2026. We combine a complete census of Counterparty betting (1,149 bets), analysis of the full Bitcoin chain through block 958,628, and searches for documented keys from Reality Keys, Orisi, Bitrated, and Oraclize in an 854-million-row public-key index. We also recover DLC oracle records from an archived explorer and live Nostr relays. Two results emerge. First, early contracts remain on-chain, but many event descriptions have disappeared, and protocol encoding and API limitations complicate access to the surviving record. However, for modern DLCs, public oracle announcements can survive even when the contracts using them cannot be identified on-chain. In the script classes examined, the share of spends that reveal no script peaks at 81.9% in 2024 after excluding spends containing inscription data. Second, public registries can give a misleading picture of oracle use. In Counterparty, 95% of pre-2018 sources declaring an oracle fee were never bet on. In Bitrated, 0.1% of archived keys appear on-chain overall, compared with 10 of 19 keys captured in 2014. Sport dominates Counterparty's matched volume, while a daily price series dominates the archived DLC announcements. These findings show how protocol design and data preservation shape the historical record of Bitcoin oracle use.

Sources

Related papers