166 Commits (23a2679bbee23ce44d9fcda22f99df618f8a34e0)

Author	SHA1	Message	Date
Yorke Rhodes	836060240b	feat: mutable storage ISMs (#4577) ... ### Description Some chains like zkSync do not support eip1167 (minimal/meta) proxies. This PR adds an alternative storage based multisig and aggregation ISM for use on these chains. ### Drive-by changes Simplify CLI multisig interactive config builder. Remove stale multisig config. ### Related issues None ### Backward compatibility Yes, relayer already supports this module type ### Testing Contract unit tests Manual CLI tests 	3 weeks ago
Kunal Arora	f26453ee55	fix(contracts): add `msg.Value` to `verifyMessageId` (#4541) ... ### Description - Added to the msg.value to verifyMessageId to test if the msgValue passed in is the same as the msgValue used postDispatch ### Drive-by changes - None ### Related issues - fixes https://github.com/chainlight-io/2024-08-hyperlane/issues/3 ### Backward compatibility Yes ### Testing Unit tests	3 weeks ago
Kunal Arora	469f2f3403	fix(contracts): quote management for L2->L1 hooks (#4552) ... ### Description - check for sufficient fees in `AbstractMessageIdAuthHook` and refund surplus - add a child hook to OPL2ToL1Hook and ArbL2ToL1Hook to use the igp to pay for the destination gas fees ~~Note: LayerzeroL2Hook currently also refunds from msg.value, will make it into issue to be fixed later as we're using the layerzero hooks right now.~~ ### Drive-by changes - None ### Related issues - fixes https://github.com/chainlight-io/2024-08-hyperlane/issues/10 ### Backward compatibility No ### Testing Fuzz	3 weeks ago
Kunal Arora	cca032fb18	fix(contracts): assume no zero address for beneficiary address in `ProtocolFee` fuzz test (#4781) ... ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### 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 -->	4 weeks ago
Kunal Arora	0640f837ce	fix(contracts): InterchainAccountRouter minor audit remediation (#4581) ... ### Description - disabled the ICARouter's ability to change hook given that the user doesn't expect the hook to change after they deploy their ICA account. Hook is not part of the derivation like ism on the destination chain and hence, cannot be configured custom by the user. ### Drive-by changes - MailboxClient events for hook and ism setting - ProtocolFee events for setting beneficiary and owner ### Related issues - partly fixes https://github.com/chainlight-io/2024-08-hyperlane/issues/14 ### Backward compatibility No ### Testing Unit tests	4 weeks ago
Kunal Arora	a42616ff3f	fix(contracts): add rebasing compatibility for `HypERC4626` (#4524) ... ### Description - Added overrides for transferFrom, totalSupply to reflect the internal share based accounting for the 4626 mirror asset ### Drive-by changes - Overridden `_transfer` to update the Transfer event to display the asset being transfers as amount not the internal shares. ### Related issues - fixes https://github.com/chainlight-io/2024-08-hyperlane/issues/6 ### Backward compatibility Yes ### Testing Fuzz testing	1 month ago
Kunal Arora	c55257cf5f	fix(contracts): minor token related changes (#4580) ... ### Description Minor token related changes like adding custom hook to 4626 collateral, checking for ERC20 as valid contract in HypERC20Collateral, etc. ### Drive-by changes check for overflow in bytes32ToAddress ### Related issues - partly fixes https://github.com/chainlight-io/2024-08-hyperlane/issues/14 ### Backward compatibility Yes ### Testing Unit tests	1 month ago
Kunal Arora	8cc0d9a4ae	feat(contracts): add wrapped HypERC4626 for ease of defi use (#4563) ... ### Description ### Drive-by changes None ### Related issues - closes https://github.com/chainlight-io/2024-08-hyperlane/issues/7 ### Backward compatibility Yes ### Testing Unit	1 month ago
Kunal Arora	72c23c0d63	fix(contracts): owner vault metadata compatibility (#4566) ... ### Description - Added PRECISION and rateUpdateNonce to ensure compatibility of HypERC4626 (even though this is not a useful warp route bc exchangeRate will stay at 1e10) ### Drive-by changes None ### Related issues - closes https://github.com/chainlight-io/2024-08-hyperlane/issues/9 ### Backward compatibility No ### Testing Unit test	1 month ago
Kunal Arora	c9bd7c3c52	fix(contracts): `RateLimit` minor changes (#4575) ... ### Description - Added a check for invalid capacity and event for token level change ### Drive-by changes None ### Related issues - fixes https://github.com/chainlight-io/2024-08-hyperlane/issues/14 ### Backward compatibility Yes ### Testing Unit tests	1 month ago
Kunal Arora	3e1ab75643	fix(contracts): add check for valid mailbox and relayer in `TrustedRelayerIsm` (#4553) ... ### Description - minor fix: add an isContract check for mailbox and non-zero check for relayer when instantiating TrustedRelayerIsm ### Drive-by changes None ### Related issues - partly fixes https://github.com/chainlight-io/2024-08-hyperlane/issues/14 ### Backward compatibility Yes ### Testing Unit	1 month ago
Kunal Arora	ec6b874b15	feat(contracts): add nonce for monotonically increasing delivery ordering for `HypERC4626` (#4534) ... ### Description - Added a `rateUpdateNonce` in `HypERC4626Collateral` and `previousNonce` in `HypERC4626` to ensure we only update the exchangeRate on the synthetic asset if the update was after the last recorded update. This is to make sure we don't update it to a stale exchange rate which may cause losses to users using the synthetic asset. ### Drive-by changes - `processInboundMessage` in MockMailbox` to simulate processing of messages out of order. ### Related issues - fixes https://github.com/chainlight-io/2024-08-hyperlane/issues/12 ### Backward compatibility Yes ### Testing Unit test	1 month ago
Kunal Arora	2760da1ded	fix: ensure no duplicate signatures verified for `AbstractWeightedMultisigIsm.verify()` (#4468) ... ### Description - There's a bug in the verify function of `AbstractWeightedMultisigIsm` that an attacker might use to bypass the verification of multiple signatures. The code tried to check the duplication of the signers if not found, but the code does not increment validatorIndex when the recovered signer matches to the stored signer. For instance: - validatorsAndThresholdWeight returns [A, B, C, D] - an attacker uses signatures as [sig from A, sig from A, sig from A, sig from A, ...] or [sig from B, sig from B, …] Fix is to add a ++validatorIndex at the end of the for loop implies we don't allow the next signer to be the same as the signer we just verified. ### Drive-by changes None ### Related issues From Chainlight's audit findings ### Backward compatibility We haven't deployed these contracts yet on testnet/mainnet ### Testing Fuzz testing	1 month ago
Kunal Arora	c9085afd96	fix: add fix for checking for correct messageId in `OPL2ToL1Ism` and `ArbL2ToL1Ism` via external call (#4437) ... ### Description - In agreement with Chainlight team's recommendation, added a second isVerified() check after portal call to make sure an arbitrary call which passes the check for metadata length and messageId cannot be verified without calling is verifyMessageId(messageId) in `OPL2ToL1Ism` and `ArbL2ToL1` ### Drive-by changes None ### Related issues - fixes https://github.com/chainlight-io/2024-08-hyperlane/issues/2 ### Backward compatibility No, but the contracts aren't deployed anywhere ### Testing Unit testing	1 month ago
Yorke Rhodes	92c86cca66	fix: forward value from ICA router to proxies (#4395) ... ### Description Value sent to the hyperlane message recipient (InterchainAccountRouter) would not be forwarded to the proxy account for use in calls with value. Only value sent to the proxy account was supported. ### Related Issues - Fixes https://github.com/chainlight-io/2024-08-hyperlane/issues/4 ### Backward compatibility No, ICA routers would need upgrade/redeploy ### Testing Unit Tests	2 months ago
Yorke Rhodes	bb75eba74a	fix: recipient rate limited ISM (#4636) ... ### Description Add recipient restriction to rate limited ISM. This prevents multiple recipients from sharing the same rate limit ISM and denial of service attacks. ### Backward compatibility No ### Testing Unit Tests	2 months ago
Yorke Rhodes	c5c217f8ea	feat: embed package version in deployed bytecode (#4518) ... ### Description Embed NPM package version in all deployed contracts bytecode. Follows [similar pattern to published CLI version](3010e36ec9/typescript/cli/src/version.ts (L0-L1)). Should not be conflated with `Mailbox.VERSION` used for message encoding. ### Drive-by Changes Unfixes solidity NPM package version from typescript packages ### Backward compatibility No, only applies to new deployments or upgrades ### Testing Tested [changeset glob](https://changesets-docs.vercel.app/fixed-packages#using-glob-expressions) ```ts console.log(micromatch(['@hyperlane-xyz/sdk', '@hyperlane-xyz/core', '@hyperlane-xyz/cli'], ['@hyperlane-xyz/!(core)|*'])); ['@hyperlane-xyz/sdk', '@hyperlane-xyz/cli'] ``` Added test that version function is on ABI	2 months ago
Kunal Arora	c032b8ba27	chore: refactor MessagIdHook/ISM tests into a common `ExternalBridgeTest` contract (#4490) ... ### Description We currently have 6 different versions of ISMs derived from AbstractMessageIdAuthorizedIsm: - OPL2ToL1 - ArbL2ToL1 - OPStack (L1->L2) - ERC5164 - LayerZero - PolygonPOS But all of them have their own custom test suite right now, with widely overlapping testing areas. For standardizing the tests, I've created a base test contract `ExternalBridgeTest` that handles the common tests. This has a few benefits: - harder to miss tests for known pitfalls like msg.value or asynchronicity assumption for verifyMessageId - less code duplication with each additional Ism I have moved OPL2ToL1, ArbL2ToL1, OPStack, and ERC5164 to the new base test, and I'll forgo the rest for now because of the time sensitivity of audit remediations. I've created an issue tracking the remaining work here: https://github.com/hyperlane-xyz/issues/issues/1384 ### Drive-by changes None ### Related issues Related to https://github.com/chainlight-io/2024-08-hyperlane/issues/3 ### Backward compatibility Yes ### Testing Unit	2 months ago
Yorke Rhodes	eb5afcf3eb	fix: native value covers message value in HypNative (#4526) ... ### Description `HypNative.transferRemote` overload checks that the native `msg.value` deposited covers the warp message `amount` in addition to checking the mailbox post-dispatch fee is covered. ### Backward compatibility No, applies to net new `HypNative` and `HypNativeScaled` deployments ### Testing Unit Tests	2 months ago
Kunal Arora	445b6222c0	fix: `ArbL2ToL1Ism` will support msg.value (#4328) ... ### Description - Added support for msg.value by rearranging the `releaseValueToRecipient()` in the verify call ### Drive-by changes - uncommented out `test_postDispatch_revertWhen_notLastDispatchedMessage` test ### Related issues <!-- - Fixes #[issue number here] --> ### 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 Unit tests	3 months ago
Nam Chu Hoai	0779a23db6	refactor: Rename InterchainAccountRouter tests for easier reuse (#4336) ... ### Description Minor refactor of test	3 months ago
Kunal Arora	6f377f1743	feat: implement `OPL2ToL1Ism` contracts (#4319) ... ### Description Implementing the `OPL2ToL1Hook` and OPL2ToL1Ism` contracts for using the Optimism native bridge for sending messages from the L2 to L1. - Optimism needs double call encoding for the direct portal call because the portal itself calls the l1Messenger which then directs it to the ism. ### Drive-by changes None ### Related issues - fixes https://github.com/hyperlane-xyz/issues/issues/1346 ### Backward compatibility Yes ### Testing Unit testing with mocks for OP contracts	3 months ago
Yorke Rhodes	76f7ecafff	feat: attributable fraud for signers (#4284) ... ### Description Implements fraud proof attributions for checkpoint signers (validators). It is important to have a record of attribution in storage for slashing replay protection. We also maintain a [whitelist of merkle tree hooks](b14f997810/solidity/contracts/libs/CheckpointLib.sol (L50-L54)) such that validators cannot simply lie about this part of the checkpoint and circumvent fraud proofs. ### Backward compatibility Yes ### Testing Unit Tests	3 months ago
Kunal Arora	63abe564d4	feat: implementation of yield rebasing warp route contracts (#4203) ... ### Description - To reflect the rebased underlying asset, `_transferRemote` is overridden because we need to pass in the ERC4626 vault shares which on the synthetic `HypERC4626VaultYield` which change in value as the underlying vault shares accrue yield or receive a drawdown. - The exchangeRate (i.e., assets/shares) is encoded as metadata and sent to the synthetic token to calculate the value of the synthetic token. - On synthetic transfers, the overridden `ERC20.transfer()` function calculates the needed shares for the amount and transfers them instead. Design decisions - Do we need to rebase frequently? Yes, otherwise the exchangeRate on the synthetic token will be stale compared to the the actual vault claimable yield, which means a user who deposits later and right before the infrequent rebase will get disproportionate share of the yield. You can rebase by calling `rebase()` on the collateral token which makes a transferRemote call with 0 amount. - Why exchangeRate and not underlyingDepositedAmount on the synthetic? If a user withdraws (ie calls transferRemote on the synthetic) while a rebase is inflight, the underlyingDepositedAmount will get an inaccurate update (will be overreported and hence will derive inaccurate balance amounts on the synthetic. The exchangeRate doesn't change if the user is depositing or withdrawing. - Why override the `transfer` on the synthetic? Otherwise if a user A sends 100 USDC worth of shares to user B which has a exchange rate of 1.05, user A would have unwittingly sent 105 #tokens (5 excess). - What happens in a drawdown of the value? Once the user calls withdraws the the withdrawal they get out is accordingly discounted. If a user transfers on the synthetic, it will still gets the stale exchangeRate until rebase. - What if the owner of the vault charges a fee on the yield? In that case, you need to override the totalAssets to reflect the assets - feesByOwner and the warp route implementation will stay the same. One example implementation is `MockERC4626YieldSharing` and we have adequate tests to cover the functionality. - Rounding error? We're rounding down the exchangeRate as per the general recommendation for ERC4626 vault math. - Why not make the synthetic token an ERC4626 itself, given that there's some overlapping functionality? Even though, the assetsToShares and assetsToShares functions are the same, the synthetic token itself doesn't have an underlying token so it doesn't confer to the 4626 interface. - What if there are multiple synthetic tokens for a single rebasing collateral contract and what happens is the exchange rate is not in sync between the synthetics? Things to keep in mind for - How do I keep the exchangeRate in sync with the underlying vault? Keep calling rebase as a cron job frequently, or make a hook call in deposit, redeem, and withdraw function to automatically resync the exchangeRate. - 4626 math pitfalls: https://www.zellic.io/blog/exploring-erc-4626/ ### Drive-by changes - Renaming `HypERC20CollateralVaultDeposit` -> `HypERC4626OwnerYieldCollateral` ### Related issues - fixes https://github.com/hyperlane-xyz/issues/issues/1334 ### Backward compatibility Yes ### Testing Unit tests	3 months ago
Yorke Rhodes	cb404cb85c	feat: implement checkpoint fraud proofs (#4277) ... ### Description Implements 4 categories of checkpoint fraud proofs for use in future validator slashing protocol: 1. **premature**: if a checkpoint index is greater than the corresponding mailbox count, it is fraudulent 2. **non local**: if a checkpoint origin does not match the checkpoint's mailbox domain, it is fraudulent 3. **message id**: if a checkpoint message ID differs from the actual message ID (verified by merkle proof) at the checkpoint index, it is fraudulent 4. **root**: if a checkpoint root differs from the actual root (verified by merkle proof + root reconstruction) at the checkpoint index, it is fraudulent Notably this is implemented independently from signature verification to allow for multiple checkpoint signing schemes to reuse the same checkpoint logic. ### Related issues - Touches https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3799 - See https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/2431 for previous discussions ### Backward compatibility Yes ### Testing Unit testing with fixtures in `vectors/merkle.json` that are generated by the rust merkle tree and proof code	3 months ago
Kunal Arora	e151b5f9ac	feat: support Arbitrum L2->L1 message using CLI self-relay option (#3986) ... ### Description - trying for null metadata (in case where the L2->L1 call has been executed by a third party) otherwise waiting for the challenge period and then fetching the outbox proof using the `ArbL2ToL1MetadataBuilder` - deriving ArbL2ToL1 hook and ism - deriving custom hook from reciptISM when ismType == ARB_L2_TO_L1 ### Drive-by changes - modifying status command in CLI to write context for self-relaying messages ### Related issues - fixes https://github.com/hyperlane-xyz/issues/issues/1290 ### Backward compatibility Yes ### Testing Testnet from arbitrumsepolia -> sepolia - l2->l1 tx using selfrelay (if already preverified by 3rd party relayer) https://sepolia.etherscan.io/tx/0xa6af2355facedb102e1fb7275249ab714dadacd4264daa170801469cf22f2bc0 - l2->l1 tx using direct executeTransaction call https://sepolia.etherscan.io/tx/0x42bb0eefcbd0f78b5048052c911746d13da15a9fb9659775d5d9df1e116a2a3d --------- Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz> Co-authored-by: Yorke Rhodes <email@yorke.dev>	4 months ago
Kunal Arora	d396e2c553	feat: add `IStaticWeightedIsm` implementation (#4170) ... ### Description - Adding the static variation of the IWeightedIsm config where you configure validators with their corresponding weights and store it as bytecode. ### Drive-by changes None ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4160 ### Backward compatibility Yes ### Testing Fuzz tests	4 months ago
Kunal Arora	90598ad449	feat: remove outbox param from `ArbL2ToL1Ism` (#4178) ... ### Description - outbox contract can be derived from arbitrum's bridge contract so it's not useful to pass in ### Drive-by changes None ### Related issues None ### Backward compatibility Yes ### Testing Unit	4 months ago
Kunal Arora	f733379488	feat: support Arbitrum L2->L1 post dispatch hook (#3853) ... ### Description - Contract support for the enabling postDispatch hook with the Arbitrum nitro bridge from L2 to L1 - asynchronously via executeTransaction call to verifyMessageId first and then the relayer calling the verify message with no metadata (note: this supports msg.value) - synchronously via a single verify call which in turn calls executeTransaction on outbox to gets the message verified in the verifyMessageId (note: this doesn't support msg.value as ism.verify isn't payable) - Added a script for deploying the hook and ISM since the sdk doesn't support it yet. ### Drive-by changes - changing the type from "rate_limited_hook" to "RATE_LIMITED" to maintain consistency ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2846 ### Backward compatibility Yes ### Testing Unit and e2e with arbitrumsepolia->sepolia	5 months ago
Yorke Rhodes	6620fe6367	fix: eliminate branching from `TokenRouter` (#3878) ... ### Description Fixes bug in `TokenRouter` which dispatches messages to token recipient rather than address in `Router` table when hook overrides are provided. ### Drive-by changes Simplifies inheritance tree of `TokenRouter` > `GasRouter` > `Router` > `MailboxClient` ### Backward compatibility Yes ### Testing Unit Tests	5 months ago
Yorke Rhodes	a8a68f6f61	test: XERC20 and XERC20 Lockbox integration tests (#3849)	6 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	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
Yorke Rhodes	babe816f86	feat: support xerc20 and xerc20Lockbox in CLI (#3753) ... ### Description - Supports xERC20 and xERC20Lockbox in CLI and UI ### Drive-by changes - Rename XERC20Collateral to XERC20 ### Backward compatibility - Yes ### Testing - Manual	6 months ago
Yorke Rhodes	69de68a66e	Multisig and Aggregation ISM Metadata Encoding (#3701) ... ### Description - Implement multisig metadata encoding/decoding - Implement aggregation metadata encoding/decoding - Generates test metadata fixtures from solidity unit tests - Test encoders using fixtures ### Drive By - Make CI tests run topologically ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3449 - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3451 ### Backward compatibility Yes ### Testing Unit Tests	7 months ago
Paul-T.C-Yu	c9c5d37bab	add polygon hook and ism (#3038) ... ### Description - Add native polygon bridge hook and isms ### Related issues - Fixes #2847 - Documented with https://github.com/hyperlane-xyz/v3-docs/pull/31 ### Backward compatibility Yes ### Testing Unit Tests --------- Co-authored-by: NOOMA-42 <suncloud2203357667@gmail.com>	7 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
Chanh Le	c3276bd424	fix: `testNotOwnerEnrollRouter` (#3670) ... ### Description This PR fixes solidity's `testNotOwnerEnrollRouter`. ### Drive-by changes Only the unit test `testNotOwnerEnrollRouter`.	7 months ago
Yorke Rhodes	b6fdf2f7fe	Implement Connext xERC20 and Circle FiatToken collateral (#3618) ... ### Description - Implement XERC20 Collateral contract - Implement FiatToken Collateral contract ### Drive-by - Move vault collateral extension into token extensions folder ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3486 ### Backward compatibility - Yes ### Testing - Unit tests	7 months ago
Yorke Rhodes	c7007b0561	Implement trusted relayer ISM (#3363) ... ### Description - Adds an ISM that verifies whether the configured trusted relayer is the relayer of the message ### Related issues - Touches https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3371 ### Testing Unit Tests	7 months ago
Lee	0090f19e78	Support self-relay with IGP enforced on warp routes (#3566) ... ### Description Adds transferRemote overload ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Fixes #3525 ### Backward compatibility Yes ### Testing Unit Tests	8 months ago
J M Rossy	b63714ede8	Convert packages from CJS to ESM (#3531) ... ### Description - Reconfigure tsconfig and package.json for the utils, core, sdk, and helloworld packages - Update imports to use ESM syntax - Add patch for typechain to address [issue 898](https://github.com/dethcrypto/TypeChain/pull/898) ### Drive-by changes Improve package Readme content ### Related issues Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/1354 ### Backward compatibility No: package consumers using CJS will need to modify their imports or update to ESM. See [this popular gist](https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c#pure-esm-package) for details. ### Testing - [x] CI test coverage which invokes a lot of code via the CLI e2e - [x] Manually test in Warp UI by copying packages - [x] Publish beta packages and test in a few popular bundlers	8 months ago
Lee	24e1f86d25	Warp Route rate limiter hook & ISM (#3527) ... ### Description Adds rate limiting hook and ism to limit warp route transfers ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Fixes #2697 ### Backward compatibility Yes ### Testing Unit Tests --------- Signed-off-by: Paul Balaji <paul@hyperlane.xyz> Co-authored-by: Noah Bayindirli 🥂 <noah@primeprotocol.xyz> Co-authored-by: Kunal Arora <55632507+aroralanuk@users.noreply.github.com> Co-authored-by: Paul Balaji <paul@hyperlane.xyz> Co-authored-by: J M Rossy <jm.rossy@gmail.com> Co-authored-by: Trevor Porter <trkporter@ucdavis.edu> Co-authored-by: Daniel Savu <23065004+daniel-savu@users.noreply.github.com>	8 months ago
Kunal Arora	769f57d283	feat:ICA support in SDK (#3483) ... ### Description - Adding 'deployAccount` and `getCallRemote` helpers in InterchainAccount.ts for ease of use for the governor - Adding resolveAccountOwner/resolveInterchainAccountAsOwner wherever it's ambiguous if the owner is address (status quo) or AccountConfig (from this PR) - Added icaApp to HyperlaneDeployer for easier access to ICA ownership for any deployer - resolveAccountOwner vs resolveInterchainAccountAsOwner: the former is usable outside the deployers like the checker, etc whereas the latter is where we're already using the deployer and have the required localRouter already cached - includes the formatting change for the account verification file - owner needs casting in infra/config because of the type Address | AccountConfig type (cannot use resolveAccountOwner here which requires multiprovider) - Add quoteGasPayment with gas limit override to the ICA router contract ### Drive-by changes - HyperlaneDeployer.cacheAddressesMap appends addresses two keys deep instead of overridding the whole cache - callData in utils now supports value to be compatible with CallData[] in the ICA Router contract and generally for V3 which allows msg.value on dispatch - `appFromAddressesMapHelper` doesn't intersect multiprovider with contractMap chains (this causes issues if the contracts map doesn't include chains we may want to read something like domainId from like ismfactory or ICADeployer) - HyperlaneHookDeployer is now using the owner as owner vs it was earlier using the deployer earlier for unknown reason - ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3505 ### Backward compatibility No (call value) ### Testing Unit testing/e2e testing through governor --------- Signed-off-by: Paul Balaji <paul@hyperlane.xyz> Co-authored-by: Paul Balaji <paul@hyperlane.xyz> Co-authored-by: J M Rossy <jm.rossy@gmail.com> Co-authored-by: Trevor Porter <trkporter@ucdavis.edu> Co-authored-by: Daniel Savu <23065004+daniel-savu@users.noreply.github.com>	8 months ago
Lee	db85f8aaf4	Upgradable warp routes (#3474) ... ### Description Makes the following Warp Routes upgradable through CLI deployment ``` - FastHypERC20Collateral - FastHypERC20 - HypERC20 - HypERC20Collateral - HypERC20CollateralVaultDeposit - HypNative - HypNativeScaled - HypERC721Collateral - HypERC721 - HypERC721URICollateral - HypERC721URIStorage ``` - Adds `initialize()` to each contract - It mostly contains `_MailboxClient_initialize`, and any additional proxy specific constructor logic - Refactors - Update `GasRouterDeployer` to inherit from `ProxiedRouterDeployer` - Update `ProxiedRouterDeployer.routerContractName` to `abstract ProxiedRouterDeployer.routerContractName(): RouterKey` . - This allows child classes to specify their own contract name instead of being locked-in to a single name upon construction. Similar concept to the existing `ProxiedRouterDeployer.constructorArgs()` and `ProxiedRouterDeployer.initializeArgs()` - Update `router()` - Add function into `InterchainQueryDeployer` - Add function into `InterchainAccountDeployer` - Update to abstract function in `ProxiedRouterDeployer` - ### Drive-by changes ### Related issues Fixes #999 ### Backward compatibility - Should be backward compatible ### Testing - Updates contract unit tests - Manual testing through CLI and verified contracts	8 months ago
Kunal Arora	4f0ea4361e	feat: add quoteGasPayment to ICA router (#3460) ... ### Description - for easier offchain use, we can directly call the ICA router to fetch the quote needed for the dispatch. ### Drive-by changes None ### Related issues None ### Backward compatibility Yes ### Testing Unit	8 months ago
J M Rossy	adab1bec0c	Add code spellcheck CI job (#3467) ... ### Description Fix spelling mistakes and create codespell CI job. An extension of #3422 with the remaining mistakes fixed ### Backward compatibility Yes --------- Co-authored-by: miles <66052478+miles-six@users.noreply.github.com> Co-authored-by: Paul Balaji <paul@hyperlane.xyz>	8 months ago
Kunal Arora	d224c060d4	fix: send_value fuzz test for ICA (#3469) ... ### Description make sure we assume `value <= balance - gasQuote` in ICA tests ### Drive-by changes none ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3468 ### Testing fuzz	8 months ago
Kunal Arora	59e89afc5c	feat: add account -> owner mapping in ICA router (#3447) ... ### Description - added accountOwner mapping to the ICA router for easier tracking of remote owners for the transaction type inference by the AppGovernor ### Drive-by changes none ### Related issues none ### Backward compatibility yes ### Testing unit	8 months ago
Lee	ae0990a0b3	LayerZero Hook and ISM (#3102) ... ### Description - Implements LayerZero V1 and V2 hook with V2 ISM. - V2 ISM is backwards compatible i.e., V1 hook (which uses V1 endpoint to send) can send to V2 ISM (which uses V2 endpoint to receive). See [here](https://docs.layerzero.network/explore/migration#configuring-ultralightnode301) for configuration. - V2 uses `AbstractsMessageIdAuthorized*`. In. other words, hook passes messageId through LayerZero, which stores into ISM to be used when relayer calls `verify()` . - Includes unit test for both V1 and V2 hook and ISM. - V1 uses official LayerZero endpoint mock. ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Implements #2853 ### Backward compatibility Yes ### Testing Manual/Unit Tests	9 months ago