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

Create error transaction when user tries to unstake for the only active node #1215

Closed
Daksh14 opened this issue Dec 19, 2023 · 1 comment
Closed
Assignees
Labels
priority:minor Low priority issues

Comments

@Daksh14
Copy link
Contributor

Daksh14 commented Dec 19, 2023

Right now we allow unstaking from the default address and if you try to stake again no blocks are produced

Throw an error tx if its the only active node in the cluster and you try to unstake

@autholykos autholykos added the priority:minor Low priority issues label Dec 20, 2023
@autholykos
Copy link
Member

It's fine to record this issue, but it is definitely not a priority right now. This is a situation that cannot happen irl because there will always be at least one Provisioner that will keep the Dusk network running. Changing the status to minor

herr-seppia added a commit that referenced this issue Dec 20, 2023
@herr-seppia herr-seppia closed this as not planned Won't fix, can't repro, duplicate, stale Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority:minor Low priority issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants