2 Commits (0d12ff31cdf1b66c64e653b7e0679d26a8a7633f)

Author	SHA1	Message	Date
Kunal Arora	b440d98be3	feat: CLI command for (de)registering from AVS (#3790) ... ### Description - CLI commands for registering/deregistering an operator from the AVS - uses the encrypted local key store as source of operator key - Web3Signer not implemented yet ### Drive-by changes None ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3598 (duplicate) - also fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3758 ### Backward compatibility Yes ### Testing Onchain https://holesky.etherscan.io/tx/0x95d95f6fcf1f80d0911124bd0a85ac848eecedc8ec39b3ceba6e1a30792c5651 and https://holesky.etherscan.io/tx/0xd1d1b56d45c30276596b73e040e3747ca7ef90977182f1912c5b399559d2a503 --------- Co-authored-by: Connor McEwen <connor.mcewen@gmail.com> Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>	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