Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
8 changes: 8 additions & 0 deletions crates/node/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 <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. 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:
Expand Down
6 changes: 6 additions & 0 deletions docs/running-an-arc-node.md
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down