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

[TASK] Slashing and governance #717

Open
Tracked by #783
drewstone opened this issue Jul 30, 2024 · 0 comments
Open
Tracked by #783

[TASK] Slashing and governance #717

drewstone opened this issue Jul 30, 2024 · 0 comments

Comments

@drewstone
Copy link
Contributor

Overview

We let Blueprint developers define slashing, but we should also retain control to veto and cancel slashes at the governance/network level. This is useful to prevent truly malicious behavior from happening as well as to ensure that there is a process for forgiving slashing conditions in the event the network wants to (early launch of the product, disputes have been resolved, payments for downtime organized, etc. whatever it may be).

The logic should resemble similarly to validator slashing, where the governance system can propose to cancel it within a window or alternate time tracking mechanism.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant