> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stable.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Introduction to Stable's full-stack optimization covering consensus, execution, database, and RPC layers.

## Full stack core optimization

<img className="block" src="https://mintcdn.com/stablelabs/J4B7HU7gv5jVOi-7/images/transaction-lifecycle.png?fit=max&auto=format&n=J4B7HU7gv5jVOi-7&q=85&s=9b9438a53ab255382e5755dd91327540" alt="Blockchain Transaction Lifecycle" width="1600" height="596" data-path="images/transaction-lifecycle.png" />

The lifecycle of a blockchain transaction, from submission to finalized result, passes through multiple tightly connected stages. A transaction is first submitted through the **RPC** interface, added to the **mempool**, packaged into a block, validated through **consensus**, executed by the **state machine**, and finally written to persistent storage in the **database**. Only after completing this full pipeline does the user receive a confirmed result.

Improving just one stage in isolation is not enough. Any inefficiency in the pipeline can impact the overall performance of the system. This is why Stable focuses on optimizing the blockchain stack from top to bottom.

The following pages describe how Stable upgrades each layer of its architecture (Consensus, Execution, Database, and RPC) to ensure reliable and high-performance transaction processing.

## Next recommended

<CardGroup cols={2}>
  <Card title="Consensus" icon="handshake" href="/en/explanation/consensus">
    Learn how StableBFT extends CometBFT for high throughput and low latency.
  </Card>

  <Card title="Execution" icon="cpu" href="/en/explanation/execution">
    See how Stable EVM runs transactions in parallel with Block-STM and Optimistic Block Processing.
  </Card>

  <Card title="Storage (StableDB)" icon="database" href="/en/explanation/stable-db">
    Understand how decoupled state commitment and memory-mapped storage remove the disk I/O bottleneck.
  </Card>

  <Card title="High performance RPC" icon="zap" href="/en/explanation/high-performance-rpc">
    Understand the split-path RPC architecture separating reads from writes.
  </Card>
</CardGroup>
