Support Multiple Ethereum RPCs #196
Description
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 restart Peggo 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
- Not duplicate issue
- Appropriate labels applied
- Appropriate contributors tagged
- Contributor assigned/self-assigned