---
title: "Reth Releases v2.11.0 With Strict RPC Caps and evm2 Block Execution"
description: "Paradigm's Ethereum execution client caps heavy RPC methods at 1,024 calls, removes legacy CLI flags, and refactors execution into evm2."
url: https://basisdesk.news/news/reth-v2-11-0-rpc-caps-evm2-release
published: 2026-11-11T10:51:30.315Z
modified: 2026-11-11T10:51:30.315Z
section: Ethereum & L2s
author: Basis Desk Newsroom (AI-generated, source-verified)
sentiment: neutral
tickers: [ETH]
tags: [reth, ethereum, node-clients, paradigm, rpc, software-update]
license: Quote with attribution to Basis Desk (basisdesk.news). Not financial advice.
---

# Reth Releases v2.11.0 With Strict RPC Caps and evm2 Block Execution

Paradigm's Ethereum execution client caps heavy RPC methods at 1,024 calls, removes legacy CLI flags, and refactors execution into evm2.

## At a glance

- **What happened:** Reth published release notes for version 2.11.0, capping unbounded RPC requests, dropping obsolete CLI flags, and moving execution logic to evm2.
- **Why it matters:** RPC callers face new 1,024-call ceilings and shared gas caps, while node operators must scrub retired CLI flags to prevent startup failures.
- **Who is affected:** Ethereum node runners, payload builders, and RPC infrastructure providers using Reth.
- **What's next:** Confirmation of database migration and downgrade specifications against the final published v2.11.0 release build.
- **Primary source:** [Reth v2.11.0](https://github.com/paradigmxyz/reth/releases/tag/v2.11.0) — Reth releases

## Key points

- Reth v2.11.0 marks a high-priority update for all node operators, introducing caps on unbounded RPC queries [1].
- Calls to eth_callMany, trace_callMany, and proof endpoints are capped at 1,024 operations and subject to strict timeouts [1].
- Nodes will refuse to start if legacy CLI flags remain configured or if IPC socket permissions fail validation [1].

## Editorial remark

- **Context:** The update builds on continuous performance and architectural overhauls across the Paradigm-backed client, continuing refactoring efforts seen in earlier versions like 2.10.0 [1].
- **Impact:** Payload builders, RPC providers, and node operators must clean up CLI configuration flags and adjust large batch RPC queries to avoid query failures and startup crashes [1].
- **Watch:** Confirmation of database migration, resync criteria, and downgrade compatibility pending final build publication [1].

Ethereum execution client Reth published release notes for version 2.11.0 on Nov. 11, introducing hard limits on resource-heavy RPC queries, removing several obsolete configuration flags, and shifting Ethereum block execution to `evm2::block` [1]. The release marks a "high" update priority for both payload-building and non-payload-building node operators [1].

Under the new release, RPC methods prone to unbound computational workloads face strict operational limits [1]. Calls to `eth_callMany`, `trace_callMany`, and `debug_traceCallMany` are now capped at a maximum of 1,024 calls per request, operate under a shared `--rpc.gascap` budget, and terminate if subsequent calls begin more than five seconds after the initial one [1]. Additionally, `eth_getProof` enforces a ceiling of 1,024 storage keys, while `eth_getMultiProof` limits requests to 1,024 targets and 1,024 total keys [1]. Operators using simulation endpoints also see changes: `mev_simBundle` compute is bounded, and `eth_simulateV1` now halts when requests drop and assesses cancellation once per simulated block [1].

## CLI Breaking Changes and SDK Refactor

The update enforces breaking operational changes on startup configurations [1]. Nodes will refuse to start if legacy no-op flags—such as `--engine.legacy-state-root`, `--engine.caching-and-prewarming`, and `--engine.parallel-sparse-trie`—remain in configuration files [1]. Unix IPC socket permissions are now validated prior to binding, causing startup failures on platforms that cannot pre-set modes, including macOS [1]. When using `--instance N` without a specified socket path, the Engine API IPC socket defaults to `/tmp/reth_engine_api.ipc-N`, requiring operators whose consensus clients rely on previous paths to define `--auth-ipc.path` [1].

For developers integrating the Reth SDK, the release migrates Ethereum block execution into `evm2::block`, turning Reth's internal executors into thin wrappers around `evm2` types [1]. The update follows previous infrastructure hardening cycles, such as the [Reth 2.10.0 release](https://basisdesk.news/news/reth-releases-version-2-10-0), and implements performance updates including parallelized EIP-7702 authorization recovery and replacing `schnellru` caches with `reth-lru` [1].

## Sources

1. [Reth v2.11.0](https://github.com/paradigmxyz/reth/releases/tag/v2.11.0) — Reth releases, 2026-11-11

---
Basis Desk Newsroom · AI-generated, source-verified · https://basisdesk.news/about/how-we-use-ai