Coincashew users - KES rotation - change in guide?

Staking & Delegation Operate a Stake Pool
1

Hi guys, just resurrecting my old topic for a new question.

I’m still using the coincashew guide for my stake pool and haven’t had any issues.

I notice the guide now includes a step to manually increment the node.counter number,

Each time you generate a new operational certificate, you must increment the value of Next certificate issue number for the description key in the node.counter JSON file on your air-gapped, offline computer. To edit the node.counter file, use a text editor.

But I have never manually increased the counter. It happens each time I generate a new node.cert automatically. Is this guide incorrect now?

Thoughts?

2

if your next increment counter is fine (should be > than the OpCert used last time adapools.org → blocks → OpCertC) then you don’t need to increment it manually.
you will need to manually modify only if u are using and old backup for example…

Cheers,

3

yeah, that’s what I thought. The guide is a bit a misleading for that now. I’ll see if I can get it updated for clarity,

5

Counter is unique per pool but u can’t run 2 pools on same machine… I mean it is hard to do it

1 Like
6

By the way, this topic is out of date now. Kes key counter values must be exactly +1 of the last kes key that minted a block. Not just higher.

1 Like