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. Overview
  2. SEDA Overview
  3. SEDA Primer for Key Features

Fast Settlement & Horizontally Scalable

PreviousProgrammable Tooling and Permissionless DevelopmentNextFork-less Upgrades

Last updated 2 months ago

SEDA’s efficiency is determined by its Time To Finality (TTF), which indicates when a data request’s outcome is irreversible. TTF measures the interval between the data request initiation and the definitive network response in the oracle realm. Cross-chain solver verification on launch is estimated to be <15 seconds, whereas current estimates for existing solutions are several minutes to 2 hours.

Efficient workload distribution drives SEDA's scalability. SEDA minimizes on-chain operations without compromising security by executing data requests off-chain and in parallel. Specific factors, like data source response time, destination network block time and originating network congestion, will influence TTF for platforms like SEDA.

Page cover image