Skip to content
Basis Desk

New: Basis Desk Verify for Chrome & Firefox — fact-check crypto news on any page, free.Get the extension →

Ethereum & L2s · 1 min read

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.

Editorial oversight: Julian Mercer, Chief Editor
Neutral

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 releases: Reth v2.11.0

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.

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, and implements performance updates including parallelized EIP-7702 authorization recovery and replacing schnellru caches with reth-lru 1.

Sources

  1. [1] Reth v2.11.0 — Reth releases, November 11, 2026

Written by Basis Desk's newsroom system from the primary sources above and machine-verified against them before publication. Market figures marked "at the time of writing" come from live exchange data. Report an error: corrections@basisdesk.news · corrections policy.

Community read
How do you read this story for the assets involved? One vote a day, anonymous.
Be the first to vote

The Daily Brief, in your inbox at 07:00 ET

Five stories, the numbers that moved, what to watch. Three minutes. No hype, no advice, unsubscribe in one click.

Not financial advice. Basis Desk publishes information, not recommendations. Crypto assets are volatile and you can lose what you invest.