Skip to content

v0.2.5-mainnet-m2-minor-eigenpod-upgrade
Compare
Choose a tag to compare
@wadealexc wadealexc released this 17 May 16:11
· 59 commits to mainnet since this release
v0.2.5-mainnet-m2-minor-eigenpod-upgrade
1bf4c12
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Small followup release addressing a minor EigenPod accounting inconsistency. This upgrade ensures EigenPods are compatible with and ready for the upcoming Rewards release.

No action is required.

Changes:

  • EigenPod.verifyWithdrawalCredentials requires that oracleTimestamp is from an epoch after the pod owner calls activateRestaking.

Affected Users:

  • This is a minor tweak to the timing window used in verifyWithdrawalCredentials, and only affects pods that have not yet made the M1 -> M2 transition (by calling activateRestaking), but plan to do so in the future.
  • For anyone making this transition, when you call activateRestaking and want to verify a validator's withdrawal credentials, it will no longer be possible to use an oracleTimestamp that belongs to the same epoch as your call to activateRestaking. You may need to wait for the next available timestamp instead.
Assets 2
Loading