-
Notifications
You must be signed in to change notification settings - Fork 435
release: MOOCOW [DO NOT MERGE] #1522
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
Draft
ypatil12
wants to merge
19
commits into
release/moocow-rc.1
Choose a base branch
from
release/moocow
base: release/moocow-rc.1
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
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
Passing workflow run: https://github.com/Layr-Labs/eigenlayer-contracts/actions/runs/16151588124 |
**Motivation:** Previously, we stored `startBlock` and computed the `completeBlock` at runtime by iterating through the list of added strategies for a given `slashId`. This approach required recalculating the `completeBlock` each time. **Modifications:** We now store `completeBlock` directly instead of `startBlock`. During each call to `initiateSlashEscrow`, we compare the delay of the newly added strategy to the current `completeBlock` for the `slashId`. If the new delay is larger, we update `completeBlock` accordingly. This ensures that the maximum delay is always preserved. **Result:** The `completeBlock` for each `slashId` is now computed and maintained incrementally, eliminating the need for runtime iteration over all strategies.
**Motivation:** Release functions did not have a `nonReentrant` check, and while code is well isolated it would be nice to prevent the concern entirely. **Modifications:** * Applied the `nonReentrant` modifier to both `releaseSlashEscrow` and `releaseSlashEscrowByStrategy` functions within the `SlashEscrowFactory` to prevent potential reentrancy vulnerabilities. * Relocated the `nonReentrant` modifier from `clearBurnOrRedistributableShares` to `clearBurnOrRedistributableSharesByStrategy` in the `StrategyManager` to ensure both methods are protected. **Result:** Less reentrancy-based security risk.
**Motivation:** It was previously possible to set the redistribution recipient for a redistributing operator set to the burn address, meaning it's effectively a non-redistributing operator set. **Modifications:** - Ensure`redistributionRecipient != DEFAULT_BURN_ADDRESS`. **Result:** L-02 resolved.
**Motivation:** Missing documentation noting that an upgrade is required to rescue paused funds. **Modifications:** - Update `ISlashEscrowFactory.sol` and `SlashEscrowFactory.md`. **Result:** L-01 resolved.
**Motivation:** We've decided we do not want delays on redistributions. **Modifications:** - Removed `SlashEscrowFactory` + `SlashEscrow` and all relevant changes. **Result:** Tokens are immediately redistributed upon calling `clearBurnOrRedistributableShares`.
**Motivation:** Incorrect gap, off by one. **Modifications:** - Updated SM gap. **Result:** Correct SM gap.
**Motivation:** Test should be passing. **Modifications:** - Minor (likely rebase) error fixes. **Result:** Tests passing.
**Motivation:** We want to address a few nits. **Modifications:** - slash's -> operator set's. **Result:** Nits addressed.
**Motivation:** Want up to date changelog. **Modifications:** - Updated changelog. **Result:** Up-to-date changelog.
**Motivation:** Need updated upgrade scripts without slash escrow **Modifications:** - Remove slash escrow - Add source chain conditionals - Blacklisted eigen and beigen tokens **Result:** Working upgrade scripts --------- Co-authored-by: clandestine.eth <[email protected]>
* test: add unit tests for consolidation and withdrawal
* chore: make bindings * chore: misc feedback
chore: changelog
**Motivation:** SAFE now disables `delegateCall`. Thus, we cannot use multisend via the Multisig directly. This results in the redistro/moocow failing **Modifications:** Tests: `zeus test --env mainnet script/releases/v1.6.0-moocow-and-elip5/*.s.sol --rpcUrl $RPC_MAINNET -vvv` Upgrade deploy scripts to split up execution **Result:** Working upgrade
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:
CI for moocow release
Modifications:
Rebase off of v1.5.0. Target original v1.6.0 release (no eigenpod related changes)
Result:
Clear release