-
Notifications
You must be signed in to change notification settings - Fork 334
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: prevent beacon chain allocs #883
feat: prevent beacon chain allocs #883
Conversation
- opsets CAN include `beaconChainETHStrategy`, the just cannot allocate or slash it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add a sanity test?
|
3 similar comments
|
|
|
cheats.prank(defaultAVS); | ||
allocationManager.slashOperator(SlashingParams(defaultOperator, defaultOperatorSet.id, WAD, "")); | ||
|
||
// assertEq( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we slash this operator (mag < WAD) and then assert that the magnitude is still WAD
|
Closing this for now since we decided to go for freezing BC ETH |
Changes
require(strategies[i] != beaconChainETHStrategy)
check toaddStrategiesToOperatorSet
andcreateOperatorSets
.if(strategy == beaconChainETHStrategy) continue;
added tomodifyAllocations
. This prevents allocating to the beacon-chain ETH strategy, but does not revert if it's provided. Can alternatively modify this to arequire
statement.Test to ensure no storage is mutated if
beaconChainETHStrategy
is provided.