hyperlane-monorepo

Commit Graph

Author	SHA1	Message	Date
Kunal Arora	968160f4e2	feat: AVS upgrade for correct reporting on Eigenlayer UI (#4152 ) ### Description - upgraded the AVS on holesky - now working splendidly! - included the function call for upgrading the AVS on mainnet `upgradeHsm4090` - encoded calldata to `0x9e3045a8Feb10F05f4d1268Ef8E303b655e8F562` is `0x99a88ec4000000000000000000000000e8e59c6c8b56f2c178f63bcfc4ce5e5e2359c8fc0000000000000000000000009e3045a8feb10f05f4d1268ef8e303b655e8f562 ` - make the call `forge script script/avs/DeployAVS.s.sol:DeployAVS --sig "upgradeHsm4090(string memory,address,address)" "ethereum" 0xe8E59c6C8B56F2c178f63BCFC4ce5e5e2359c8fc 0x272CF0BB70D3B4f79414E0823B426d2EaFd48910 --rpc-url https://rpc.ankr.com/eth -vvvv --sender 0x3965AC3D295641E452E0ea896a086A9cD7C6C5b6` to repro ### Drive-by changes Found two issues with forge scripting - upgrade call wasn't working with a pranked sender but the equivalent low-level call worked - once you call `vm.expectRevert()` the script terminates. ### Related issues - fixes https://github.com/hyperlane-xyz/issues/issues/1297 ### Backward compatibility Yes ### Testing Fork run of upgrade --------- Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>	4 months ago
Yorke Rhodes	49f41d9759	chore: Merge branch 'main' into cli-2.0 (#3863 ) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Kunal Arora <55632507+aroralanuk@users.noreply.github.com> Co-authored-by: Connor McEwen <connor.mcewen@gmail.com> Co-authored-by: Trevor Porter <tkporter4@gmail.com> Co-authored-by: byeongsu-hong <hong@byeongsu.dev> Co-authored-by: Avi Atkin <103125634+avious00@users.noreply.github.com> Co-authored-by: Daniel Savu <23065004+daniel-savu@users.noreply.github.com> Co-authored-by: J M Rossy <jm.rossy@gmail.com> Co-authored-by: Ali Alaoui <aalaoui2001@gmail.com> Co-authored-by: Nam Chu Hoai <nambrot@googlemail.com> Co-authored-by: Paul Balaji <paul@hyperlane.xyz> Co-authored-by: omahs <73983677+omahs@users.noreply.github.com>	6 months ago
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

3 Commits (23a2679bbee23ce44d9fcda22f99df618f8a34e0)