M-04 MitigationConfirmed

[c4-bot-8]

Lines of code

Vulnerability details

M-04: Delayed Slashing Window and Lack of Transparency for Pending Slashes Could Lead to Loss of Funds

Link to issue

Comments

The original implementation lacked getter functions to check if a vault had pending slashes. As a result, new deposits could unknowingly be made into a vault that was about to be slashed, potentially leading to unexpected loss of funds.

Mitigation

Fix link

The mitigation introduces functionality to track pending slashes and a getter function, allowing users to verify whether a vault has pending slashes before making deposits.

    function isVaultQueuedForSlashing(address vault) public view returns (bool) {
        uint256 count = _self().getSlashingsQueuedForVault(vault);
        return count != 0;
    }

Conclusion

This fix mitigates the potential for loss of funds by allowing users to check if a vault has pending slashing, thereby preventing new deposits from unknowingly entering a vault that is at risk of being slashed.

[c4-judge]

MiloTruck marked the issue as satisfactory

[c4-judge]

MiloTruck marked the issue as confirmed for report