WHITE PAPER
  • Abstract
  • Introduction
  • API Connectivity Problem
    • 1.1 Oracle problem: A source-agnostic misinterpretation
    • 1.2 Decentralized APIs
  • Issues with Third-Party Oracles as Middlemen
  • Airnode: A Node Designed for First-Party Oracles
    • 1.1Benefits of disintermediation
      • Off-chain signing of data
    • 1.2 Barriers to API providers operating oracles
    • 1.3 Airnode features
    • 1.4 Airnode protocol
    • 1.5 API integrations
  • Decentralizing Governance through Tokenomics
    • Centralized oracle network governance
    • Management of funds
    • OracleMesh DAO
    • dAPI monetization and API provider compensation
    • OM3 tokenomics
  • Conclusion
Powered by GitBook
On this page

Airnode: A Node Designed for First-Party Oracles

First-party oracles are integral to the OracleMesh solution. This means each API is served by an oracle that is operated by the entity that owns the API, rather than a third- party. In this section, we will discuss the benefits of using first-party oracles, why it is not feasible for API providers to operate their own oracles with current available solutions, and how we aim to solve this problem with Airnode.

PreviousIssues with Third-Party Oracles as MiddlemenNext1.1Benefits of disintermediation

Last updated 1 year ago