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

SEDA: an Intent-Based Modular Data Layer

Introducing SEDA: A Pioneering Shift in Data Transmission

SEDA goes far beyond today’s definition of an oracle. SEDA is a data transmission and computation network that enables a permissionless environment for developers to deploy data feeds. SEDA implements a fully modular interface that developers can use to dictate what data feeds to fetch and how to use this data for computation. This approach ensures that developers receive results that can be readily integrated into their networks and/or smart contracts. The SEDA Network consists of:

  • The SEDA Chain: which is used for settlement, and data storage for distribution.

  • The Overlay Network: a Multi-Party Computation (MPC) network that does the data querying and computation.

  • Solvers: the entities forwarding new data requests to the SEDA Chain and forwarding results to destination chains.

  • Data Providers: the (private) data providers plugging in to the SEDA Network.

The SEDA Chain and Overlay Network have security guarantees consistent with leading layer one networks. Security guarantees are facilitated through game theory, cryptography, strong backstops, and a high degree of configurability and computability.

SEDA eliminates the need for any trusted authority role within the Network with the use of specially designed economic incentives. Any entity can validate, relay, request, and supply data. As a fully interoperable layer one network, SEDA is universally accessible from any blockchain network with shared security.

Developers on destination networks can request both public and private data depending on their desired use case. The SEDA Network incentivizes data providers to participate by allowing them to earn revenue based on the utilization and the value of the data they provide. Data providers get to set their fee on a per-query basis, and will earn a percentage of the on-chain opportunities their data enables through OEV auctions, more on this later.

When issuing a data request, developers on destination networks can specify a set of instructions that determines how SEDA should perform computation on the fetched dataset. As a result, developers on destination networks utilizing SEDA can perform complex computations off-chain. These complex computations enable developers to perform more extensive computation than what would otherwise be possible within the destination network’s rigid smart contract environment.

Last updated 1 year ago

πŸ“œ
⛰️