Skip to content

Releases: Layr-Labs/eigenlayer-contracts

v1.3.0-rc.0

v1.3.0-rc.0 Pre-release
Pre-release

Choose a tag to compare

@ypatil12 ypatil12 released this 06 Mar 21:46
db0f582

Overview

This is the release candidate for the upcoming EigenLayer mainnet slashing release. It encompasses changes from two external audits along with several testing upgrades.

Note: This release is the similar to our v1.4.0.tesnet-holesky release, except it does not include any Pectra compatibility changes. We anticipate slashing to be deployed on mainnet prior to the mainnet Pectra hard fork.

Breaking Changes

  • Require AVS Metadata Registration prior to Opset Creation #1025
  • Rename getQueuedWithdrawal -> queuedWithdrawals: #1133. getQueuedWithdrawal still exists, but changes the behavior of getQueuedWithdrawals.
  • Behavior of getMinimumSlashableStake: #1037
  • encumberedMagnitude getter: #1038
  • ISignatureUtils -> ISignatureUtilsMixin and ISignatureUtilsMixinTypes: #1015

What's Changed

New Contributors

Full Changelog: v0.5.4...v1.3.0

v1.4.0

v1.4.0 Pre-release
Pre-release

Choose a tag to compare

@ypatil12 ypatil12 released this 13 Mar 20:25
aa84b7a

Overview

This is the release candidate for the upcoming EigenLayer mainnet slashing release. It encompasses changes from two external audits along with several testing upgrades. Full release notes here.

Note: This release is the similar to our v1.3.0.rc-1 release, except it DOES include Pectra compatibility changes. We anticipate slashing to be deployed on mainnet prior to the mainnet Pectra hard fork. The minor version 1.3 is skipped on testnet to align delivery order with mainnet.

Breaking Changes

  • Require AVS Metadata Registration prior to Opset Creation #1025
  • Rename getQueuedWithdrawal -> queuedWithdrawals: #1133. getQueuedWithdrawal still exists but now matches the behavior of getQueuedWithdrawals, except it returns shares for a single root.
  • Behavior of getMinimumSlashableStake: #1037
  • encumberedMagnitude getter: #1038
  • ISignatureUtils -> ISignatureUtilsMixin and ISignatureUtilsMixinTypes: #1015

What's Changed

New Contributors

Full Changelog: v1.2.0-testnet-holesky...v1.4.0-testnet-holesky

v1.2.0-testnet-holesky

Pre-release

Choose a tag to compare

@ypatil12 ypatil12 released this 12 Mar 22:35

Overview

This is the release to make EigenPods Pectra-Comptiable. There are no breaking changes. As part of this release, we also add support for compounding withdrawal credentials (0x02 validators). For more information on off-chain implications, see our Pectra guide

Summary of Changes

Full Changelog: v1.1.1...v1.2.0

v.1.1.1-testnet.holesky

Pre-release

Choose a tag to compare

@ypatil12 ypatil12 released this 21 Feb 15:28

Overview

This release is a hotfix upgrade to preprod/testnet with the purpose of unblocking AVSs and their integration with Slashing. It addresses some edge cases uncovered during audit and integration testing from AVS partners.

The changes in this upgrade are being prioritized to go live prior to a larger patch with the majority of the audit fix changes. This is scheduled for early March, and it progress can be viewed here #1046 or in the slashing-magnitude-fixes branch.

We are splitting these releases due to the interface changes we note below. As they may necessitate small reworks from AVSs, we are releasing them in advance of a larger patch with the remaining audit fixes.

Note: The rewards v2.1 changes in v1.1.1 are part of this release.

