Action required: IBC assets on Sei will become inaccessible If you hold USDC.n (USDC via Noble), USDT.kava (Kava USDT), Wormhole-bridged tokens, or any other IBC asset on Sei, you must swap, migrate, or bridge out before the governance proposal to disable inbound/outbound IBC transfers passes and is activated to avoid permanent loss of access. After this, Sei will no longer support IBC bridging of assets from Cosmos-based chains to and from Sei Network. Consult the SIP-03 Migration Guide for the full list of affected assets, required actions, and supported routes. For USDC.n specifically, see: Holders of USDC.n Need to Swap or Migrate.
A comprehensive technical overview of Sei Giga - a high-performance blockchain platform combining EVM compatibility with groundbreaking consensus, execution, and storage innovations for unprecedented throughput and sub-second finality.
Sei Giga represents a high-performance blockchain platform designed to address the persistent challenges of the “blockchain trilemma”: the difficulty of simultaneously optimizing for security, decentralization, and performance. The platform combines current optimizations with upcoming architectural innovations to achieve exceptional performance while maintaining security guarantees and developer experience.
Current Features: Sei operates with Twin Turbo consensus optimizations, parallel execution capabilities, and SeiDB storage, delivering significant performance improvements over traditional blockchains.
Upcoming Features: Advanced features including Autobahn consensus, multi-proposer architecture, and 5 gigagas throughput targets are in development and represent the next evolution of the platform.
The current consensus mechanism achieves ~400ms block times through aggressive optimization of the Tendermint BFT consensus engine. Key features include:
A planned architectural enhancement will implement complete separation of consensus and execution. Unlike traditional blockchains where these processes are tightly coupled, the upcoming Sei Giga architecture will reach consensus solely on the ordering of transactions within a block, not the resulting state change.Asynchronous Execution Architecture
Traditional Blockchain
Order Transactions
Execute & Compute State
Reach Consensus on State
Finalize Block
⚠️ Execution delays consensus
Sei Giga Model
Order Transactions
Consensus on Order
Finalize Block n
Parallel Process:
Execute Block n−1
Commit State in Block n+x
✓ Consensus proceeds independently
This approach leverages the key property of deterministic execution:Lemma 1 (Deterministic Execution): Given the same initial state (Sinit) and the same ordered sequence of transactions (tx1,tx2,...,txn), all honest nodes executing these transactions will arrive at the exact same final state (Sfinal).Key benefits of this model:
Non-blocking consensus: Heavy computational blocks don’t delay consensus
Pipelined processing: Multiple blocks can be in different stages simultaneously
Optimized resource usage: Consensus and execution use different hardware resources
Future Features: The Autobahn consensus protocol described here represents upcoming enhancements. The current system uses optimized Tendermint consensus (Twin Turbo).
The upcoming Sei Giga will employ Autobahn, a Byzantine Fault Tolerant (BFT) consensus protocol designed for high performance blockchain networks. Unlike traditional single-proposer systems, Autobahn will enable multiple validators to propose blocks simultaneously, targeting significant throughput improvements while maintaining security guarantees.Autobahn Consensus Architecture
Data Dissemination Layer (Lanes)
Lane ℓ1: Prop1, Prop2, Prop3, Tip
Lane ℓ2: Prop1, Prop2, Tip, …
Lane ℓn: Prop1, Prop2, Prop3, Tip
Each validator maintains independent lane.
Consensus Layer (Cut Formation)
Cut=[Tip1,Tip2,...,Tipn]Periodic ordering of lane tips.
Prepare Phase — Leader collects tips, forms Cut
Fast Path (n votes) — Immediate commit if all agree
Slow Path (2f+1 votes) — Additional round if needed
Global ordering through BFT agreement.
Protocol Properties
Network Model
n=3f+1 replicas
Safety
Unconditional
Liveness
Eventual synchrony
The protocol operates through two complementary layers:Data Dissemination Layer (Lanes):
Each validator maintains an independent lane for proposing transaction batches