chore: update core submodule and fix broken docs links (Layr-Labs#188)

Author: wadealexc

.github/workflows/tests.yml

@@ -8,8 +8,9 @@ on:
   push:
     branches:
       - master
-      - m2-mainnet
-      - m2-mainnet-fixes
+      - mainnet
+      - testnet-goerli
+      - dev
   pull_request:
 
 env:

.gitmodules

@@ -4,7 +4,7 @@
 [submodule "lib/eigenlayer-contracts"]
 	path = lib/eigenlayer-contracts
 	url = https://github.com/Layr-labs/eigenlayer-contracts
-	branch = m2-mainnet-fixes
+	branch = dev
 [submodule "lib/ds-test"]
 	path = lib/ds-test
 	url = https://github.com/dapphub/ds-test

README.md

@@ -1,4 +1,4 @@
-[core-docs-m2]: https://github.com/Layr-Labs/eigenlayer-contracts/tree/m2-mainnet/docs
+[core-docs-dev]: https://github.com/Layr-Labs/eigenlayer-contracts/tree/dev/docs
 [core-repo]: https://github.com/Layr-Labs/eigenlayer-contracts
 
 # EigenLayer Middleware
@@ -27,7 +27,7 @@ Most of this content is intro-level and describes user interactions with the Eig
 For shadowy super-coders:
 * The most up-to-date technical documentation can be found in [/docs](/docs).
 * To get an idea of how users interact with these contracts, check out the integration tests: [/test/integration](./test/integration)
-* To explore the EigenLayer core contracts, check out the core repo technical docs [here][core-docs-m2].
+* To explore the EigenLayer core contracts, check out the core repo technical docs [here][core-docs-dev].
 
 ## Building and Running Tests
 

docs/BLSSignatureChecker.md

@@ -1,9 +1,7 @@
-[core-docs-m2]: https://github.com/Layr-Labs/eigenlayer-contracts/tree/m2-mainnet/docs
-[core-dmgr-docs]: https://github.com/Layr-Labs/eigenlayer-contracts/blob/m2-mainnet/docs/core/DelegationManager.md
-[core-dmgr-register]: https://github.com/Layr-Labs/eigenlayer-contracts/blob/m2-mainnet/docs/core/DelegationManager.md#registeroperatortoavs
-[core-dmgr-deregister]: https://github.com/Layr-Labs/eigenlayer-contracts/blob/m2-mainnet/docs/core/DelegationManager.md#deregisteroperatorfromavs
+[core-docs-dev]: https://github.com/Layr-Labs/eigenlayer-contracts/tree/dev/docs
+[core-dmgr-docs]: https://github.com/Layr-Labs/eigenlayer-contracts/blob/dev/docs/core/DelegationManager.md
 
-[eigenda-service-manager]: https://github.com/Layr-Labs/eigenda/blob/m2-mainnet-contracts/contracts/src/core/EigenDAServiceManager.sol
+[eigenda-service-manager]: https://github.com/Layr-Labs/eigenda/blob/dev-contracts/contracts/src/core/EigenDAServiceManager.sol
 
 ## BLSSignatureChecker
 
@@ -92,7 +90,7 @@ This method performs the following steps. Note that each step involves lookups o
     * `quorumNumbers` MUST be an ordered list of valid, initialized quorums
     * `params.nonSignerPubkeys` MUST ONLY contain unique pubkeys, in ascending order of their pubkey hash
 * For each quorum:
-    * If stale stakes are forbidden (see [`BLSSignatureChecker.setStaleStakesForbidden`](#blssignaturecheckersetstalestakesforbidden)), check the last `quorumUpdateBlockNumber` is within `DelegationManager.minWithdrawalDelayBlocks` of `referenceBlockNumber`. This references a value in the EigenLayer core contracts - see [EigenLayer core docs][core-docs-m2] for more info.
+    * If stale stakes are forbidden (see [`BLSSignatureChecker.setStaleStakesForbidden`](#blssignaturecheckersetstalestakesforbidden)), check the last `quorumUpdateBlockNumber` is within `DelegationManager.minWithdrawalDelayBlocks` of `referenceBlockNumber`. This references a value in the EigenLayer core contracts - see [EigenLayer core docs][core-docs-dev] for more info.
     * Validate that each `params.quorumApks` corresponds to the quorum's apk at the `referenceBlockNumber`
 * For each historical state lookup, the `referenceBlockNumber` and provided index MUST point to a valid historical entry: 
     * `referenceBlockNumber` MUST come after the entry's `updateBlockNumber`

docs/README.md

@@ -2,12 +2,12 @@
 Reference Links:
  -->
 [core-contracts-repo]: https://github.com/Layr-Labs/eigenlayer-contracts
-[core-docs-m2]: https://github.com/Layr-Labs/eigenlayer-contracts/tree/m2-mainnet/docs
+[core-docs-dev]: https://github.com/Layr-Labs/eigenlayer-contracts/tree/dev/docs
 [eigenda-repo]: https://github.com/Layr-Labs/eigenda/
 [bitmaputils-lib]: ../src/libraries/BitmapUtils.sol
 
-[core-registerToAVS]: https://github.com/Layr-Labs/eigenlayer-contracts/blob/m2-mainnet/docs/core/DelegationManager.md#registeroperatortoavs
-[core-deregisterFromAVS]: https://github.com/Layr-Labs/eigenlayer-contracts/blob/m2-mainnet/docs/core/DelegationManager.md#deregisteroperatorfromavs
+[core-registerToAVS]: https://github.com/Layr-Labs/eigenlayer-contracts/blob/dev/docs/core/AVSDirectory.md#registeroperatortoavs
+[core-deregisterFromAVS]: https://github.com/Layr-Labs/eigenlayer-contracts/blob/dev/docs/core/AVSDirectory.md#deregisteroperatorfromavs
 
 ## EigenLayer Middleware Docs
 
@@ -64,7 +64,7 @@ Each quorum has an associated list of `StrategyParams`, which the Owner can conf
 
 When the `StakeRegistry` updates its view of an Operator's stake for a given quorum, it queries the `DelegationManager` to get the Operator's shares in each of the quorum's strategies and applies the multiplier to the returned share count.
 
-For more information on the `DelegationManager`, see the [EigenLayer core docs][core-docs-m2].
+For more information on the `DelegationManager`, see the [EigenLayer core docs][core-docs-dev].
 
 ##### Operator Sets and Churn
 

docs/RegistryCoordinator.md

@@ -1,6 +1,6 @@
-[core-dmgr-docs]: https://github.com/Layr-Labs/eigenlayer-contracts/blob/m2-mainnet/docs/core/DelegationManager.md
-[core-dmgr-register]: https://github.com/Layr-Labs/eigenlayer-contracts/blob/m2-mainnet/docs/core/DelegationManager.md#registeroperatortoavs
-[core-dmgr-deregister]: https://github.com/Layr-Labs/eigenlayer-contracts/blob/m2-mainnet/docs/core/DelegationManager.md#deregisteroperatorfromavs
+[core-dmgr-docs]: https://github.com/Layr-Labs/eigenlayer-contracts/blob/dev/docs/core/DelegationManager.md
+[core-dmgr-register]: https://github.com/Layr-Labs/eigenlayer-contracts/blob/dev/docs/core/DelegationManager.md#registeroperatortoavs
+[core-dmgr-deregister]: https://github.com/Layr-Labs/eigenlayer-contracts/blob/dev/docs/core/DelegationManager.md#deregisteroperatorfromavs
 
 ## RegistryCoordinator
 

docs/ServiceManagerBase.md

@@ -1,6 +1,5 @@
-[core-dmgr-docs]: https://github.com/Layr-Labs/eigenlayer-contracts/blob/m2-mainnet/docs/core/DelegationManager.md
-[core-dmgr-register]: https://github.com/Layr-Labs/eigenlayer-contracts/blob/m2-mainnet/docs/core/DelegationManager.md#registeroperatortoavs
-[core-dmgr-deregister]: https://github.com/Layr-Labs/eigenlayer-contracts/blob/m2-mainnet/docs/core/DelegationManager.md#deregisteroperatorfromavs
+[core-registerToAVS]: https://github.com/Layr-Labs/eigenlayer-contracts/blob/dev/docs/core/AVSDirectory.md#registeroperatortoavs
+[core-deregisterFromAVS]: https://github.com/Layr-Labs/eigenlayer-contracts/blob/dev/docs/core/AVSDirectory.md#deregisteroperatorfromavs
 
 ## ServiceManagerBase
 
@@ -11,7 +10,7 @@
 The `ServiceManagerBase` represents the AVS's address relative to EigenLayer core. When registering or deregistering an operator from an AVS, the AVS's `ServiceManagerBase` communicates this change to the core contracts, allowing the core contracts to maintain an up-to-date view on operator registration status with various AVSs.
 
 *As of M2*:
-* Currently, this contract is used by the `DelegationManager` to keep track of operator registration and deregistration. Eventually, this relationship will be expanded to allow operators to opt in to slashing and payments for services.
+* Currently, this contract is used by the `AVSDirectory` to keep track of operator registration and deregistration. Eventually, this relationship will be expanded to allow operators to opt in to slashing and payments for services.
 
 ---    
 
@@ -27,18 +26,18 @@ function registerOperatorToAVS(
     onlyRegistryCoordinator
 ```
 
-When the `RegistryCoordinator` registers an operator for an AVS and they were not previously registered, it calls this method on `ServiceManagerBase`, which forwards the call to the EigenLayer core contract, the `DelegationManager`.
+When the `RegistryCoordinator` registers an operator for an AVS and they were not previously registered, it calls this method on `ServiceManagerBase`, which forwards the call to the EigenLayer core contract, the `AVSDirectory`.
 
 *Entry Points*:
 * `RegistryCoordinator.registerOperator`
 * `RegistryCoordinator.registerOperatorWithChurn`
 
 *Effects*:
-* See EigenLayer core: [`DelegationManager.registerOperatorToAVS`][core-dmgr-register]
+* See EigenLayer core: [`AVSDirectory.registerOperatorToAVS`][core-registerToAVS]
 
 *Requirements*:
 * Caller MUST be the `RegistryCoordinator`
-* See EigenLayer core: [`DelegationManager.registerOperatorToAVS`][core-dmgr-register]
+* See EigenLayer core: [`AVSDirectory.registerOperatorToAVS`][core-registerToAVS]
 
 #### `deregisterOperatorFromAVS`
 
@@ -51,7 +50,7 @@ function deregisterOperatorFromAVS(
     onlyRegistryCoordinator
 ```
 
-When the `RegistryCoordinator` deregisters an operator from an AVS, it calls this method on `ServiceManagerBase`, which forwards the call to the EigenLayer core contract, the `DelegationManager`.
+When the `RegistryCoordinator` deregisters an operator from an AVS, it calls this method on `ServiceManagerBase`, which forwards the call to the EigenLayer core contract, the `AVSDirectory`.
 
 *Entry Points*:
 * `RegistryCoordinator.registerOperatorWithChurn`
@@ -61,8 +60,8 @@ When the `RegistryCoordinator` deregisters an operator from an AVS, it calls thi
 * `RegistryCoordinator.updateOperatorsForQuorum`
 
 *Effects*:
-* See EigenLayer core: [`DelegationManager.deregisterOperatorFromAVS`][core-dmgr-deregister]
+* See EigenLayer core: [`AVSDirectory.deregisterOperatorFromAVS`][core-deregisterFromAVS]
 
 *Requirements*:
 * Caller MUST be the `RegistryCoordinator`
-* See EigenLayer core: [`DelegationManager.deregisterOperatorFromAVS`][core-dmgr-deregister]
+* See EigenLayer core: [`AVSDirectory.deregisterOperatorFromAVS`][core-dmgr-deregister]

docs/registries/StakeRegistry.md

@@ -1,4 +1,4 @@
-[core-docs-m2]: https://github.com/Layr-Labs/eigenlayer-contracts/tree/m2-mainnet/docs
+[core-docs-dev]: https://github.com/Layr-Labs/eigenlayer-contracts/tree/dev/docs
 
 ## StakeRegistry
 
@@ -26,7 +26,7 @@ For a given quorum, an Operator's stake weight is determined by iterating over t
 
 Note that the `RegistryCoordinator` Owner also configures a "minimum stake" for each quorum, which an Operator must meet in order to register for (or remain registered for) a quorum.
 
-For more information on the `DelegationManager`, strategies, and shares, see the [EigenLayer core docs][core-docs-m2].
+For more information on the `DelegationManager`, strategies, and shares, see the [EigenLayer core docs][core-docs-dev].
 
 #### High-level Concepts