Node Health
Last updated
Last updated
To serve as a validator, both CL and EL need to be up to date with the network. There are a couple of techniques of how to check that.
All this healthchecks data should lead to a of your choice.
Most of the nodes have exposed healthchecks APIs, that return HTTP 5xx if the node is not syncing properly, and HTTP 200 OK if everything is okay. That is the most simple and most basic version of the healthcheck.
One more strategy is based on the timestamp of the latest block.
For EL that is a response to .
It has a field called timestamp. By knowing the timestamp of the block and the block production rate (1 block per 12 seconds), it is possible to see how "old" is the current block of the node.
Since sometimes the block proposals could be missed, it doesn't make sense to keep this threshold too tight, but if it is > 5 minutes old, it makes sense to mark the node as "unhealthy" and notify your .
Finally, the case when the blocks are being synced, but you are on the wrong fork. Detection of that could happen on the EL very easily, by using the block hash of returned from .
You can compare these hashes across the nodes and also across the external sources of truth.