Bor v2.6.5 is a quality-of-life release focused on improving RPC node stability and fixing a configuration issue.

New RPC Range Limiting

This update introduces a new --rpc.rangelimit flag. Node operators can now set a maximum block range for log queries to protect their nodes from expensive, wide-range requests that can cause performance issues.

This limit is enforced on both the standard eth_getLogs and the Bor-specific bor_getLogs endpoints.

By default, the limit is 0 (unlimited), so node operators must opt-in to enable this protection.

Usage:

To limit log queries to a range of 1000 blocks via the command line:
bor --rpc.rangelimit 1000

Alternatively, you can set this in your HCL/TOML config file:
[jsonrpc]
rangelimit = 1000

Configuration Fix

A bug has been fixed where filter settings such as LogCacheSize, LogQueryLimit, and the new RangeLimit were not being correctly applied to the bor_getLogs API path. With this release, these configurations will now be properly recognized.