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

Introduction

A technical breakdown of the SEDA Network architecture.

SEDA | The Evolution of Data and Blockchains

Blockchain networks are isolated execution environments that lack the ability to directly interface with data sources beyond their native environment. This isolation creates a fragmented landscape between blockchain networks and any data source from the traditional internet. Furthermore, this isolation prevents blockchain networks from unlocking the full potential of their technology, which relies heavily on its capability to query data beyond the confines of the network itself.

Smart contract-based systems, commonly referred to as "oracles'', were developed as a technology to bridge this gap. Yet, the prevailing oracle systems exhibit shortcomings, such as unsustainable economic models, centralized bottlenecks, bandwidth restrictions, and limited accessibility, let’s call these systems oracles 1.0. When a smart contract depends on oracles 1.0 designs, they inadvertently sacrifice some of the advantages of their base network by introducing a single point of failure.

In this litepaper, we delve into how SEDA has solved these challenges, offering a scalable and secure solution that aligns with the core principles of permissionless technology, enabling the next evolution of oracles, oracles 2.0. SEDA is a layer one network that supports the permissionless data flow from any source to any destination network. SEDA addresses the core centralization and failure risks we see today when accessing off-chain data. SEDA is a necessary building block to achieve a modular, purpose-built future for layer one and layer two networks. SEDA is the foundation for data in web3.

Last updated 1 year ago

πŸ“œ
ℹ️