As of block #224# 201 091, Sei v6.6 is officially live. V6.6 includes nearly 400 pull requests, including the first mainnet components of Sei Giga. This is the largest upgrade to Sei since EVM support was added in May 2024. Here are the most important takeaways: Execution and storage - The Ares Upgrade begins: the v2 executor is being retired. The Giga hybrid executor is now the default execution path on mainnet, with roughly 10x the throughput. Every upgraded node runs it. v2 stays on as a per-transaction fallback, and a full v2 node runs on every network comparing results block by block. - The Eidos Upgrade begins: state separation. Two years of chain state, unpicked one block at a time, with EVM history moving into its own database instead of sharing one with Cosmos state. This is the most error-prone part of shipping Giga, engineered to be a non-event for operators. Security - Over 30 issues fixed across DoS and resource exhaustion, P2P attack surface, and supply-chain hardening. Closer to 50 counting race conditions and upstream security backports. Node operators - Network synchrony is significantly improved. Consensus timeout parameters were retuned, with devnet showing up to 15% fewer vote misses and block proposal latency cut in half. More predictable block times, less bandwidth spent on catchup. - Two configuration footguns are gone. Both have caused validator outages in the past. Simpler values, less to get wrong. - Pruning no longer drags nodes behind the chain. It now compacts the deleted key range as soon as each prune finishes, holding prune runs at a steady ~5 minutes and head lag under 60 blocks. Builders - Receipts are backed by Giga+OCC by default: invisible txs no longer get receipts, state-transition errors that bump the nonce now do, and EIP-1559 effective gas price lands on the receipt. - JSON-RPC error handling is now spec-correct; query surfaces are bounded, with proper pagination. - Historical debug_trace sits behind a config flag, with a 10,000 block default lookback.

The Sei 6.6 proposal is live. 6.6 starts two of the biggest pieces of the Sei Giga Upgrade. Ares, execution engine rebuilt for Giga, becomes the default on mainnet. Eidos, the new storage layer, begins moving chain history into its own database.

First there was Autobahn, the breakthrough protocol making Sei Giga possible. Then came Ambulance, the award-winning successor. Now, a new paper introduces builds on both to push the limits of stable low latency. Introducing Hermes: the final component of the Giga Roadmap.

A whitepaper on a Multi-Proposer protocol for Monad just went up on Arxiv, authored by @Category_Labs. Two scoops: 1. Monad is pursuing Multi-Proposer consensus. This will be their next big public narrative. 2. Like Solana, they're following Sei's decision to go multi-proposer.

Sei Giga v2 series, part 1: the ordering model Giga's Autobahn consensus finalizes a tip cut: a collection of proposals from multiple proposers. This fixes the set of txs and their ordering for future views. But how are txs ordered once a cut of proposals is finalized? 🧵

Yesterday we put out v2 of the Giga Whitepaper. It features new benchmarks from our internal testing, many improvements based on our work implementing Giga over the last year (and some new research breakthroughs). Most excitingly though, it lays the foundation for some exciting future work. We also introduce Ambulance, a consensus paper with Neil Giridharan, @siobhcroo, and @kartik1507 (amongst many others), which will appear at OSDI this summer, which represents the next step in Giga’s consensus work, it achieves Autobahn performance in the good time slots and up to an order of magnitude better in the bad ones. Ambulance, Sedna, BUDs are all representative of the work we’re doing at Sei to push Giga into being the best MCP blockchain there is. They represent meaningful progress over the last year, and the start of the journey towards the Giga Upgrade going live on mainnet. Read the papers here: Ambulance: v2 of the Giga Whitepaper: Sedna: BUDs:

Announcing the Sei Giga v2 series: in the coming days, I will go in detail through each of the technical and engineering efforts that motivated v2 of the whitepaper. From execution optimizations, to state proofs, to consensus. Many of these are are applicable and necessary to many high-performance chains (or similar). Stay tuned!

