NethermindEth / NethermindEth/Catalyst
Investigate if taiko client supports multiple URLs for the RPC argument
Open
Nobody has claimed this yet.
Node
- Dominant language
- Rust
- Stars
- 44
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Description
Investigate if we can pass multiple RPC endpoints to taiko client, and if the URL list is treated as a round robin list.
Acceptance criteria
Ensure that if an RPC is over quota, that the taiko client switches to the next RPC endpoint automatically
Documentation link(s)
Contributor guide
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 locating the Taiko client code that parses the RPC argument and sends requests to an endpoint. Check whether multiple URLs and round-robin selection are already supported, then trace how quota errors are handled. Done means multiple endpoints can be configured and the client automatically tries the next one when an RPC is over quota.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100