Skip to content

Conversation

@ypatil12
Copy link
Collaborator

@ypatil12 ypatil12 commented Dec 1, 2025

v2.0.0 UX Improvements

This release brings 2 UX improvements to the middleware repo. We increment the major release due to the new createSlashableStakeQuorum interface.

🚀 New Features

  • NonSigner View Function for Bn254 Table Calculator: Constructs nonsigner witness onchain by passing in a list of signers

⛔ Breaking Changes

  • Update createSlashableStakeQuorum to take in a slasher address

🔧 Improvements

  • Move to foundry v1.5.0 and update formatting
  • Upgrade solc to 0.8.29

Changelog

  • feat: update registry coordinator for new createOperatorSets PR #548
  • feat: nonsigner view and operator index PR #545
  • chore: update readMe for middlewarev2 deployment PR #539

@ypatil12 ypatil12 force-pushed the release-dev/ux-updates branch from 04aebe5 to 071f3ec Compare December 1, 2025 19:02
ypatil12 and others added 3 commits December 1, 2025 14:50
**Motivation:**

As part of Layr-Labs/eigenlayer-contracts#1645,
we are adding a new `createOperatorSets` function that passes in the
slasher address upon creation of an operatorSet. Although the *old*
`createOperatorSets` function is not being deprecated, we are updating
the `RegistryCoordinator` in order to be **only compatible the new
function**.

**Modifications:**

- Update `createSlashableStakeQuorum` to take in a `slasher` address
- Update all tests
- Update `solc` version in `foundry.toml` to `0.8.29`, matching Core

**Result:**

Compatible with updated `AllocationManager` interface
Release notes for v2.0.0. Also, rev version for core submodule.
**Motivation:**

Natspec and docs were missing changes to the
`createTotalDelegatedStakeQuorum` and `createTotalSlashableStakeQuorum`.

**Modifications:**

Update docs and natspec. 

**Result:**

Up to date docs.

---------

Co-authored-by: Nadir Akhtar <[email protected]>
Copy link
Contributor

@nadir-akhtar nadir-akhtar left a comment

Choose a reason for hiding this comment

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

The CI seems to be failing for a "storage report" failure in regards to the RegistryCoordinator, but manual examination shows that no material change has been done to it, meaning this warning is a false positive. @0xClandestine suspects this is due to differing Foundry issues and will debug locally.

That said, no need to block the PR on this false positive.

@ypatil12 ypatil12 merged commit 799e94d into dev Dec 4, 2025
11 of 12 checks passed
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.

4 participants