Vol. 1 · 7 Jun 2026

Side by side

Reth vs Tempo

Reth and Tempo both operate in the Protocol & Core part of the Tempo ecosystem. RethThe Rust EVM execution client Tempo runs on.. Tempo The payments-first Layer 1 blockchain, incubated by Stripe and Paradigm..

Reth logo
Rethmainnet

The Rust EVM execution client Tempo runs on.

Developer
Built by Paradigm.
Repository
Open-source at paradigmxyz/reth on GitHub.
Implementation language
Written in Rust.
What it is
A production-ready Ethereum execution-layer client and modular blockchain SDK/node.
Tempo logo
TempoCore

The payments-first Layer 1 blockchain, incubated by Stripe and Paradigm.

Type
Layer 1 blockchain, EVM-compatible (Reth SDK, targets Osaka)
Mainnet chain ID
4217 (0x1079)
Consensus
Simplex BFT (Commonware), ~600ms blocks, deterministic finality
Native token
None; fees paid in USD-denominated TIP-20 stablecoins

The record

How they compare

FieldRethTempo
Typeprotocol componentprotocol component
CategoryProtocol & CoreProtocol & Core
Statusmainnetmainnet
ChainsTempo
WebsiteYesYes
DocsYes
GitHubYes
Confidence92%90%
Sources43
Throughput (testnet confirmed)20K TPS
Block time600 ms
Integrated partners60 partners

Keep exploring


Answers

Reth vs Tempo: questions

What is the difference between Reth and Tempo on Tempo?
Reth is The Rust EVM execution client Tempo runs on.. Tempo is The payments-first Layer 1 blockchain, incubated by Stripe and Paradigm.. Both sit in the Protocol & Core part of the Tempo ecosystem.
Is Reth or Tempo live on Tempo?
Both are live on Tempo mainnet. Reth is mainnet and Tempo is mainnet.
Should I choose Reth or Tempo?
It depends on your use case — both serve the Protocol & Core role on Tempo. Compare them on type, status, chains, integrations and source-backed confidence (Reth: 92%, Tempo: 90%), then read each full profile before deciding.