forked from InjectiveLabs/peggo
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Support Multiple Ethereum RPCs #196
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Currently, we support providing an Ethereum RPC to Peggo's
orchestrator
command via--eth-rpc
. However, RPCs can fail and many operators are using and/or running multiple RPCs for redundancy and liveness purposes.Problem Definition
In order to switch to a new ETH RPC if one goes down or is not available, the operator would have to update the
--eth-rpc
flag value and restartPeggo
making this a tedious and manual process. If the operator has no alerting or monitoring in place, it could even be too late.Proposal
Peggo should support taking a list of ETH RPCs instead of a single one,
--eth-rpcs=addr1,addr2,...
. Peggo will connect to the first one. If any request ever fails, or at least fails X number of times, it'll automatically try to connect to and use the next RPC, in a round-robin fashion.For Admin Use
The text was updated successfully, but these errors were encountered: