// the find
paradigmxyz/reth
Modular, contributor-friendly and blazing-fast implementation of the Ethereum protocol, in Rust
Reth is a production-grade Ethereum execution client written in Rust, now at v2.0. It's aimed at node operators who care about sync speed and memory efficiency — RPC providers, MEV searchers, indexers — and at developers who want to build custom Ethereum tooling by importing individual crates rather than forking a monolithic client.
The crate-level modularity is real, not just marketing: you can pull in `reth-chainspec`, `reth-engine-tree`, or `reth-consensus` independently and compose them with your own pieces. Sync performance is measurably faster than geth on mainnet according to third-party benchmarks from ethPandaOps. The Storage V2 format (default in 2.0) reduces database footprint and allows history to live on a separate volume, which is a practical win for operators who want to prune aggressively. CI is thorough — unit, integration, hive compatibility tests, e2e, and reproducible builds all run on every PR.
The Storage V1 migration path is 'encouraged but not forced yet,' which means operators on old nodes are sitting on a deprecation clock with no hard deadline — that ambiguity tends to bite during a future forced migration when least convenient. The warning about NippyJar and Compact encoding being unsafe against malicious data is buried in the README footer; anyone building a service that ingests external data through these formats could miss it. OP-Reth has been moved out to the Optimism monorepo, so if you were counting on Reth as your multi-L2 story, that's now split across two repos with different release cadences. Compile times on a fresh checkout are punishing — the workspace is enormous and cold builds will test your patience even on fast hardware.