[dfuse-bot]

Merges Base's reth fork base-v2.5.2.11, the reth version upstream Base v1.5.4 pins, into release/base-2.x. Tag base-v2.5.2.11-fh3.1 on the merge commit once merged; streamingfast/base#41 (v1.5.4-fh3.1) pins that tag.

The merge had no conflicts. The range (base-v2.5.2.8..base-v2.5.2.11) only touches RPC (eth_getLogs blocking IO permits and windowed range scans, cancelled blocking tasks), the trie iterator seek boundary, and snapshot download presets. No Firehose code changed and the block model is unchanged, so the tag keeps fh3.1.

Please merge with a merge commit (not squash or rebase): the streamingfast/base PR's Cargo.lock records this branch's head commit, which stays reachable from the tag only that way.

CHANGELOG

## base-v2.5.2.11-fh3.1

### Changed

- Rebase on Base's reth fork at `base-v2.5.2.11`, the reth version pinned by Base `v1.5.4`. It
  backports the `eth_getLogs` range scan fixes (blocking IO permits, window by window scans), a
  trie iterator seek fix, and RocksDB indices for the full snapshot download preset. Firehose code
  and the block model are unchanged.

Tests

Command	Status	Notes
cargo test -p reth-firehose -p reth-firehose-tests	PASSED	35 + 2 tests
cargo test -p reth-engine-tree --test firehose_live_tracing --test firehose_live_tracing_bal	PASSED	2 tests
cargo test -p reth-trie --lib node_iter	PASSED	2 tests (the changed iterator)

The Base node built against this branch also passed its Firehose tests and the Battlefield op-reth-devnet suite; see the streamingfast/base PR.

Firehose bug patterns

1. Serial order: no change to execution, the payload processor or the engine tree. None found.
2. Emit after accept: the trie seek fix is in state root computation, which still runs before mark_verified() prints the block. None found.
3. Activations: no hardfork or chain spec change in the range. None found.
4. Fields: no change to consensus types or the mapper. None found.