What's Changed

  • Added address avs field in calldata of IAVSRegistry.registerOperator, IAVSRegistry.deregisterOperator

    • The interface IAVSreigsitry can be found here.
  • Added IAVSRegistry.supportsAVS(avs) interface which is checked upon setting an AVS registry.
    There are now additional checks on the AVS registry being set to prevent registries being used without consent for multiple AVSs. The address avs field should also be verified by AVSs upon callbacks.

  • Removed the try/catch on AllocationManager.deregisterFromOperatorSets
    Operator deregistration will be a atomic interaction between the core and AVS contracts with the try/catch being removed. AVSs won’t have to account for how previously an operator could be still seen as registered in AVS contracts but have deregistered on the AllocationManager.

  • OperatorSets require avs metadata being set before they are created.

Full Changelog: v1.0.3...yash/merge-rewardsv2.1-in-v1.1.1

v1.1.0-testnet.holesky

Pre-release

Choose a tag to compare

@0xrajath 0xrajath released this 06 Feb 19:12
64c0283

What's Changed

Full Changelog: v1.0.3...v1.1.0-testnet

v0.5.4

Choose a tag to compare

@0xrajath 0xrajath released this 21 Jan 21:02
bb09862

Overview

The Rewards v2 protocol upgrade is the next iteration of EigenLayer rewards. The proposal is outlined in depth in (ELIP-001).

Rewards v2 addresses key challenges identified in the EigenLayer Rewards MVP (v1), particularly the need for Operator-directed rewards via external logic and flexibility for Operators in setting different fee rates to better cover operating costs or attract more stake when running different AVS types. The growing demand from AVSs for more performance-based rewards prompted this upgrade, ensuring EigenLayer's rewards protocol can serve a wider variety of scenarios.

This upgrade to the core contracts has been audited. The results of these audits are public and can be found here.

Breaking changes and upcoming breaking changes

Operators that integrated the first released version of the Rewards code should note the following naming change. globalOperatorCommissionBips has been renamed to defaultOperatorSplitBips.

Improvements

  • Performance-based and directed rewards from AVSs to Operators via the createOperatorDirectedAVSRewardsSubmission function.
  • Operator-configurable split for AVS Rewards, via the setOperatorAVSSplit function on the RewardsCoordinator to allow per-AVS variable Operator fees.
  • Operator-configurable split for Programmatic Incentives with the Eigen Foundation, via the setOperatorPISplit function on the RewardsCoordinator to allow variable operator fees for Programmatic Incentives.
  • Batch claiming for both Stakers and Operators via the processClaims function on the RewardsCoordinator
  • Permissionless verifiability of the entire Rewards pipeline via the open-source Eigen Sidecar. More details on this can be found in the Sidecar repository.

What's Changed

Full Changelog: v0.4.3-mainnet-rewards-foundation-incentives...v0.5.4

v0.5.4-testnet-rewards-v2

Pre-release

Choose a tag to compare

@0xrajath 0xrajath released this 17 Jan 16:44
bb09862

What's Changed

Full Changelog: v0.5.3...v0.5.4-holesky

Slashing Audit Release

Pre-release

Choose a tag to compare

@ypatil12 ypatil12 released this 28 Jan 21:30
7a6f8a6

Audit release for SP/Certora

v1.0.3-testnet-slashing

Pre-release

Choose a tag to compare

@ypatil12 ypatil12 released this 06 Jan 21:26
44ece6d

What's Changed

Full Changelog: v1.0.2...v1.0.3

v1.0.2-testnet-slashing

Pre-release

Choose a tag to compare

@ypatil12 ypatil12 released this 19 Dec 19:40
8fb585a

This release marks the testnet slashing release. A full spec change is in documented in ELIP-002

See the following docs for breaking changes:

New Addresses

There are two new core contracts deployed

Name Proxy Implementation Notes
AllocationManager 0x78469728304326CBc65f8f95FA756B0B73164462 0xe03d...4ee2 Proxy: TUP@4.9.0
PermissionController 0x598cb226B591155F767dA17AfE7A2241a68C5C10 0x7ab0...a2b9 Proxy: TUP@4.9.0

What's Changed

Full Changelog: v0.5.3...v1.0.2