LogoLogo
  • Overview
    • SEDA Overview
      • SEDA Primer for Key Features
        • SEDA’s Intent-Centric Framework
        • Modular Design Benefits
        • Programmable Tooling and Permissionless Development
        • Fast Settlement & Horizontally Scalable
        • Fork-less Upgrades
      • RWAs, Price Feeds, AI and More
        • Custom Data Feeds
      • SEDA Token Primer
        • Network Utilization
        • Network Participation & Chain Security
        • Network Governance
      • Introducing SEDA's Flagship Product - The IVM
        • 🌉Intro to Interop 3.0 & Emerging Verification Markets
        • Programmable Modules
        • Triggering A Verification Data Request With An IVM
        • SEDA IVM Security
        • An IVM Summary
    • SEDA Network Architecture
      • Walking Through SEDA’s Architectural Features
      • The PoS SEDA Chain
      • Oracle Programs
      • The Overlay Network
      • Decentralized Solver Network
      • SEDA’s Prover Contract
  • For Developers
    • 📈Data Requests
      • ❓What is a Data Request?
      • 🔃Data Request Life Cycle
    • 💾Building an Oracle Program
      • Price Feed Example
        • 👋Getting Started: Price Feed
        • 🧪Testing Your Oracle Program
        • 🚀Deploying Your Oracle Program
      • 🌐Fetching Open Data
      • 🔐Advanced: API-key Gated Data
    • ⚡Access Data from Any Network
      • 🔎Access from EVM Networks
        • 🔧Using SEDA in a Contract
        • 🚀Contract Deployment
      • 🔜Access from other Networks
      • 🔜Advanced: Run your own Solver
    • 🏗️Deployments
    • 👽Interoperability Verification Module (IVM)
      • 🛸Interop Verification Module for Message-Based Bridge Protocols
      • Powering Intents and Chain Abstraction with SEDA
  • For Users
    • ⭐Getting Started
      • 🏦Wallet Overview
      • ⏬Installing Cosmos Hub on Ledger
      • ⛓️Adding SEDA Chain to Keplr
      • 🌌Delegating your SEDA
        • 📨Selecting a Validator
        • 📡Delegating to a Validator
    • 👐Tools and Dashboards
      • 🌐SEDA Explorers and Dashboards
      • 🔭Third-party Explorers
      • 📶Public RPCs + APIs
    • 🔵SEDA Token Info
      • 📈Token Charts and Tracking
      • 📊Exchanges
      • 〰️SEDA Distribution Schedule
  • For Data Providers
    • Data Proxy
      • ℹ️Introduction to Data Proxy
      • 💻System Requirements
      • 🔢Operating and Running a Data Proxy
      • 🔐Advanced: API-key Gated Data
  • For Node Operators
    • 📶SEDA Chain Guide and Requirements
      • 🎬Installation and System Requirements
      • 👟Operating and Running a Node
      • 🔗Linking to an External Node
      • 🏗️Validator Onboarding
      • 🔑SEDA Keys
      • 📸Joining Testnet Using Snapshot
      • 🤝Joining Testnet Using State Sync
  • Resources
    • 🛡️Audits
      • Trail of Bits Audit Report Repo Link - March 2024
      • Sherlock Audit of SEDA Network Full Feature Launch - April 2025
  • Legal
    • Privacy Policy
    • Terms
Powered by GitBook
On this page
  1. Learn
  2. SEDA Litepaper
  3. SEDA's Key Features

Oracle Extractable Value (OEV)

Putting a value on the data that oracles supply to destination networks has historically been challenging. As a result, oracles have adopted business models from web2. SEDA presents an opportunity to establish an additional revenue stream that can more accurately price the data provided by the system and data providers to various destination networks.

When an oracle pushes data to a network, a state change results: Whether it’s a price update, a deposit, or a generated random number, the difference in state between, before, and after the update creates an OEV opportunity. Today, we can observe these opportunities on any blockchain network. Whenever an oracle update results in an opportunity, a “gas war” commences from other network participants, known as “searchers,” who monitor the chain to spot current or imminent opportunities for value extraction. This gas war is the result of searchers bidding to be the first transaction to be executed after an oracle state change to extract the newly created value.

New data creates new opportunities. Searchers are, therefore, incentivized to pass a percentage of their potential profits to the validators of the SEDA network, a place with abundant opportunities for further value extractions.

Since searchers don’t have guaranteed execution, the gas war results in searchers, who sometimes don’t even get to execute their strategies, burning significant amounts of gas on the native destination network. This war means that a ton of value leaks as burned gas for failed transactions, and the destination network experiences unnecessary load.

SEDA’s solution removes this inefficiency and moves the opportunity for profit from the destination network to the SEDA Network. The SEDA Network can now split the profit between the network participants and data providers. SEDA achieves this by auctioning off the right to bundle transactions with the oracle updates. Searchers participate in this auction, and the highest bidder gets the guarantee that their transaction is executed as the first transaction after the oracle update is live. The result is searchers do not have to participate in “gas wars” on the destination network. As a result, there’s less value leaking through inefficient “gas wars”. SEDA’s network will now profit from the value of the data it provides, and destination networks will see less congestion around oracle updates.

Last updated 1 year ago

📜
🔑
💸