RemoveMyPool is undone by the announceAvailability of the hbbft node client. #139
Labels
waiting-for-dmd-node
Contract side is done, but diamond-node requires an implementation for this feature as well.
Not verified yet, if it is really the case - but according to my current understanding it is...
Validators can call
removeMyPool
in order to plan a maintenance and skip being available for the next epoch.... But our Nodes, they are so smart and see: "Hey, i am at the Head of the Blockchain, and my mining Address is associated with a pool that has enough stake, and it is marked as "unavailable and active" - but i am here, so i
announceAvailability
.The text was updated successfully, but these errors were encountered: