Skip to content

docs: document eth_getLogs query limits #383

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
huklaa wants to merge 4 commits into
base: main
Choose a base branch
from
+21 −0
Open

docs: document eth_getLogs query limits #383

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
5b0847c
docs: document inherited eth_getLogs limits
huklaa Sep 22, 2026
e7d4ae3
docs: explain node and gateway RPC limits
huklaa Sep 22, 2026
7192e86
docs: note public eth_getLogs gateway limit
huklaa Sep 22, 2026
bdb38be
docs: note public eth_getLogs gateway limit
huklaa Sep 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions crates/node/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -96,6 +96,18 @@ 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 <N>` limits the block range scanned by one filter (default: `100000`).
- `--rpc.max-logs-per-response <N>` limits the number of logs returned by one response (default: `20000`).

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

In addition to standard Reth flags, `arc-node-execution` provides the following custom flags:
Expand Down
9 changes: 9 additions & 0 deletions docs/running-an-arc-node.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -196,6 +196,15 @@ 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. 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

After starting the [execution layer](#start-execution-layer), in a different terminal, start the consensus layer:
Expand Down
Loading