You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just a note - we would not want to rely on CLI or storage - but look at runtime (in line with all metrics gLV shows), we already had an item to use Koios query layer to check for latest OpCert metrics for given pool which would be refreshed at:
KES time interval change;
Startup of gLiveView;
PID change of node
Also, we would need to note that KOIOS_MODE being set to N (or test_koios failing) will disable this check, the test_koios should only be called once at gLiveView startup. Worth noting that CNTools users (who allow connection to koios) already had this check , as it was taken care of with node version update as well.
This is in line with Catalyst proposal from Koios to further integrate between query layer and SPO tools
Describe
LiveView should check the certificate counter.
If the OnDisk counter differs from the OnChain counter by more than 1, the certificate will be invalid.
https://developers.cardano.org/docs/stake-pool-course/assignments/kes_period/#how-do-i-know-if-i-have-issued-an-invalid-operational-certificate
The purpose is to guard against this scenario IntersectMBO/cardano-node#4114
The text was updated successfully, but these errors were encountered: