Reth Ships Three Releases in 11 Days After EVM2 Core Swap

Paradigm's reth team pushed three dated releases of its Rust Ethereum execution client within 11 days, culminating in reth v2.10.1 on November 6, 2026 — a maintenance release the project's own GitHub notes describe as a "follow up to the EVM2 release with further performance and stability fixes."

The release cadence began on October 29, 2026, with reth v2.9.0, which the project's changelog says replaced revm with evm2 as reth's execution engine — a change the notes flag as "a breaking change for SDK users who build on reth's EVM, executor or inspector types," while stating node operators do not need to change any configuration. The same release notes credit the swap with reducing monomorphization and trimming unused dependencies to make builds lighter, and add snap-sync progress metrics and JIT support in reth-bb.

Six days later, on November 5, 2026, the team shipped reth v2.10.0, described in its own release notes as "a hardening release." Per the changelog, it fixes an engine panic that could occur after a reorg below the persisted tip, bounds the work an eth_callBundle RPC call can perform, and stops the reth download command from deleting files outside the configured datadir. The same notes list several RPC correctness fixes, peer-to-peer interoperability fixes, a parallelized storage-verification path for db repair-trie, and a new --tracing-otlp flag that writes trace spans directly to a local file. The notes also flag an SDK-level change: the commit-condition callback on the BlockExecutor and BlockBuilder types now receives additional transaction data.

On the same date, November 5, 2026, the Optimism team published a related op-reth v2.8.1 release for its reth-based OP Stack client. The release notes state plainly that "all node operators should upgrade to this release," describing a fix to the eth_capabilities endpoint: on OP Mainnet, the endpoint had reported historical data availability from block 0 rather than from the Bedrock upgrade block, which per the notes could route pre-Bedrock RPC requests to nodes unable to answer them. The fix ensures every resource now reports an oldestBlock no lower than the chain's Bedrock block.

Reth's own documentation rates the update priority for both payload builders and non-payload builders as "Medium" for the v2.10.1 release, per the project's release page.

Taken together, the three paradigmxyz/reth releases and the op-reth companion update show a client team iterating quickly after a core architecture change. The evm2 swap in v2.9.0 is the structural event; the two releases that followed within a week are framed by the project itself as stabilization and correctness passes rather than new feature work. Node operators and payload builders tracking reth's release cadence can verify update priority and binaries directly from the v2.10.1 release page, which also publishes a PGP signature for binary verification.