V2 of the Sei Giga Whitepaper is live. Sei Labs can now confirm that Giga will have substantially better performance and an improved featureset over what was initially described. Giga will have: - Sub-250ms finality - Pre-execution privacy - Protocol-level MEV resistance. Here's what's new and why it matters: Finality: sub-250ms, down from 400ms. Autobahn's pipelined two-phase BFT is designed to reach consensus in 1.5 round trips versus Tendermint's 3. In the design, ordering finality is decoupled from state attestation: every trade will settle at consensus speed, while execution happens asynchronously so heavy computation never delays block production. State commitments will use lattice hash divergence digests over write logs, eliminating Merkle tree computation from the hot path. The biggest addition in this new version is Sedna. On single-leader chains, the block producer controls ordering. On multi-proposer chains, any proposer that sees your full transaction can duplicate it and race you in the merge order. The whitepaper identifies three MCP-specific MEV channels. Sedna is designed to address all of them. Senders would encode transactions into rateless fragments distributed across proposer lanes, and no proposer would see the full payload until the finalization threshold is crossed. Pre-execution privacy without encrypted mempools, threshold decryption or adding latency to the critical path. Under Giga, transaction ordering will be fully deterministic. The tip priority merge rule orders lanes by descending maximum tip, preserves intra-lane position, and deduplicates by hash. The output is a pure function of the committed cut. Every correct executor will derive the same ordered transaction sequence from the same finalized data. Storage and execution were also substantially upgraded in v2. Storage: flat LSM-based key-value store will replace Merkle Patricia Tries. Tiered hot/warm/cold architecture. Divergence commitments over write logs introduced. Execution: Block-STM parallel execution with optimistic concurrency control. Pipelined parsing, address recovery, and signature verification. The paper also clearly defines: - Production Sedna with PIVOT-K incentive layer - Autobahn consensus upgrades Forthcoming research: - Full transaction fee mechanism - Full-scale PQC alternatives beyond ML-DSA - Giga tokenomics

Introducing Ambulance: the successor to Autobahn and a landmark in BFT consensus. It replaces consensus timeouts, delivering up to 10.8x lower latency during severe consensus delays.

An encrypted mempool needs a committee to hold the decryption key and release it. This adds latency and creates an attack target. Sedna will have no key. It will split each transaction across Sei Giga's proposers, so no one ever holds the whole thing.

Thank you @jdetychey for speaking on $ETH issuance at yesterday's All Protocol Devs Happy Hour! And thank you to @SeiNetwork for hosting our group again for these discussions. 🙌

Unironically, @PhoenixTrade is much more exciting than @HyperliquidX. Censorship resistance matters, and regulatory scrutiny is an existential threat to Hyperliquid. To be resilient, we need more decentralized perp DEXes that actually run on the L1.

The inbound transfer of IBC assets to @SeiNetwork has been disabled, following a community proposal. Any wallets still holding IBC assets on the Sei Network need to bridge those tokens before outbound IBC transfers are also disabled. Here's how:

As the Sei protocol completes its transition to a unified, EVM-only architecture, exchanges and custodians supporting the SEI token need to migrate customer holdings before support for Cosmos and IBC-related functionality is deprecated

MIT's @ccatalini was at the Sei offices to talk about the economics of AGI for rcnyc. What happens when intelligence is abundant and commoditized? The emerging solution is a verification economy, the only scarcity left. s/o @curiousgurnoor for the collab

reth 2.0 hitting 1 gigagas/s execution is a real milestone. but on its own it doesn't move the needle much. execution has never been the binding constraint on L1 throughput. consensus and data propagation are, and have been for a while. a faster execution client running on top of the same consensus layer still inherits that ceiling. most L1s still order things sequentially: sequencer produces a block, consensus commits, and execution runs. when execution is fast, the limitation is how quickly you can agree on what to execute next. if consensus takes 500ms and execution takes 5ms, you've got more performance than you can actually use. the interesting architectural work is improving consensus, and then decoupling consensus from execution. async execution, where consensus reaches agreement on ordering without waiting for state, and execution runs in parallel. multi-proposer chains like Giga are designed to make these performance gains usable

SIP-03 update: validators accepted a proposal that has effectively disabled new CosmWasm code uploads and contract instantiations. Existing CosmWasm contracts are unaffected. IBC transfers remain enabled for IBC assets. For more:

Multi-proposer blockchains are meant to solve the monopoly on transaction inclusion inherent to single-proposer chains. But multi-proposer designs only solve half of it. Censorship resistance keeps proposers from blocking your transaction; it doesn't keep them from reading it and extracting MEV. Why does this matter? Because in the context of trading, MEV creates inefficient price discovery. If blockchain is fundamentally trading infra, bad prices have follow on effects for the lending, prediction, and derivatives markets that consume those prices. Giga will account for this with Sedna, a protocol that splits each transaction into rateless coded symbols and disseminates small bundles of those symbols across multiple proposer lanes, such that no single lane ever holds enough fragments to reconstruct the payload. The result is a design that eliminates the most common forms of MEV (front running, sandwich attacks, etc.) almost entirely. For trading, that means order flow privacy is a property of the protocol. On single-proposer chains, the solutions for common MEV are application-layer workarounds: private mempools, encrypted order flow auctions, etc. These work to varying degrees, but they ask users to trust an additional party (i.e., trade one monopoly for another) or accept added latency. Sedna moves that protection into consensus, tying privacy to the same data layer Giga's consensus already requires for liveness.