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 Network Architecture

SEDAโ€™s Prover Contract

Facilitating Near-Instant Integration To The SEDA Network

PreviousDecentralized Solver NetworkNextData Requests

Last updated 2 months ago

The SEDA Prover Contract is permissionless and can be deployed to any chain at any time. The prover acts as the point of communication between any network and the decentralized Solver Network. Solvers monitor the Prover Contract for inbound data requests and relay them to the SEDA Network. Once a data request has been executed and the results land on the SEDA Chain, the same Solver relays the results to the network via the Prover Contract. When results are relayed back, the Prover Contract can verify that the data result has come from SEDA.

By deploying a prover contract, any network theoretically gains access to any data type and achieves interoperability with any other network that has a Prover Contract. By integrating with SEDA via a single Prover Contract that is monitored by a Solver Network, SEDA can facilitate same-day access to any data from new networks. In contrast to rigid network-specific architecture, this method can reduce integration time to several hours from what has traditionally been several months.

Any network, protocol or smart contract can interact with SEDA and all its resources without directly integrating with the SEDA Chain.