feat: slashing commitments #1645
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nadir-akhtar
reviewed
Oct 2, 2025
ypatil12
changed the base branch from
release/slashing-ux-improvements
to
release-dev/slashing-ux-improvements
ypatil12
force-pushed
the
feat/alm-solution
branch
from
a457081 to
999b54b
Compare
ypatil12
force-pushed
the
release-dev/slashing-ux-improvements
branch
from
bce9cbb to
c572ec5
Compare
ypatil12
force-pushed
the
feat/alm-solution
branch
3 times, most recently
from
4bf458a to
e32292e
Compare
eigenmikem
approved these changes
Oct 28, 2025
ypatil12
force-pushed
the
feat/alm-solution
branch
from
cd75057 to
13ea59b
Compare
nadir-akhtar
approved these changes
Nov 4, 2025
feat: allow migration chore: gap chore: make opSets backwards compatible feat: add operatorSet creation; add tests test: setSlasher feat: add pending slasher introspection + tests test: add slasher tests test: slasher fix: require slasher to be zero address test: upgrade feat: migration script; migration event chore: update strat.sh docs: slashing commitments
fix: lavamoat zeus
Co-authored-by: Nadir Akhtar <[email protected]>
ypatil12
force-pushed
the
feat/alm-solution
branch
from
eb68e6f to
817eacc
Compare
ypatil12
merged commit e0297a4
into
release-dev/slashing-ux-improvements
16 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
We want to solve the following use cases:
PermissionControlleractionsModifications:
The slasher permissions are set and stored in the
AllocationManagerinstead of thePermissionController. The slasher is initially set upon creation of the operatorSet.New functions:
updateSlasher: can set a new slasher on aALLOCATION_CONFIGURATION_DELAYblocks (17.5 days on mainnet)migrateSlasher: migrates the slasher address from thePermissionControllerto theAllocationManager. Can be migrated only once for a given operatorSet. This function will be called after the upgrade for all operatorSets. See the script in the script folder, which will eventually be added to the upgrade script.createOperatorSet: modified to take in a slasher address, which can immediately slash an operatorSet. The old function is still available and will be deprecated in Q2 2026. The old function automatically the slasher to the avs address.Old Functions:
slashOperatoris modified to not use thecheckCanCallmodifierWe have 1.9KB left in the ALM.
Result:
Stronger commitments.