Use custom provider with multiple RPC's#2260
Merged
pablomendezroyo merged 15 commits intodevelopfrom Sep 17, 2025
Merged
Conversation
3alpha
reviewed
Sep 16, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implement a custom provider with multiple RPC's with a priority defined by the order of the URL item in the array. The main purpose of this implementation is to fetch the RPC and retry on error with the next RPC in the array. Also store the healthy status of the latest RPC queried as well as the timestamp, so the unhealthy RPC's are only re-queried if the timestamp has passed.
Todo: allow to define optional beaconchain URL associated with an execution URL to check if its synced or not