OpenZeppelin / OpenZeppelin/Robust-Provider
Improve Fallback Logic for Endpoints
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6
- Forks
- 4
- Avg merge
- 15h 52m
- Merged PRs (30d)
- 5
Description
Currently all providers are tried in order when calling regular rpc endpoints. This means that even if a provider is down (e.g the primary provider) we will still try to call it then failover to the next provider (which might also be down). This can cause significant lag / degradation in performance as you need to cycle through known dead providers before getting to the one that works.
Ideally there's global state tracking of which provider is working across rpc calls. This is similar logic to the robust subscription.
We should share the same logic between the robust subscription and regular calls.
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 comparing the existing robust subscription logic with the regular RPC endpoint call path. Trace how providers are tried across calls and identify what shared provider-health state would need to cover both paths. Done means regular calls avoid repeatedly trying known-dead providers while preserving failover to a working provider.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100