4

With reference to my previous question regarding inconsistent reading of KES validity given by cardano-node and gLiveView, is there any way I could objectively verify KES validity without waiting for the next block?

1 Answer 1

4

Things you can verify:

  • Current opcert counter is higher than previous counter on chain in a block created by your pool (you can use dbsync or query a public instance) - you already saw in your previous thread that expected OCert for your node was 6).
  • Expiry date of KES (can query EKG or also just check gLiveView).
  • Make sure your cert was derived using kes from your cold key using which pool was created.

Once each of above is verified, it's simply a matter of waiting for your next block to get the proof/assurance. The above are pretty much the only checks you can perform.

2
  • What if you haven't done any blocks yet? Mine is currently up to 9, no blocks done, and the cert instantly expires.
    – Cyberience
    Mar 31 at 8:24
  • 1
    @Cyberience - "instantly expires" => That suggests you're likely not using right start period for KES (assuming you're verifying it correctly using right files and post node restart)
    – RdLrT
    Apr 1 at 3:36

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.