Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation:
Fixes an issue where rounding in
slashingFactor
calculations can result in a factor of zero, causing stakers to lose all their withdrawable shares under specific edge cases. This can be exploited by malicious operators through intentional self-slashing and small beacon chain penalties. (EGSL-16)Modifications:
slashingFactor
whenoperatorMaxMagnitude
andbeaconChainSlashingFactor
are extremely small.Implemented frontend warnings for stakers when delegating to operators with extremely lowmaxMagnitude
, helping mitigate potential exploits.Result:
Preventative warnings to stakers to avoid delegation to potentially malicious or risky operators.