Skip to content

Add support for multiple RPC providers #872

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jereldlimjy opened this issue Dec 6, 2023 · 3 comments · May be fixed by #980
Open

Add support for multiple RPC providers #872

jereldlimjy opened this issue Dec 6, 2023 · 3 comments · May be fixed by #980
Labels
Type: feature New feature or request

Comments

@jereldlimjy
Copy link

Currently supports a single choice of RPC provider. To add support for failing over from a primary to a secondary RPC provider, based on an error response/no response from the primary

@jereldlimjy jereldlimjy added the Type: feature New feature or request label Dec 6, 2023
@tabaktoni tabaktoni added the OnlyDust Open for OnlyDust contributors label Dec 14, 2023
@tabaktoni
Copy link
Member

One could do this localy by creating multiple Providers but we can create it also in the lib./
I'm marking this as only dust, his should be simple to do. we could call it fallbackRpcProvider or it could be implemented inside existing rpc provider?

@ivpavici
Copy link
Collaborator

Ethers.js has a rather complex logic regarding this IIRC, we could try and go with something simple

@Cybermaxi7
Copy link

I'm interested in working on this issue to add support for automatic failover from a primary to a secondary RPC provider. I have experience handling API integrations, error detection, and implementing fallback strategies in web applications.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: feature New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants