You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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?
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.
Activity
tabaktoni commentedon Dec 14, 2023
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 commentedon Dec 14, 2023
Ethers.js has a rather complex logic regarding this IIRC, we could try and go with something simple
Cybermaxi7 commentedon Mar 13, 2025
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.