The newer PersistentConnectionProvider implementations, mostly the WebSocketProvider, seem to be getting a lot of use and a lot of good feedback is coming back from users, whether through issues or Discord. It's time to start thinking about some good UX abstractions that can help facilitate subscription management, re-connection logic, and anything else that might make sense to bake into the library.

Some ideas that have been brewing:

• Configurable re-connection logic. This should be able to be turned off and also configured for different exceptions, etc. Re-subscribe to existing subscriptions with new subscription ids when this re-connection is triggered.
• (Subscription management implementation #3554) Handling subscriptions via specific callbacks. Could this be an argument to w3.eth.subscribe method perhaps? Likely managed within a SubscriptionManager class strapped to persistent connection providers.

If you have UX improvements, pain points, or any comments on anything discussed in this issue, please feel free to join the discussion below!