> ## Documentation Index
> Fetch the complete documentation index at: https://seilabs-docs-bridge-release-v6-6-0.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Sei Giga Technical Specifications

> Comprehensive technical specifications for Sei Giga architecture, consensus protocols, and performance characteristics

## 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.

<Columns cols={2}>
  <Card horizontal title="Current Implementation" icon="circle-check">
    Features and specifications that are live on the Sei network today.
  </Card>

  <Card horizontal title="Upcoming Features" icon="clock">
    Planned features and specifications in development.
  </Card>
</Columns>

## Consensus Architecture

### Current: Twin Turbo Consensus

<Card horizontal title="Live Implementation" icon="circle-check">
  <Columns cols={2}>
    <Card horizontal title="Protocol Specifications">
      | Property          | Value                   |
      | ----------------- | ----------------------- |
      | Base Protocol     | Enhanced Tendermint BFT |
      | Marketing Name    | Twin Turbo Consensus    |
      | Target Block Time | \~400ms                 |
      | Finality          | Instant (1 block)       |
      | Safety Threshold  | ⅔ + 1 validators        |
    </Card>

    <Card horizontal title="Optimizations">
      * Pipelined block processing
      * Optimistic execution
      * Aggressive timeouts
      * Parallel validation
    </Card>
  </Columns>
</Card>

### Upcoming: Autobahn Consensus

<Card horizontal title="In Development" icon="clock">
  <Columns cols={2}>
    <Card horizontal title="Protocol Design">
      | Property          | Value                    |
      | ----------------- | ------------------------ |
      | Architecture      | Multi-proposer BFT       |
      | Target Block Time | Sub-second               |
      | Proposer Model    | Parallel lanes           |
      | Safety Model      | Byzantine Fault Tolerant |
    </Card>

    <Card horizontal title="Key Innovations">
      * Asynchronous execution
      * Data availability lanes
      * Consensus/execution separation
      * Optimized data dissemination
    </Card>
  </Columns>
</Card>

### 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.

<Note>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`).</Note>

<Card horizontal title="In Development" icon="clock">
  <Columns cols={2}>
    <Card horizontal title="Block Size Constraints">
      | Property                     | Value                                                                                 |
      | ---------------------------- | ------------------------------------------------------------------------------------- |
      | Max transactions per block   | 2000 (`MaxTxsPerBlock`)                                                               |
      | Max total tx bytes per block | \~2 MB (`MaxTxsBytesPerBlock` = 2000 × 1024)                                          |
      | Max gas wanted per block     | Derived from genesis `consensus_params.block.max_gas_wanted` (`MaxGasWantedPerBlock`) |
      | Max gas estimated per block  | Derived from genesis `consensus_params.block.max_gas` (`MaxGasEstimatedPerBlock`)     |
      | Block proto size bound       | Derived from `MaxTxsPerBlock` and `MaxTxsBytesPerBlock` (`MaxBlockProtoSize`)         |
    </Card>

    <Card horizontal title="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.
    </Card>
  </Columns>
</Card>

## Execution Engine

### Current: Parallel EVM Execution

<Card horizontal title="Live Implementation" icon="circle-check">
  <Columns cols={3}>
    <Card horizontal title="EVM Compatibility">
      Full Ethereum Virtual Machine compatibility with standard opcodes and gas metering.
    </Card>

    <Card horizontal title="OCC Parallel Execution">
      Optimistic Concurrency Control with multi-worker transaction processing and conflict resolution.
    </Card>

    <Card horizontal title="State Management">
      Optimized state access patterns with SeiDB storage backend.
    </Card>
  </Columns>

  **Execution Specifications**

  | Property            | Value                    |
  | ------------------- | ------------------------ |
  | VM Type             | Ethereum Virtual Machine |
  | Gas Model           | Ethereum-compatible      |
  | Execution Model     | Parallel with OCC        |
  | Supported Languages | Solidity, Vyper, YUL     |
  | Precompiles         | Standard + Sei Native    |
  | State Model         | Account-based            |
</Card>

## Storage Architecture

### Current: SeiDB

<Card horizontal title="Live Implementation" icon="circle-check">
  <Columns cols={2}>
    <Card horizontal title="Architecture">
      | Property      | Value                                  |
      | ------------- | -------------------------------------- |
      | Storage Type  | Key-Value Store                        |
      | State Storage | MemIAVL (Cosmos) + FlatKV/LtHash (EVM) |
      | Caching       | Multi-level                            |
      | Concurrency   | Thread-safe                            |
    </Card>

    <Card horizontal title="Optimizations">
      * Hot state caching
      * Efficient pruning
      * Parallel state access
      * Optimized serialization
    </Card>
  </Columns>
</Card>

## Network Specifications

### Protocol Parameters

**Network Configuration**

<Columns cols={2}>
  <Card horizontal title="Consensus Parameters">
    | Property         | Value                                  |
    | ---------------- | -------------------------------------- |
    | Max Validators   | 100 (hard limit, enforced by Autobahn) |
    | Voting Power     | Stake-weighted                         |
    | Unbonding Period | 21 days                                |
    | Slashing         | Byzantine behavior                     |

    <Note>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.</Note>
  </Card>

  <Card horizontal title="Block Parameters">
    | Property       | Value                                                      |
    | -------------- | ---------------------------------------------------------- |
    | Max Block Size | 21 MB                                                      |
    | Max Gas Limit  | 12.5 M                                                     |
    | Base Fee       | Dynamic, on-chain param; no burn (validators receive fees) |
    | Priority Fee   | Supported                                                  |
  </Card>
</Columns>

## Performance Targets

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

### Upcoming: Target Performance Specifications

<Card horizontal title="Performance Targets" icon="gauge-high">
  <Columns cols={3}>
    <Card horizontal title="5B Gas per Second">
      Peak throughput target
    </Card>

    <Card horizontal title="<1s Finality">
      Transaction confirmation
    </Card>

    <Card horizontal title="200K+ TPS">
      Simple transfers
    </Card>
  </Columns>
</Card>

## Developer Interface

### JSON-RPC Compatibility

**Ethereum JSON-RPC Support**

<Columns cols={2}>
  <Card horizontal title="Standard Methods">
    * `eth_sendRawTransaction`
    * `eth_call`
    * `eth_getBalance`
    * `eth_getTransactionReceipt`
  </Card>

  <Card horizontal title="Enhanced Methods">
    * `debug_traceTransaction`
    * `eth_feeHistory`
    * `eth_maxPriorityFeePerGas`
  </Card>
</Columns>

## Related Resources

<Columns cols={2}>
  <Card horizontal title="Overview" icon="book" href="/learn/sei-giga">
    High-level introduction to Sei Giga architecture and features.
  </Card>

  <Card horizontal title="Developer Guide" icon="code" href="/learn/sei-giga-developers">
    Complete guide for building applications on Sei Giga.
  </Card>
</Columns>