Unintended Slashing

Given most slashing conditions are cryptographically verifiable, and the vast majority of slashing on the system will be provable, there does exist the systemic risk of unintentional slashing, which would require an additional layer of consensus to come to agreement on the outcome of the slashing event. In the earliest stages of Exocore, the risk of unintentional slashing will be highest, as the system needs to mature, as do the AVS building on top of Exocore. An unintended slashing condition can be triggered by something as simple as a bug in the code, or something more complex such as emergent behavior in the system. There are several ways to minimize the risk of unintended slashing, some of which are covered in the next section on risk mitigation (8.2).

Last updated