Rate limiting handling #2
Description
If the rpc client ever gets rate limited, the Ellipsis client should have a relatively robust way to handle the error. This involves both clearly notifying the user that there are issues with the connection as well has having some sort of retry management logic
One thing that could help is managing a number of different connections and cycling through those connections (based on some rotation strategy) to manage this. Ultimately, the goal is for the network communication step to be completely abstracted away from the user.
Another criteria is to keep the client as lightweight as possible