Skip to main content

Introduction

This document provides comprehensive technical specifications for Sei Giga, covering both current features and upcoming architectural enhancements. The specifications are organized to clearly distinguish between what is currently deployed and what is planned for future releases.

Current Implementation

Features and specifications that are live on the Sei network today.

Upcoming Features

Planned features and specifications in development.

Consensus Architecture

Current: Twin Turbo Consensus

Live Implementation

Protocol Specifications

Optimizations

  • Pipelined block processing
  • Optimistic execution
  • Aggressive timeouts
  • Parallel validation

Upcoming: Autobahn Consensus

In Development

Protocol Design

Key Innovations

  • Asynchronous execution
  • Data availability lanes
  • Consensus/execution separation
  • Optimized data dissemination

Upcoming: Autobahn Block Limits

When a node runs with Autobahn (Sei Giga) consensus enabled, the block producer builds payloads by reaping transactions directly from the shared mempool, subject to hard on-chain block size constraints that are enforced during payload construction. The block gas limit is no longer a single configurable Autobahn field. The producer now tracks two separate per-block gas dimensions: gas wanted and gas estimated. Each block payload records total_gas_wanted and total_gas_estimated (replacing the previous single total_gas field), and both are enforced against MaxGasWantedPerBlock and MaxGasEstimatedPerBlock limits during payload construction. These limits are derived from the genesis consensus_params.block values: MaxGasWantedPerBlock comes from max_gas_wanted and MaxGasEstimatedPerBlock comes from max_gas — the same gas limit the EVM runtime reads via ctx.ConsensusParams().Block.MaxGas. Under Autobahn, BlockResults’s ConsensusParamUpdates.Block.MaxGas reflects MaxGasEstimatedPerBlock. The max_gas_per_block field has been removed from the Autobahn config file, so it should be omitted from existing configs.
Genesis consensus_params.block.max_gas must be a positive value. If it is missing or non-positive, node startup fails with ErrGenesisMaxGasInvalid (genesis consensus_params.block.max_gas must be > 0).

In Development

Block Size Constraints

Enforcement

  • Total tx bytes may be split arbitrarily across transactions (one large tx or many small ones), up to the MaxTxsPerBlock limit.
  • Each block payload tracks total_gas_wanted and total_gas_estimated; a transaction is rejected if adding it would push either total past MaxGasWantedPerBlock or MaxGasEstimatedPerBlock.
  • The gas limits are sourced from genesis consensus_params.block; max_gas (used for gas estimated) must be greater than zero or the node will refuse to start.
  • Under Autobahn, BlockResults reports ConsensusParamUpdates.Block.MaxGas as MaxGasEstimatedPerBlock.
  • Limits are validated when the payload is built; payloads exceeding the transaction count or total byte limit are rejected.
  • The block proto size bound derives an upper limit on the encoded block used to size networking message windows.

Execution Engine

Current: Parallel EVM Execution

Live Implementation

EVM Compatibility

Full Ethereum Virtual Machine compatibility with standard opcodes and gas metering.

OCC Parallel Execution

Optimistic Concurrency Control with multi-worker transaction processing and conflict resolution.

State Management

Optimized state access patterns with SeiDB storage backend.
Execution Specifications

Storage Architecture

Current: SeiDB

Live Implementation

Architecture

Optimizations

  • Hot state caching
  • Efficient pruning
  • Parallel state access
  • Optimized serialization

Network Specifications

Protocol Parameters

Network Configuration

Consensus Parameters

Under Autobahn consensus, the validator set size is a hard protocol limit rather than just a configurable network parameter. Committee creation (NewCommittee) enforces MaxValidators = 100 and rejects any committee containing more than 100 validators with an error.

Block Parameters

Performance Targets

Engineering Targets: The following performance specifications represent engineering targets for the upcoming Sei Giga architecture with Autobahn consensus, not current network performance.

Upcoming: Target Performance Specifications

Performance Targets

5B Gas per Second

Peak throughput target

<1s Finality

Transaction confirmation

200K+ TPS

Simple transfers

Developer Interface

JSON-RPC Compatibility

Ethereum JSON-RPC Support

Standard Methods

  • eth_sendRawTransaction
  • eth_call
  • eth_getBalance
  • eth_getTransactionReceipt

Enhanced Methods

  • debug_traceTransaction
  • eth_feeHistory
  • eth_maxPriorityFeePerGas

Overview

High-level introduction to Sei Giga architecture and features.

Developer Guide

Complete guide for building applications on Sei Giga.