Submitted by peanuts, also found by ctf_sec, imare, and Jeiwan
Wrong slashing calculation may create unfair punishment for operators that accidentally forgot to execute their job.
Docs: If an operator acts maliciously, a percentage of their bonded HLG will get slashed. Misbehavior includes (i) downtime, (ii) double-signing transactions, and (iii) abusing transaction speeds. 50% of the slashed HLG will be rewarded to the next operator to execute the transaction, and the remaining 50% will be burned or returned to the Treasury.
The docs also include a guide for the number of slashes and the percentage of bond slashed. However, in the contract, there is no slashing of percentage fees. Rather, the whole _getBaseBondAmount() fee is slashed from the job.operator instead.
Documentation states that only a portion should be slashed and the number of slashes should be noted down.
Implement the correct percentage of slashing and include a mapping to note down the number of slashes that an operator has.
alexanderattar (Holograph) commented:
alexanderattar (Holograph) resolved and commented:
