paradigmxyz /reth

Modular, contributor-friendly and blazing-fast implementation of the Ethereum protocol, in Rust

★ 5,859⑂ 2,604👁 60⑃ 22,699● 5,618▤ 106
RustApache-2.0Created 2022-09-15reth.rs/
下载:Reth v2.11.0Reth-2.11.0 ↓2.11.02026-11-11
+2
日增长
5,859
stars
2,604
forks
60
watchers
22,699
prs
5,618
issues
106
releases

README

reth


![CI status][gh-ci]
![cargo-lint status][gh-lint]
[![Telegram Chat][tg-badge]][tg-url]

Modular, contributor-friendly and blazing-fast implementation of the Ethereum protocol

!

Install
| User Docs
| Developer Docs
| Crate Docs

[gh-ci]: https://github.com/paradigmxyz/reth/actions/workflows/unit.yml
[gh-lint]: https://github.com/paradigmxyz/reth/actions/workflows/lint.yml
[tg-badge]: https://img.shields.io/endpoint?color=neon&logo=telegram&label=chat&url=https%3A%2F%2Ftg.sumanjay.workers.dev%2Fparadigm%5Freth

 What is Reth?

Reth (short for Rust Ethereum, pronunciation) is a production-ready Ethereum execution layer client focused on modularity, performance, and user-friendliness. Reth is compatible with all Ethereum Consensus Layer (CL) implementations that support the Engine API. It is built and driven forward by Paradigm, and is licensed under the Apache and MIT licenses.

 Note: OP-Reth has moved to ethereum-optimism/optimism. Git history has been preserved.

 Goals

1. Modularity: Every component is built to be used as a library: well-tested, documented and benchmarked. Import crates, mix and match, and innovate on top of them. Learn more about the project's components here.
2. Performance: Built with Rust, Alloy, evm2, and Foundry — battle-tested and optimized for speed. Check the ethPandaOps Lab Dashboard for a third-party comparison against other Ethereum clients.
Here's what that looks like in practice on Ethereum Mainnet:

!

3. Free for anyone to use any way they want: Apache/MIT licensed, no business license restrictions.
4. Client Diversity: More client implementations make Ethereum more antifragile.
5. Support as many EVM chains as possible: Reth can sync Ethereum and other EVM chains. If you're building one, reach out.
6. Configurability: Profiles for different use cases — from high-performance RPC operators to hobbyists on consumer hardware.

 Status

Reth is production ready, and suitable for usage in mission-critical environments such as staking or high-uptime services. We also actively recommend professional node operators to switch to Reth in production for performance and cost reasons in use cases where high performance with great margins is required such as RPC, MEV, Indexing, Simulations, and P2P activities.

- We released Reth 2.0 in April 2026. See the release notes and blog post.
- We released 1.0 "production-ready" stable Reth in June 2024.
  - Reth completed an audit with Sigma Prime, the developers of Lighthouse, the Rust Consensus Layer implementation. Find it here.
- We released multiple iterative beta versions, up to beta.9 on Monday June 3, 2024, the last beta release.
- We released beta on Monday March 4, 2024, our first breaking change to the database model, providing faster query speed, smaller database footprint, and allowing "history" to be mounted on separate drives.
- We shipped iterative improvements until the last alpha release on February 28, 2024, 0.1.0-alpha.21.
- We initially announced 0.1.0-

Top issues

Discussions

Latest release

Reth v2.11.0 v2.11.0 2026-11-11
!image

 Summary

Reth v2.11.0 is a hardening and performance release. RPC calls that can do unbounded work are now capped or cancellable (eth_callMany, trace_callMany, debug_traceCallMany, eth_getProof, mev_simBundle, eth_simulateV1), and the release brings a broad set of transaction pool, P2P and storage correctness fixes. EIP-7702 authorization recovery is parallelized, P2P skips decoding responses it never asked for, and overlay provider setup is cheaper.

SDK users: Ethereum block execution now runs on evm2::block, and reth's executor types are thin adapters over it (see Breaking Ch

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON