From 884596a3dd7ec90c5ece7b828b50b8d498e626ac Mon Sep 17 00:00:00 2001 From: Hukla <129692708+huklaa@users.noreply.github.com> Date: Sat, 12 Sep 2026 00:05:38 +0300 Subject: [PATCH 1/4] docs: document inherited eth_getLogs limits --- crates/node/README.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/crates/node/README.md b/crates/node/README.md index a220e585..ef2b107a 100644 --- a/crates/node/README.md +++ b/crates/node/README.md @@ -96,6 +96,14 @@ For a complete list of available flags, see the [Reth CLI reference](https://ret arc-node-execution node --help ``` +Two inherited Reth flags control the size of `eth_getLogs` queries: + +- `--rpc.max-blocks-per-filter ` limits the block range scanned by one filter (default: `100000`). +- `--rpc.max-logs-per-response ` limits the number of logs returned by one response (default: `20000`). + +These limits apply to a node's own RPC server. A public gateway or reverse proxy +may enforce stricter limits independently. + #### Custom flags In addition to standard Reth flags, `arc-node-execution` provides the following custom flags: From 26aee9a981ab5de8cc018615e6c3914a2becbc33 Mon Sep 17 00:00:00 2001 From: Hukla <129692708+huklaa@users.noreply.github.com> Date: Sat, 12 Sep 2026 00:05:40 +0300 Subject: [PATCH 2/4] docs: explain node and gateway RPC limits --- docs/running-an-arc-node.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/running-an-arc-node.md b/docs/running-an-arc-node.md index df392c5e..e3f89e2d 100644 --- a/docs/running-an-arc-node.md +++ b/docs/running-an-arc-node.md @@ -196,6 +196,12 @@ and `--rpc.max-subscriptions-per-connection` (default `32`) if clients see `MaxConnections` or `TooManySubscriptions` errors. The defaults bound WebSocket log-fanout memory growth and should only be raised, not lowered. +For `eth_getLogs`, `--rpc.max-blocks-per-filter` limits the block range scanned +by one filter (default `100000`), while `--rpc.max-logs-per-response` limits the +number of logs returned by one response (default `20000`). These inherited Reth +limits apply to the node itself; a public gateway or reverse proxy may enforce +stricter limits independently. + ### Start consensus layer After starting the [execution layer](#start-execution-layer), in a different terminal, start the consensus layer: From 7fa05e06a6e7f68b16a8aebacc14bc1212a7134c Mon Sep 17 00:00:00 2001 From: Hukla <129692708+huklaa@users.noreply.github.com> Date: Sun, 20 Sep 2026 02:58:07 +0300 Subject: [PATCH 3/4] docs: note public eth_getLogs gateway limit --- crates/node/README.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/crates/node/README.md b/crates/node/README.md index ef2b107a..489c3571 100644 --- a/crates/node/README.md +++ b/crates/node/README.md @@ -101,8 +101,12 @@ Two inherited Reth flags control the size of `eth_getLogs` queries: - `--rpc.max-blocks-per-filter ` limits the block range scanned by one filter (default: `100000`). - `--rpc.max-logs-per-response ` limits the number of logs returned by one response (default: `20000`). -These limits apply to a node's own RPC server. A public gateway or reverse proxy -may enforce stricter limits independently. +These limits apply to a node's own RPC server. The Arc public mainnet RPC currently +rejects `eth_getLogs` ranges above 10,000 blocks with JSON-RPC error `-32600` +(`Query exceeds max block range of 10000`), so applications using the public +gateway should paginate below that limit even though self-hosted nodes default +to 100,000 blocks. Other gateways or reverse proxies may enforce different +stricter limits independently. #### Custom flags From d2f55c8ea60db9c5e4e39883b790125fe289834f Mon Sep 17 00:00:00 2001 From: Hukla <129692708+huklaa@users.noreply.github.com> Date: Sun, 20 Sep 2026 02:58:09 +0300 Subject: [PATCH 4/4] docs: note public eth_getLogs gateway limit --- docs/running-an-arc-node.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/running-an-arc-node.md b/docs/running-an-arc-node.md index e3f89e2d..faa0936d 100644 --- a/docs/running-an-arc-node.md +++ b/docs/running-an-arc-node.md @@ -199,8 +199,11 @@ log-fanout memory growth and should only be raised, not lowered. For `eth_getLogs`, `--rpc.max-blocks-per-filter` limits the block range scanned by one filter (default `100000`), while `--rpc.max-logs-per-response` limits the number of logs returned by one response (default `20000`). These inherited Reth -limits apply to the node itself; a public gateway or reverse proxy may enforce -stricter limits independently. +limits apply to the node itself. The Arc public mainnet RPC currently rejects +ranges above 10,000 blocks with JSON-RPC error `-32600` +(`Query exceeds max block range of 10000`), so clients using the public gateway +should paginate below that limit. Other gateways or reverse proxies may enforce +different stricter limits independently. ### Start consensus layer