Relay throws an "IP rate limit exceeded ..." exception, regardless of whether it's an IP-related rate issue

[Neurone]

Description

The relay throws an exception to the client saying “IP rate limit exceeded …” regardless of whether it's a real IP rate limit applied by the relay or an RPS rate limit applied by the MN. I.e:

{"error":{"code":-32605,"message":"[Request ID: 6dcd2378-defa-47d2-8de6-74c3bdfc6600] IP Rate limit exceeded on Rate limit exceeded on eth_call"},"jsonrpc":"2.0","id":72}'

While providers can apply IP rate limits on their gateway when serving an MN (i.e. this is what the public mirror node service does), the mirror node itself does not apply limits but for the mirror-node-web3 container.

In that case, a throttling based on the RPS is applied, regardless of the client's IP. The setting can be changed using the hedera.mirror.web3.throttle.requestsPerSecond parameter (default: 500).

Steps to reproduce

1. Disable the rate limits in the JSON-RPC relay setting RATE_LIMIT_DISABLED=true
2. Hit the /api/v1/contracts/call relay endpoint multiple times per second
3. See the "IP Rate limit exceeded on Rate limit exceeded on eth_call" error appears.

Additional context

No response

Hedera network

other

Version

v0.61.0

Operating system

None