⬆️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 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.
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.
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:
Proposal Submission
Fixed: July 14 ~3:00 PM CET
Governance proposal submitted for voting.
Voting Period Ends
Fixed: July 15 ~3:00 PM CET
Voting closes; validators must have cast votes.
Proposal Activation
Fixed: July 15 ~5:00 PM CET
Upgrade activates at specified block height.
Validator Public Key Registration
Starts post-activation
Validators register SEDA public keys (required for batch signing).
Threshold Reached (80% Voting Power Registered)
Dynamic
When 80% of voting power has registered, triggers grace period.
Grace Period
1 day after threshold
Final opportunity to register keys before activation of batch signing.
Overlay Node Onboarding
In parallel after proposal activation
Overlay Nodes are registered and configured to resolve data requests.
Mainnet Upgrade Completion
After grace period & Overlay Onboarding
Mainnet Data Request capabilities are operational.
Last updated
Was this helpful?