> For the complete documentation index, see [llms.txt](https://docs.seda.xyz/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.seda.xyz/home/archvie/seda-docs-home/seda-technical-roadmap.md).

# SEDA Technical Roadmap

Unveiling the SEDA technical roadmap: From Mainnet Beta v0.1 → Mainnet v1.0.

*Disclaimer: Timelines and version design are subject to change without notice and some version of SEDA Testnet may be worked on in parallel.*

## Mainnet Beta v0.1

( ✅ Deployed )

The foundation of the SEDA network, featuring robust infrastructure and a growing validator set, ensuring the stability and security of the ecosystem.

* SEDA Chain.
* FLX to SEDA Upgrade.
* +100 Validators.
* 134m+ $SEDA staked.
* Custom and Open-Source Explorer live.

<figure><img src="https://4237789557-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWTQafbsjeB6Wu0r07ksa%2Fuploads%2FiLQO5XsI7XgbHpNJ9ElR%2Fimage.png?alt=media&amp;token=e331bd85-9f59-4c6d-ad5d-430b154fe3e5" alt="" width="563"><figcaption></figcaption></figure>

## Devnet v0.2 | Oracle Programs, Contracts & Overlay&#x20;

( ✅ Deployed )

This phase introduces the first oracle functionalities, laying the groundwork for reliable data request and settlement within the network.

* Deploy Oracle Programs for initial partners.
* Launch a single Overlay Node operated by SEDA.
* Implement Tally Chain Module for data aggregation.
* Deploy Core Contracts for on-chain data settlement.

<figure><img src="https://4237789557-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWTQafbsjeB6Wu0r07ksa%2Fuploads%2FqNaBV5al5H2uOWTC2uCz%2Fimage.png?alt=media&amp;token=9ce25ef1-9c37-413a-a839-301cb786ca75" alt="" width="563"><figcaption></figcaption></figure>

## Devnet v0.2.1 | EVM Solvers & Destination Chains

( ✅ Deployed )

EVM Solvers and the first prover contracts enable the initial integrations and proof of concepts.

* Implement initial EVM Prover Contracts with mock verification functions.
* Deploy Prover Contracts to EVM destination chains, including Base Sepolia and Sepolia.
* Launch Solver Nodes to relay DRs and results between destination chains and the SEDA network.

<figure><img src="https://4237789557-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWTQafbsjeB6Wu0r07ksa%2Fuploads%2FP57mJW037kwPwchbwmzA%2Fimage.png?alt=media&amp;token=89f3e1c4-56b3-4911-8bff-665ab66bc813" alt="" width="563"><figcaption></figcaption></figure>

## Devnet v0.3 | Data Proxies

( ✅ Deployed )

Introducing Data Proxy functionality, this version allows data providers to easily make their data accessible on the SEDA network, streamlining the integration process.

* Implement Data Proxy Registry Chain Module.
* Develop initial Data Proxy implementation.
* Update protocol and Core Contracts for data proxy support.
* Integrate Data Proxy verification into Overlay Node.

<figure><img src="https://4237789557-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWTQafbsjeB6Wu0r07ksa%2Fuploads%2F00IfkbFu2ai4t362OR5O%2Fimage.png?alt=media&amp;token=d2301390-70f9-4ed8-ab2f-900e311b5235" alt="" width="563"><figcaption></figcaption></figure>

## Devnet v0.4 | Tamper-resistance: Batch Proving

( ✅ Deployed )

Tamper-resistance mechanisms will be added to the Solver Network for security. This version will allow anyone to deploy a Solver and begin communicating inbound DRs and returning results on the SEDA testnet.

* Implement Batch Generation in Core Contracts.
* Implement Batch Chain Module to support DR batch proofs.
* Implement verification functions to Prover Contracts.

<figure><img src="https://4237789557-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWTQafbsjeB6Wu0r07ksa%2Fuploads%2FWjpGOMgEkxKbMcZZszCM%2Fimage.png?alt=media&amp;token=0d058dc1-e0b1-48f7-ac76-3256c96eccd0" alt="" width="563"><figcaption></figcaption></figure>

## Devnet v0.5 | Incentivization & Performance

( ✅ Deployed )

This phase focuses on economic incentives and performance enhancements, encouraging broader participation in the network by rewarding contributors who deploy nodes or solvers, while also improving the efficiency and reliability of the SEDA ecosystem components.

<figure><img src="https://4237789557-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWTQafbsjeB6Wu0r07ksa%2Fuploads%2FLLa0eCfYHd032RBYHXnc%2Fimage.png?alt=media&amp;token=4988639b-8c1a-40b3-bb9a-dd6ba49538b0" alt="" width="563"><figcaption></figcaption></figure>

## Devnet v0.6 | Testing Stability & Code Freeze

( ✅ Deployed )&#x20;

With all features in place, the SEDA team will conduct final network testing, followed by a code freeze and audit to ensure stability and functionality before the mainnet upgrade.

## Mainnet v1.0 | Upgrading To A Complete Mainnet

The final upgrade, where the SEDA network transitions to a fully operational mainnet, ready to support a wide range of use cases.

* Mainnet upgrade goes live with all integration partners.
* Vote for SEDA Network Inflation.
* Rewards for Network Participation.
* Multiple Oracle Programs Live.
* Complete permissionless integration available.

<figure><img src="https://4237789557-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWTQafbsjeB6Wu0r07ksa%2Fuploads%2FyiMKbrFZK8Pc9c5AHEks%2Fimage.png?alt=media&amp;token=1bbfcd41-7499-4508-af07-7a779f39c9be" alt="" width="563"><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.seda.xyz/home/archvie/seda-docs-home/seda-technical-roadmap.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.