Skip to content

fix: ejection manager inclusive ejection #462

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

Merged
merged 2 commits into from
May 1, 2025

Conversation

ypatil12
Copy link
Collaborator

Motivation:

Per Hexens Eigen2-2, The current rate limit logic allows ejection beyond the allowed limit.

Modifications:

Modify the ejection logic such that when the caller is the ejector, do not automatically eject the first operator regardless of limit.

Result:

Proper rate limit assertions.

@ypatil12
Copy link
Collaborator Author

Regression Test:
Screenshot 2025-04-30 at 4 42 36 PM

@ypatil12 ypatil12 requested a review from wadealexc April 30, 2025 21:43
@ypatil12 ypatil12 changed the base branch from hexens/audit-fixes to hexens-slashing/audit-fixes April 30, 2025 21:44
@ypatil12 ypatil12 requested a review from pakim249CAL May 1, 2025 02:33
Copy link
Contributor

@wadealexc wadealexc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ypatil12 ypatil12 merged commit be5dd14 into hexens-slashing/audit-fixes May 1, 2025
5 checks passed
@ypatil12 ypatil12 deleted the hexens/eigen2-2 branch May 1, 2025 16:05
ypatil12 added a commit that referenced this pull request May 7, 2025
**Motivation:**

Middleware slashing audit fixes from Hexens and Dedaub. 

**Modifications:**

**Medium Sev**
- #467

**Low Sev**
- #462
- #463
- #468
- #474 - note: this removes stale stakes checks from the `BLSSignatureChecker` 

**Informational/Docs**
- #465
- #466
- #472

**Result:**

Audit fixes applied to slashing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants