hello to all, i have a block producer node that i would like to retire. i forgot to rotate the KES so it is expired. i tried to rotate it afterwards but the expiration date remains the previous one. i used this procedure that previously always worked:
Correct me if I’m wrong but isn’t generating pools and retiring pools done on the blockchain? Why do you need a working producer node? (I never retired a pool myself)
Afaik you simply need a node in sync to submit your retirement ceritificate to. For this you wouldn’t require an operating certificate. I’m on thin ice here
hi hanswurst thanks for your reply.
In fact, that’s what I’d like to know. I don’t need the node to be fully working. more than anything, I need to know if I can retire it without making mistakes and thus losing the pool deposit.
Check that you are using the same names for your corresponding files or change as needed.
Note to future users: You need to change the ‘444’ value for --kes-period to the value you calculated in the steps above.
Copy the following files to block producer and restart
kes.skey
kes.vkey
node.cert
And while you are at it, chmod them to 0400 to make them read-only as a good standard practice for important files like these that shouldn’t change during normal operations.
so its possible to retire a pool with expired kes keys?
im trying to do that right now, i’ve spent a week trying to get the kes keys restored but if i can just retire the pool without it that it would amazing! the nodes are all synced just the bp kes keys is expired
You need the cold key to sign the deregistration certificate transaction and you need the stake key to collect the returned deposits 1 to 2 epochs later. That’s all.