SEDA engineers have shipped multiple devnet upgrades in parallel in preparation for mainnet v1.0
SEDA’s updated technical roadmap includes multiple versions upgraded in parallel, forming several key foundations necessary for a v1.0 mainnet upgrade. In the latest update, v0.2 and v0.2.1 have been completely shipped, and v0.3 is in final testing. v0.4 is now under development in parallel to actively organizing integrations with a selected group of EVM networks.
In the final months of 2024, aim to include remaining versions being shipped to devnet, followed by a complete upgrade to testnet, followed by v1.0 mainnet. In its current version, SEDA devnet incorporates vital network elements, including the first overlay nodes, solver network, and Oracle programs ready for data requests from the EVM to SEDA. In this article, we will break down each live feature deployment and explore the next steps for mainnet.
v0.2 & v0.2.1 Features & Outcomes
The first complete iterations v0.2 & v0.2.1 include the first oracle programs, overlay node and DR tally function alongside an EVM solver primed to communicate any Data Requests (DRs) from EVM deployed prover contracts.
What Are Oracle Programs?
Oracle programs are network instructions that dictate how SEDA should execute a data request. Programs are essential to providing networks with complete control, customization, and flexibility when issuing data requests to SEDA. Compared to traditional Oracle models offering preset data feeds, SEDA’s Oracle programs essentially allow a network to create its own Oracle feed like you create a custom pizza at Dominoes. Networks define:
- What data types they want (RPC, Indexer, RWA, AI etc)
- Where they do & do NOT want to query
- How data results should be returned (aggregation)
What Is An Overlay Node, And Why Is There Only One?
The Overlay Network is built to consist of thousands of Overlay Nodes run by the community. In the interest of shipping mainnet sooner rather than later as well as the ability to mitigate risk and stress test, SEDA has deployed a single SEDA-managed overlay node. The Overlay node is responsible for querying data sources and executing the instructions preset in an oracle program by a network/protocol.
What Is A DR Tally?
DR Tally is responsible for cleaning, filtering, and aggregating the data reveals issued by the overlay nodes once sources have been queried. Here, the DR Tally reads the filtration and aggregation instructions defined in the oracle program to return multiple data points as one consumable data set to the receiving chain.
What Is A Prover & Solver, And What Is Their Relationship?
The Prover contract is SEDA’s point of communication to any new network. Provers monitor core contracts from protocols or networks from which data requests are issued. Once the prover contract receives the DR, Solvers monitor the prover and bid for the right to manage the DR on behalf of the consumer.
The selected Solver then relays from any chain (currently EVM only in testing) to SEDA, where the overlay node committee is formed to execute the request. In the same interests as the overlay node, SEDA will manage the first solvers on the EVM while testing before opening the option to be a solver to the public market for further decentralization.
v0.3 & v0.4 Features And Projected Outcomes
v0.3 is in its final stages of testing. This iteration focused on deploying the proxy nodes, a massive differentiator between trad oracle models and the SEDA design system.
What Are Proxy Nodes And Why Are They A Game Changer?
Proxy nodes act as a single front door to private data sources. Data providers connect their APIs to a single proxy node, which is queriable by the overlay network. Understanding how traditional designs operate is essential to understanding why this is a game-changer.
Typical Oracle models require a new API, a new smart contract, and possible audits for every new data set a provider wants to make available to an Oracle network. This means more resources and time must be available when an oracle wants to connect new data streams to their service. On the contrary SEDA’s proxy nodes provide a single point of connection for data providers who can seamlessly link any current or new API to existing proxys in hours.
EVM Integrations And Benefits To EVM Devs
SEDA is currently organizing the initial deployments of the first prover contracts to a select group of EVM networks. Deploying the prover contract to selected EVM testnets allows their developer community priority access to deploy the first custom oracle programs on the network. Selected chains will be able to work with the SEDA dev team in deploying programs and have the first access to POC protocols currently deploying their bespoke Oracle programs to the network.
This highlights a significant milestone for EVM chains with prover contracts, unlocking first-time access to:
- Any data type available on the internet + private data sources
- Access to interop partners on SEDA (POCs)
- Access to abstraction protocols on SEDA (POCs)
- Creation of the first oracle programs on SEDA
The Final Steps To Mainnet
Final additions to SEDA’s dev/testnet before shipping mainnet v1.0 include deploying the necessary infrastructure frameworks to support an ongoing network decentralization. These frameworks will allow for the eventual deployment of thousands of community-run overlay nodes that, in their end state, will be simple enough to manage on a phone browser.
In addition, the network will support the decentralization of solver networks, allowing solvers to operate with SEDA from any L1 or L2 as the prover contract becomes available in other languages, such as Rust for the Solana community.
To stay up to date, follow SEDA or join the community channels, which allow direct contact with the team and founders.
