Bor v2.6.4 is now available. This is a minor release focused on enhancing RPC node stability and performance.

The key change is the introduction of a new command-line flag: --rpc.rangelimit.
This flag allows node operators to set a maximum block range for log queries, protecting the node from expensive and resource-intensive requests that can cause slowdowns.

The limit is enforced on both the eth_getLogs and the Bor-specific bor_getLogs RPC methods. The default value is 0, which means the range limit is disabled by default.

Usage Example:
To reject any log queries spanning more than 1000 blocks, start your node with:

bor --rpc.rangelimit 1000

Additionally, this release includes a fix ensuring that filter configurations (such as LogCacheSize, LogQueryLimit, and the new RangeLimit) are now correctly applied to the bor_getLogs endpoint, which was previously not the case.