Implement JSON-RPC batch support
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
ETHEREUM JSON RPC endpoints arguably support batching calls. So we should allow batching via the transport module
- https://web3js.readthedocs.io/en/v1.2.11/web3-eth.html#batchrequest
- https://sajya.github.io/docs/batch/
via alchemy docs:
https://docs.alchemy.com/alchemy/documentation/batch-requests
Batch requests are single HTTP requests that contain multiple API calls nested within it.
Generally speaking, Alchemy does not recommend using batch requests as they can be less reliable compared to individual API calls.
Alchemy does not recommend using batch requests for any methods. These requests tend to be less performant than sending them individually, so if you’re trying to optimize speed, this might not be the best option.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the transport module and the linked web3.js, Sajya, and Alchemy batch-request documentation. Determine how a single HTTP request should carry multiple JSON-RPC calls and how responses should be represented; done means the transport supports the requested batch behavior and its reliability and performance constraints are understood.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100