Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RemoveMyPool is undone by the announceAvailability of the hbbft node client. #139

Open
SurfingNerd opened this issue Oct 7, 2022 · 1 comment
Labels
waiting-for-dmd-node Contract side is done, but diamond-node requires an implementation for this feature as well.

Comments

@SurfingNerd
Copy link
Collaborator

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.

@SurfingNerd
Copy link
Collaborator Author

Pools that are planned to get removed are in _poolsToBeRemoved

@SurfingNerd SurfingNerd added the waiting-for-dmd-node Contract side is done, but diamond-node requires an implementation for this feature as well. label Dec 14, 2022
@SurfingNerd SurfingNerd moved this to Todo in Alpha4 Apr 25, 2024
@SurfingNerd SurfingNerd removed this from Alpha4 Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
waiting-for-dmd-node Contract side is done, but diamond-node requires an implementation for this feature as well.
Projects
Status: No status
Development

No branches or pull requests

1 participant