hedera-json-rpc-relay
hedera-json-rpc-relay copied to clipboard
hashgraph
Implementation of Ethereum JSON-RPC APIs for Hedera
This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade pnpm from 8.15.5 to 8.15.7. :information_source: Keep your dependencies up-to-date....
This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @hashgraph/sdk from 2.43.0 to 2.44.0. :information_source: Keep your dependencies up-to-date....
**Description**: - adds support for batch request feature to WS server - adds WS neccessary config variables to configurations.md - added two new predefined errors, WS_BATCH_REQUESTS_DISABLED and WS_BATCH_REQUESTS_AMOUNT_MAX_EXCEEDED, to JsonRpcError...
### Problem Currently, the WS_BATCH_REQUESTS_ENABLED configuration defaults to true, allowing the WS server to accept batch requests. However, this functionality is currently being monitored, and adjustments may be required to...
### Problem The relay has the recommended and default values hardcoded within the app. however we are overriding these with the one with the chart values, what is forcing devs...
Populates null values in transactions. **Related issue(s)**: Fixes #2451
Added toBlock and fromBlock parameters Fixes #2464
### Description Expected: web3_clientVersion to return the same value as HTTP endpoint Current: returns null value ### Steps to reproduce { "jsonrpc":"2.0", "method":"web3_clientVersion", "params":[], "id":1 } {"result":null,"jsonrpc":"2.0","id":null} ### Additional context...
### Problem Currently, batch request feature lack of metrics and is not rate limited. ### Solution Improve metrics and add rate limit for the batch request feature in WS server...
### Description Expected: WS logs subscription should accept the same params as HTTP that works Current: Errors out with "error": { "code": -32602, "name": "Invalid parameter", "message": "Invalid parameter 'fromBlock'...