Skip to content
This repository was archived by the owner on Apr 25, 2026. It is now read-only.
This repository was archived by the owner on Apr 25, 2026. It is now read-only.

[TASK] Slashing and governance #717

Description

@drewstone

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions