2 Commits (f4bbfcf08a4d93d681eb99a9f32c5c9b84e5f41e)

Author	SHA1	Message	Date
Kunal Arora	d0ce9081dd	feat: support attesting signing key for Hyperlane AVS (#3847) ... ### Description - Adding support for attesting signing key and key rotation from here https://github.com/Layr-Labs/eigenlayer-middleware/pull/252 ### Drive-by changes None ### Related issues None ### Backward compatibility Yes ### Testing Tested by Eigenlayer here: https://github.com/Layr-Labs/eigenlayer-middleware/blob/dev/test/unit/ECDSAStakeRegistryUnit.t.sol	6 months ago
Kunal Arora	76619d0729	feat: Hyperlane AVS contracts (#3651) ... ### Description - Implements `IServiceManager` for the `ECDSAServiceManagerBase` which has a single quorum - `HyperlaneServiceManager` (HSM), the main AVS contract for registering/deregistering operators and enrolling/unenrolling into challengers - the HSM has a mutable slasher so that once the EL slasher is live, we can set it for your AVS too to enable freezing operators. - EnumerableMapEnrollment for a enumerable map of enrollment statuses for each operator and challenger Update: I switched the ECDSAServiceManager i had written earlier to steven's PR here: https://github.com/Layr-Labs/eigenlayer-middleware/pull/234. The differences are: - events for (de)registering Notes - `hardhat yarn` tries looking for all imports (including the ones from submodules) as npm libraries , eg. @eigenlayer/core. ### Drive-by changes - none ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3590, ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->	7 months ago