<!-- tempo-docs-context -->
> Source: [/docs/protocol/blockspace/consensus](https://tempo.com/developers/docs/protocol/blockspace/consensus.md)
> Section: [Tempo EVM](https://tempo.com/developers/docs/development.md). Build on Tempo EVM: wallets and keys, payments, transactions and fees, TIP-20 Tokens, contracts, exchange, network details, nodes, protocol specifications, and changelog.
> [Documentation index](https://tempo.com/developers/llms.txt) · [Docs skill](https://tempo.com/developers/SKILL.md)

> Tempo MCP: Use `search`, `find_pages`, `read_page`, and `code` at `https://mcp.tempo.xyz` for Tempo and related documentation.
> If an indexed page is missing or reflects an older site, read this site’s [documentation index](https://tempo.com/developers/llms.txt) and Markdown pages directly.

# Consensus and finality using Simplex BFT

Tempo uses Simplex BFT consensus to provide deterministic, sub-second finality.

## Simplex BFT Consensus

Tempo uses Simplex Consensus, implemented by [Commonware](https://www.commonware.xyz/). Simplex is a Byzantine Fault Tolerant consensus protocol optimized for fast finality with graceful degradation under adverse network conditions.

### Block Production

Blocks are produced approximately every 600ms under normal network conditions (500ms builder loop plus network latency and block validation). Proposer selection uses a VRF (Verifiable Random Function) for random leader election, providing DoS protection and MEV resistance. Once a block is finalized, it cannot be reverted.

### Deterministic Finality

Tempo provides deterministic finality rather than probabilistic finality. When a block is marked as finalized, transactions in that block are guaranteed to remain in the canonical chain. There is no reorg risk after finality.

## Validator Set

### Current Configuration

The active validator set is permissioned. See [validator setup](https://tempo.com/developers/docs/guide/node/validator-setup) for participation requirements and [validator status](https://tempo.com/developers/docs/guide/node/validator-status) for querying the onchain validator configuration.

### Fault Tolerance

Simplex BFT tolerates Byzantine validators up to a threshold:

* The network maintains safety as long as fewer than one-third of validators are Byzantine
* The network maintains liveness as long as at least two-thirds of validators are honest and online

With 4 validators, the network tolerates 1 Byzantine validator. With 10 validators, the network tolerates 3 Byzantine validators.

## Distributed Validation

Tempo uses a distributed validator set rather than a single sequencer. Multiple validators share block production responsibility. Transactions can be included by any proposer, preventing single points of censorship. The network can continue finalizing blocks as long as two-thirds of validators are online and honest.

## Degraded State Behavior

Under adverse conditions, Simplex consensus behaves as follows:

| Condition | Behavior |
|-----------|----------|
| Network partition | Block times may increase but finality guarantees are preserved |
| Validator offline within threshold | Network continues with remaining validators |
| More than one-third of validators offline | Network halts and resumes when threshold is restored |

The protocol prioritizes safety over liveness. It will halt rather than produce conflicting blocks.

## For Integrators

Treat finalized blocks as irreversible for settlement purposes. No additional confirmations are needed after finality. Query finalized blocks using `eth_getBlockByNumber` with the `finalized` tag.

## Further Reading

* [Commonware Simplex Documentation](https://docs.rs/commonware-consensus/0.0.65/commonware_consensus/simplex/)
* [Simplex with BLS12-381 Threshold Scheme](https://docs.rs/commonware-consensus/0.0.65/commonware_consensus/simplex/index.html#schemebls12381_threshold)
