The proposal for Sei 6.6 is live. This is a huge release for Sei. Dozens of DevEx and performance improvements. Most importantly: the start of Giga on mainnet. 6.6 is the beginning of the Giga storage upgrade. A complete storage overhaul to support Giga's 200,000 TPS.

Introducing SIP-5. If a quantum threat appears, every account on @SeiNetwork has a route to become quantum-secure. In parallel we’re working to find new post-quantum signature schemes that will enable even better performance.

The perfect perp DEX has all these. – maker rebates at every tier, not just for whales – no legacy funding baseline taxing longs – cancels that beat fills – portfolio margin that nets correlated positions – one deep market per asset, not five fragmented ones

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.

Rampant MEV is a huge, unacceptable problem. Giga will neutralize MEV at the protocol layer. No single proposer to bribe, rule-based ordering, pre-execution privacy. Per @MessariCrypto: no blockchain has had all three before.

Today, I'm excited to share V2 of the Giga Whitepaper. Big changes since v1: - Even faster sub-250ms finality - Pre-execution privacy - Makes MEV on @SeiNetwork negligible Giga will be more than high-performance. It will fundamentally change onchain trading.

One of the biggest unsolved problems in blockchain consensus: what do you do if the block leader goes down? Many protocols try but fail to solve this adequately. Ambulance, by @Sei_Labs and the original authors of Autobahn, does.

Sei Giga needs MEV-resistance, inclusion guarantees, and above all, privacy. Sedna is Sei Labs' solution. It will deliver 90% of the benefits with barely 0.001% of the complexity. This is how privacy starts on @SeiNetwork.

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