LogoLogo
  • Overview
    • SEDA Overview
      • 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
      • AI, Price Feeds, RWAs and More
        • Beyond Interoperability
        • SEDA’s Customizable Oracle Programs
      • A SEDA Network Primer
        • SEDA’s Intent-Centric Framework
        • SEDA’s Prover Contract
        • Decentralized Solver Network
        • Any Data, Any App
      • SEDA Token Primer
        • Network Utilization
        • Network Participation & Chain Security
        • Network Governance
    • SEDA Network Architecture
      • Walking Through SEDA’s Architectural Features
      • Fast Settlement & Horizontally Scalable
      • 🥩Proof of Stake Consensus
      • Programmable Tooling and Permissionless Development
      • Fork-less Upgrades
      • Modular Design Benefits
  • 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
  • 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
  • Resources
    • 🌍Upgrade your FLX to SEDA Token
      • 🔓How to Connect your EVM and SEDA Wallets
      • ➡️How to Upgrade from FLX to SEDA
      • 🚁Support and FAQs
    • 🛡️Audits
  • 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
      • 🧬SEDA Mainnet
        • 👟Operating and Running a Node
        • 🔗Linking to an External Node
        • 🏗️Creating a Validator
      • 🧪SEDA Testnet
        • 👟Operating and Running a Node
        • 🔗Linking to an External Node
        • 📸Joining Testnet Using Snapshot
        • 🤝Joining Testnet Using State Sync
        • 🏗️Creating a Validator
Powered by GitBook
On this page
  1. Overview
  2. SEDA Network Architecture

Fast Settlement & Horizontally Scalable

PreviousWalking Through SEDA’s Architectural FeaturesNextProof of Stake Consensus

Last updated 1 day 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