SEDA's EVM Expansion Plan

From zero to any chain, learn how SEDA is rolling out its distribution to any network.

‍

Six Devnet versions, multiple listings, bespoke token upgrade infrastructure, a flagship product framework, hackathons and two audits later, SEDA is preparing its upgrade rollout to a feature complete v1.0 mainnet state. This article highlights our strategy to begin SEDA’s expansion starting within the EVM and ending on any and all VMs. 

‍

What Is The SEDA Prover Contract? 

‍

SEDA’s Prover Contract is being built to be available in any language. It acts as the point of communication between any network and SEDA. Prover Contracts are where networks publish data requests that are relayed to SEDA for processing via a decentralized network of solvers. Solvers relay the data results back to the Prover Contract, which parses and verifies tamper-resistant proofs that ensure the integrity of the data from SEDA’s network. Wherever there is a SEDA prover contract there is a pathway to access any data needed by builders on that network. 

‍

Learn more: https://x.com/sedaprotocol/status/1891530249734664493

‍

Prover Contract Distribution Phase 1: The EVM 

Our initial focus will be to support EVM networks in the deployment of SEDA prover contracts and connecting necessary Solvers. SEDA’s BD team has been speaking to 5+ EVM networks per day to understand their data needs not being fulfilled by legacy Oracle's rigid frameworks.

‍

Partner networks that wish to integrate SEDA from day one of the v1.0 rollout will be able to do so either by managing Provers, Solvers and token requirements themselves with SEDA’s support. 

‍

Prover contracts deployed to networks by SEDA will be selected by where the BD team identifies develop traction and need for SEDA. Our current conversations are ranging from core networks to long-tail chains ensuring that any network that needs limitless data access can have it as required. 

‍

Non-EVM Distribution Phase 2: Connecting Everywhere

During Phase 1, SEDA will be connecting with AltVMs that require the SEDA Prover contract in alternative coding languages. Networks that wish to provide their developers with unrestricted data access can connect with SEDA at any time to learn how they can fork the Prover and deploy it in their native coding language. SEDA has already had multiple discussions with leading AltVms and will likely lead phase two with Prover Contracts in Rust, Move and Sway. 

‍

If you’re interested in writing Prover Contracts in other languages excluding Solidity, connect with SEDA to learn more. Alternatively, if you’re a network looking to break the mold and have developers build unimagined use cases on your chain connect with the SEDA BD team to understand how you can access SEDA from day one of the v1.0 mainnet upgrade.

BD Team: Stefan https://x.com/stefan_rottler
Docs Link: https://docs.seda.xyz/home

‍