llifezou
commented
8 months ago As a suggestion, I would try and avoid to rely on SSV API for performance monitoring.
Yes, very much agree.
for things like validator performance, I would encourage using something like rated.network or beaconcha.in
This is an improved solution, but probably not enough. My idea is to not only monitor whether the validator is active, but also monitor whether each operator in a cluster is performing its duties correctly (without relying on the SSV API).
My current idea is to develop an SDK (or modify the ssv node), analyze the status in the ssv-node to determine whether the operator is fulfilling its responsibilities; monitor the consensus layer nodes to determine whether the verifier is active; monitor the execution layer nodes to obtain ssv Network events.
Information on a per-operator basis are missing, but for that we can discuss on discord, or try and come up with ideas for a framework SSV can provide
Please allow me to study it. If the idea is correct, I will discuss it with you. Thank you for your help.
As a suggestion, I would try and avoid to rely on SSV API for performance monitoring.
The API is more of an internal-use tool, and the more we iterate on it, the more we have developed the idea that this should only be used to let people know that, for example, a certain address is the owner of a certain cluster, which manages a certain number of validators.
for things like validator performance, I would encourage using something like rated.network or beaconcha.in So the advice is to refactor the tool to lookup the validators of a certain owner, (or operator, up to you), using SSV API, and then use other means to monitor the performances.
Information on a per-operator basis are missing, but for that we can discuss on discord, or try and come up with ideas for a framework SSV can provide