hello. a new key was updated. but I have a question.
cd $NODE_HOME
cardano-cli query kes-period-info
–${NODE_CONFIG}
–op-cert-file node.cert
the number of qKesOnDiskOperationalCertificateNumber is 7… qKesNodeState----- number is 4.
Before updating, qKesNodeState number was 4…
Problem???
Can u share the ticker?
The value of the qKesNodeStateOperationalCertificateNumber key indicates the current counter value for your stake pool registered by the blockchain protocol. The value of the qKesOnDiskOperationalCertificateNumber key indicates the counter value of the current operational certificate that your stake pool uses.
For a new operational certificate, the counter value must be exactly one (1) greater than the current value of the qKesNodeStateOperationalCertificateNumber key.
If qKesOnDiskOperationalCertificateNumber is more than one (1) greater than qKesNodeStateOperationalCertificateNumber then the operational certificate is invalid. Your stake pool cannot mint blocks using an invalid operational certificate.
If ur last OP used was 4 to mint blocks u should have now qKesOnDiskOperationalCertificateNumber 5
my pool`s ticker is yabak
according to adapools.org last op number used is 4… set the incremental number to 5 and rotate the kes again
U must have
“qKesNodeStateOperationalCertificateNumber”: 4,
“qKesOnDiskOperationalCertificateNumber”: 5,
you mean the number should be 5… then counter -value should be 5+1 ???
5+ 1 = 6
must be 4 (last one used) + 1 = 5 (just set it to 5)
The incremental number 5 means… next certificate will be 5
I don`t understand… I used 4+1… then, 4, 7 are shown. ← problem.
I should rotate it again using 5+1 ???
:)) why 6 when its a must to use 5
Set the incremental number from cold.counter/node.counter to 5, save the file and rotate the KES again… if u are using cntools just go to pool - rotate and set 5 when it will ask for the incremental number
Cheers,
cd $HOME/cold-keys
cardano-cli node new-counter
–cold-verification-key-file $HOME/cold-keys/node.vkey
–counter-value $(( 4 + 1 ))
–operational-certificate-issue-counter-file node.counter
after this command check with cat node.counter if the incremental number was updated to 5 inside the file and after rotate should be 6
Ok… thanks… Now
“qKesNodeStateOperationalCertificateNumber”: 4,
“qKesOnDiskOperationalCertificateNumber”: 5,
Now is correct
many thanks…
I had to write “–counter-value $(( 4 + 1 ))” I wrote –counter-value $(( 5 )), therefore the problem happened.
U can modify manually inside the file (nano node.counter) and skip this step
Hello. I have a question… When node cert file was created yesterday, the created date was April 9th in my OS. Is it ok?
should be also updated if u issued a new certification file (node.cert)
My air-gapp computer`s date was April 9th when the new certification was issued.
Is it ok?
If not OK, the key should be rotated again… 
U made a block so I guess all good 
thanks. Alex. But it seems Blocks are minted less.