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

# Cosmos EVM

> The recommended digital ledger chain and its published chain-layer performance figures.

Cosmos EVM is the recommended chain for the digital ledger. It ships in the
Cosmos Tokenization Suite (CTS) evaluation environment.

Cosmos EVM is a standard Cosmos SDK chain with the EVM module. It runs as
`evmd` on the Cosmos 2026.1 release family, which includes IBC v2.

Two properties distinguish it from a generic Ethereum Virtual Machine chain.

Precompiles are contracts that execute common operations natively, and they run
significantly more efficiently than the same operations interpreted as Solidity.

Native IBC is the direct integration of
[Inter-Blockchain Communication](/ibc/overview). Connectivity to counterparty
banks and other networks therefore does not require a custom deployment.

Interoperability is the reason the digital ledger exists: a chain that cannot
reach a counterparty is a database with extra steps.

## Performance

These are chain-layer figures for Cosmos EVM. CTS inherits the throughput
of whatever chain hosts the digital ledger.

| Measure              | Figure                                                    |
| -------------------- | --------------------------------------------------------- |
| Sustained throughput | Roughly 1,800 to 2,000 TPS                                |
| Block time           | Sub-second                                                |
| Finality             | Instant, single block, with no probabilistic confirmation |

Published benchmarks ran on 5 to 10 equal-stake validators plus non-validating
RPC nodes for queries and ingress, each node on 32 vCPU and 32 GB RAM, tested
both colocated and geo-distributed across up to 5 data centers. The workload was
ERC20 transfers and gas-token sends.

Single-block finality is the property that matters most for settlement. There is
no confirmation depth to wait for, so a transaction is either final or it did
not happen. See [Finality](/settlement/finality).

<Note>
  These figures describe the chain layer. CTS adds per-transaction work on
  top, including core ledger integration and reconciliation, which has not been
  separately load tested end to end. Treat the figures above as an upper bound for
  the on-chain leg rather than as an end-to-end number for CTS.
</Note>

## Sizing

The benchmark nodes above are a good reference point for maximum performance.
Higher specifications will not increase performance further, so treat 32 vCPU
and 32 GB RAM as a baseline and adjust downward where the expected load allows.

<Note>
  Per-bank production sizing is not yet documented. Scope it with the Cosmos
  Tokenization Suite team.
</Note>

## Related

* [Overview](/digital-ledger-support/overview)
* [Alternative Chains](/digital-ledger-support/alternative-chains)