fix: update slasher field immediately when instantEffectBlock=true #1687
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:
Address L-01 finding from the Certora audit: "Instant slasher setting leaves stale slasher field in storage". When
_updateSlasher()is called withinstantEffectBlock=true, onlypendingSlasherandeffectBlockare updated, leaving theslasherfield stale (address(0) for new operator sets). WhilegetSlasher()returns correct values, raw storage is inconsistent.Modifications:
_updateSlasher()inAllocationManager.solto setparams.slasher = slasherwheninstantEffectBlock=trueSlasherParamsstruct inIAllocationManager.solto document storage behaviorgetSlasherParams()helper toAllocationManagerHarness.solfor testing raw storagedocs/core/AllocationManager.mdResult:
slasherandpendingSlasherfields are set immediately wheninstantEffectBlock=truegetSlasher()return value🤖 Generated with Claude Code