Slashing should be able to affect up to 100% of the assets on a given service instance. The blueprint developer should be able to define what percentage of tokens to slash for a given malicious or non-ideal behavior. If tokens are slashed, they should be moved into a "container" that allows governance to decide where to send them or what to do with them (veto the slashing condition). This connects with the slashing queue task that we have defined previously #775.
The options for the queue outcomes are
Send funds to treasury (default if no action taken)
Overview
Slashing should be able to affect up to 100% of the assets on a given service instance. The blueprint developer should be able to define what percentage of tokens to slash for a given malicious or non-ideal behavior. If tokens are slashed, they should be moved into a "container" that allows governance to decide where to send them or what to do with them (veto the slashing condition). This connects with the slashing queue task that we have defined previously #775.
The options for the queue outcomes are