Sei Network Passes SIP-6, Clearing Autobahn Vote Without Launch Date

Sei Network's governance vote passed SIP-6 as of Nov. 3, when staked participation reached 46.63% against the proposal's 33.4% requirement — a margin of 13.23 percentage points. The vote clears a governance step for the Autobahn consensus upgrade inside Sei Giga; it does not activate the upgrade.

Sei's rollout plan still requires a public testnet, independent audits and further engineering work before mainnet, and no activation date has been announced. The published roadmap has described Autobahn mainnet as "coming soon," without a launch date.

What does SIP-6 change about block assembly?

SIP-6 rewrites how blocks get assembled. Each active validator keeps a separate lane for proposed transactions, so validators package activity concurrently rather than routing it through a single producer. Stake weight determines which validator takes the next turn coordinating references to certified batches. Transaction ordering, data availability and execution proceed in overlapping stages.

The design spreads transaction packaging across active validators and pools their combined bandwidth, cutting reliance on one block producer for transaction inclusion and sequencing. For venues building on Sei, that concentration point is the operational concern: a single producer is both a latency bottleneck and a single point of censorship and liveness failure.

• A separate proposed-transaction lane per active validator
• Concurrent transaction packaging instead of one producer queue
• Stake-weighted rotation for coordinating references to certified batches
• Overlapping ordering, data availability and execution stages

The burden also shifts. Validators, not one operator, run the packaging work, so redundancy replaces centralization at the cost of coordination overhead, with stake weight serving as the tiebreaker for turn-taking.

Which trading functions does the upgrade target?

Sei names onchain trading functions as the intended uses: placing and canceling orders, and updating prices. Those are goals for the upgrade, not functionality the approval itself puts on mainnet, and the distinction matters for anyone pricing execution risk on Sei today.

What still stands between the vote and mainnet?

Autobahn is the consensus component of Sei Giga, and the broader overhaul also tracks SIP-3, which moves Sei toward an Ethereum Virtual Machine (EVM)-only stack, with Eidos for storage and Ares for execution. Sei published an earlier draft of the Autobahn plan on Oct. 28, and the roadmap lists completion of SIP-3 in the same set of pre-mainnet gates as audits and test results.

• Completion of SIP-3 and the EVM-only stack migration
• Independent audits
• Rehearsals and test results
• A public testnet
• Mainnet activation, with no date announced

Passing SIP-6 clears a governance hurdle; it does not establish that the remaining work is complete. That sequencing matters because consensus changes and an execution-stack migration interact: faster ordering only pays off if the layer that executes and stores transactions can absorb the load the new ordering layer creates.

How do the throughput and finality figures compare?

The roadmap gives the public testnet a target of 200,000 transactions per second and 400-millisecond finality. Those figures sit separately from an under-250-millisecond ordering time recorded in an internal development-network test, and SIP-6 does not reconcile the two measurements. One is a throughput target at testnet scale; the other is a single ordering observation. Neither is a mainnet guarantee.

What would have to happen next?

The next hard checkpoint is the public testnet, where the 200,000-transaction-per-second target and 400-millisecond finality get checked against the internal ordering result, and where SIP-3, the independent audits and the rehearsals have to land. Until that window produces dated results, "coming soon" is the whole of Sei's schedule, and launch timing — not the vote count — remains the open variable.