Skip to content

Add support for multiple RPC providers #872

@jereldlimjy

Description

@jereldlimjy

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

Activity

tabaktoni

tabaktoni commented on Dec 14, 2023

@tabaktoni
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

ivpavici commented on Dec 14, 2023

@ivpavici
Collaborator

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

linked a pull request that will close this issue on Feb 23, 2024
Cybermaxi7

Cybermaxi7 commented on Mar 13, 2025

@Cybermaxi7

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      Participants

      @tabaktoni@ivpavici@jereldlimjy@Cybermaxi7

      Issue actions

        Add support for multiple RPC providers · Issue #872 · starknet-io/starknet.js