Issue To Be Solved

Currently, the gateway is configured with a single AN host for the current network. If the connection to that host is broken (likely due to the AN rebooting), the requester engine returns an error causing the node to crash. If the upstream AN is down for an extended period of time, the gateway requires the operator to manually update the config.

(Optional): Suggest A Solution

Update the client logic to gracefully reconnect to the upstream AN when disconnected. Also allow the operator to provide an arbitrarily long list of alternate nodes that are tried in order when the first node is not available.