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
  3. SEDA's Key Features

Forkless Upgrades

In many current decentralized systems, system upgrades are challenging and require active participation from all involved parties. SEDA allows for coordinated, forkless consensus upgrades to keep the network updated. Upgrades are proposed and decided upon by the community of SEDA token holders, and are coordinated via a governance upgrade vote.

SEDA achieves this is by having its nodes composed of modular building blocks. In our implementation, most of the SEDA node logic runs on WASM binaries, which are fetched from a source pointed to by the SEDA Governance Module. Nodes watch the SEDA Governance Module for any changes to the binary so that it can upgrade it β€œin-flight.” This mechanism allows SEDA Token holders to have true verifiable control over the future of the SEDA Network

Last updated 1 year ago

πŸ“œ
πŸ”‘
🍴