Hello all,
my little pool sadly failed to mint its firstblock. The log says:
Invalid block 6…6 at slot 25838705: ExtValidationErrorHeader (HeaderProtocolError (HardForkValidationErrFromEra S (S (S (Z (WrapValidationErr {unwrapValidationErr = ChainTransitionError [OverlayFailure (VRFKeyWrongVRFKey (KeyHash “3c3784c2477fbb805d60661cbf4fa472fdd6d3cface961cb26e31733”) “e88ba01c65b1038d1a7f0ed433b691c738d304770fcb4d17c43155384cbd3696” “4ee457ab506a77371bcdfd26da3546f409b940b2a4587447ce61b5e346f9f63e”)]}))))))
While rotating my KES keys couple of day back I accidentally overwritten the vrf key pair which is probably the culprit. At the moment I am not sure how to proceed to get things right.
Any advice will be very appreciated.
VRF stands for Verifiable Random Function. It is the key essential to the lottery that your node performs. It is also an input to the pool’s registration certificate. I’d think, if you now sign a block with a different vrf.skey as recorded in the pool’s registration certificate - that this would be an error condition.
Don’t you have a backup of the original vrf.* key pair? If not, you might have invalidated the pool registration because you may no longer be able to sign the blocks that your pool mints.
I also don’t think that there is a way to resurrect those keys.
Please don’t take this as the ultimate truth. You may want to get confirmation from the core team.
If you have a backup, it should be sufficient to restart the block producer node with the correct keys+cert
Thank you for your answer. The new vrf.skey on my bp does not match the vrf.vkey that signed the pool registration on the air-gapped.
Since I need to modify metadata.json I’ll reregister using the old vrf key on both places.