You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: