The validator client currently crashes if a request is made against a beacon node that goes down.

A common workflow during development is to have the validator client running and then restart an attached beacon node.

This currently raises an `OSError` which is not caught in the client and crashes the entire process.

Ideally the validator client drops requests that cannot be made when the beacon node is unreachable and keeps moving along.