2 Commits (45eb3ae5e300d6eb921ee3c9a75193cf51d39b10)

Author	SHA1	Message	Date
Mohammed Hussan	44cc9bf6b3	feat(cli): Add avs validator status command (#4056) ... ### Description <!-- What's included in this PR? --> - Command to check all operators on our AVS and show the chains that they are validating on - Already been reviewed here https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4004, this PR was to merge it main instead of cli-2.0 Example usage: ``` yarn hyperlane avs check --chain ethereum --registry $REGISTRY Hyperlane CLI Checking AVS validator status for ethereum, this may take up to a minute to run... ❗️ MerkleTreeHook is not deployed on anvil8545 Operator name: Abacus Works AVS Operator Operator address: 0xFe114FcC7609578f525219a8eF77e2CCe27C5357 Validator address: 0x03c842db86A6A3E524D4a6615390c1Ea8E2b9541 Validating on... ethereum Storage location: s3://hyperlane-mainnet3-ethereum-validator-0/us-east-1 Latest merkle tree checkpoint index: 8219 Latest validator checkpoint index: 8219 ✅ Validator is signing latest checkpoint Operator name: Kelp by Kiln Operator address: 0x96fC0751e0febe7296d4625500f8e4535a002c7d Validator address: 0xEa5f21513182e97D0169a4d2E7aC71Ae8827F5bC Validating on... ethereum Storage location: s3://kiln-mainnet-hyperlane-validator-signatures/eu-west-1/ethereum Latest merkle tree checkpoint index: 8219 ❌ Failed to fetch latest signed checkpoint index The following warnings were encountered: ❗️ Failed to fetch latest signed checkpoint index of validator on ethereum, this is likely due to failing to read an S3 bucket ``` ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> - Fixes #3976 ### 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 --> No ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> Manual	5 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