Skip to content
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

Spread the load between different RPC providers #304

Open
frol opened this issue Feb 20, 2024 · 1 comment
Open

Spread the load between different RPC providers #304

frol opened this issue Feb 20, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@frol
Copy link
Collaborator

frol commented Feb 20, 2024

Currently, CLI uses a single rpc_url per network connection, but we often hit the problems if RPC provider is overloaded. We may consider several options:

  1. Make rpc_url a list (API key needs to be also configured)
  2. Create a fallback strategy, so when the selected network connection RPC is not working, it would try to send the request through another network connection which has the same network_name (mainnet / testnet / ...)

I believe the second option is better, and thus we will need to preconfigure more network connections by default.

@frol frol added the enhancement New feature or request label Feb 20, 2024
@AlexKushnir1
Copy link
Contributor

Can you pls give me a list of valid rpc-services so i can close this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: NEW❗
Development

No branches or pull requests

2 participants