> 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/mainnet-v1-upgrade-rollout.md).

# Mainnet v1 Upgrade Rollout

This page explains the process for upgrading the SEDA Mainnet to the new version.

The complete upgrade is **not instantaneous**—it proceeds through several clearly defined steps. Validators and operators **are strongly encouraged to take action** during the process to maintain consensus participation and ensure data request functionality.

Below you will find a clear breakdown of the upgrade in five steps, along with a summary timeline table.

## Step 1: Governance Network Upgrade

This initial phase is governed by the SEDA on-chain proposal system.

**Milestones:**

* **Proposal Submission**
  * **When:** Monday, July 14th \~3:00 PM CET
  * The upgrade proposal will be submitted for validator review.
* **Voting Period Ends**
  * **When:** Tuesday, July 15th \~3:00 PM CET
  * Validators must cast their votes before this deadline.
* **Proposal Activation**
  * **When:** Tuesday, July 15th \~5:00 PM CET
  * If approved, the upgrade will automatically activate at the specified block height.

**Validator Action:**

* Review the proposal in advance.
* Cast your vote before the deadline.
* Prepare your infrastructure for activation at the designated block height.

## Step 2: Validator Public Key Registration

After activation, all **Mainnet validators are required to register their SEDA public keys**, which are used for **batch signing** data requests in the upgraded network.

**When:**

* Begins immediately following proposal activation.
* No fixed end date, but prompt registration is required.

**Validator Action:**

* Follow the instructions in the [SEDA Public Key Registration Guide](https://docs.seda.xyz/home/for-chain-operators/seda-chain-guide-and-requirements/seda-keys.md) to complete the process.
* Verify your registration status before proceeding.

## Step 3: Threshold Reached (80% Voting Power)

Batch signing activation requires at least **80% of validator voting power** to have registered their SEDA public keys.

**Process:**

* Once the 80% threshold is reached, a **1-day grace period** begins.
* After this grace period, **batch signing becomes active and required.**

**Validator Action:**

* Use the grace period as a final window to register SEDA public keys.

{% hint style="warning" %}
**Important**: Validators who fail to register their SEDA public keys **will not be able to participate in consensus** once batch signing becomes active. This can lead to their validator nodes being **jailed** until registration is completed.
{% endhint %}

## Step 4: Overlay Node Onboarding

In parallel to validator registration and the threshold process, the **Overlay Node onboarding process** will take place. Overlay Nodes are responsible for resolving data requests within the SEDA Network and supporting the network’s off-chain components.

## Step 5: Mainnet Upgrade Completion

Once the validator public key threshold is met, the grace period has elapsed, and Overlay Nodes are onboarded, the Mainnet upgrade is considered **complete**.

At this stage:

* Overlay Nodes are fully operational and can resolve data requests through the SEDA Network.
* Batch signing of data requests becomes active and mandatory for all validators.

**Validator Action:**

* No further immediate actions are required beyond maintaining node uptime and monitoring your participation in consensus and data signing.

## Summary Timeline

The following table provides an overview of the upgrade process:

<table><thead><tr><th width="232.8515625">Step</th><th>Timing</th><th>Details</th></tr></thead><tbody><tr><td><strong>Proposal Submission</strong></td><td>Fixed: July 14 ~3:00 PM CET</td><td>Governance proposal submitted for voting.</td></tr><tr><td><strong>Voting Period Ends</strong></td><td>Fixed: July 15 ~3:00 PM CET</td><td>Voting closes; validators must have cast votes.</td></tr><tr><td><strong>Proposal Activation</strong></td><td>Fixed: July 15 ~5:00 PM CET</td><td>Upgrade activates at specified block height.</td></tr><tr><td><strong>Validator Public Key Registration</strong></td><td>Starts post-activation</td><td>Validators register SEDA public keys (required for batch signing).</td></tr><tr><td><strong>Threshold Reached (80% Voting Power Registered)</strong></td><td>Dynamic</td><td>When 80% of voting power has registered, triggers grace period.</td></tr><tr><td><strong>Grace Period</strong></td><td>1 day after threshold</td><td>Final opportunity to register keys before activation of batch signing.</td></tr><tr><td><strong>Overlay Node Onboarding</strong></td><td>In parallel after proposal activation</td><td>Overlay Nodes are registered and configured to resolve data requests.</td></tr><tr><td><strong>Mainnet Upgrade Completion</strong></td><td>After grace period &#x26; Overlay Onboarding</td><td>Mainnet Data Request capabilities are operational.</td></tr></tbody></table>


---

# 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/mainnet-v1-upgrade-rollout.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.
