hyperlane-monorepo

Commit Graph

Author	SHA1	Message	Date
Yorke Rhodes	e582357de8	Make Domain Routing ISM enumerable (#2644 )	1 year ago
Kunal Arora	f01dfd005f	Add custom error message for when gasOracle not configured for domain in IGP (#2656 ) ### Description - Better error message for when gas oracle for a specific domain isn't configured ### Drive-by changes - None ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2438 ### Backward compatibility Yes ### Testing - Unit tests	1 year ago
J M Rossy	d901ca2c6f	Minimal multi-protocol SDK support (#2529 ) ### Description - Create MultiProtocolProvider - Create ProviderType enum and TypedProvider - Add viem, solana, and ethers6 dev deps to SDK - Upgrade Typescript and Eslint across monorepo (required for Viem) - Break out metadata mgmt code into new ChainMetadataManager class - Implement basic MultiProtocolApp and MultiProtocolRouterApp - Create Evm and Sealevel router adapters - Refactor contract types into separate file to avoid circular dep ### Related issues https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2503 ### Backward compatibility Yes	1 year ago
J M Rossy	465112db6f	Refactor utils package (#2550 ) ### Description - Reorganize code into separate files - Move in utils from other packages - Fix export structure - Add multi-protocol address utils ### Drive-by changes Lint fix in token package ### Related issues Pre-req for #2503 ### Backward compatibility No, some exports have been removed from the SDK and moved to utils	1 year ago
Yorke Rhodes	aa92fe37db	Fix crosschaincall duplicate warning (#2532 ) ### Description Fixes ``` duplicate definition - NotCrossChainCall() ```	1 year ago
Alex	da25b06254	CCIP Read ISM (#2398 ) ### Description CCIP Read ISM implementation, - [x] Contracts - [x] Relayer - [x] Example HTTP backend ### Drive-by changes _Are there any minor or drive-by changes also included?_ ### Related issues - Fixes #[2211] ### Backward compatibility _Are these changes backward compatible?_ Yes, relayers will skip messages they can't handle. _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ Yes, relayers won't be able to submit messages that have a CCIP Read ISM. ### Testing _What kind of testing have these changes undergone?_ - [x] Manual - [x] Unit Tests ### General approach - [x] Get a basic [CCIP Read implementation working](https://github.com/AlexBHarley/permissionless-chainlink-feeds/tree/main/contracts) - [x] Build a [mock service that serves CCIP Read compatible data](https://github.com/AlexBHarley/permissionless-chainlink-feeds/tree/main/apps/api) - [x] Update the Relayer to support CCIP Read ISMs	1 year ago
Yorke Rhodes	f5e98a745c	Publish 1.4.2 (#2523 ) ### Description Publish 1.4.2	1 year ago
J M Rossy	e1408fbc74	Bump versions to 1.4.1 (#2520 )	1 year ago
Kunal Arora	d69a3f639a	No metadata relayer support for hooks (#2495 ) ### Description - Adding `NoMetadataRelayer` moduleType which returns an empty `vec![]` on `MetadataBuilder::build()` - Adding `HyperlaneHookDeployer` which lets you deploy the hook, ISM and a testRecipient which specifies to use the `AbtractNativeISM` ### Drive-by changes - none ### Related issues - Accompanies #2316 - Fixes https://github.com/hyperlane-xyz/issues/issues/379 for Optimism - Related to adding native hooks to Mailbox V3 https://github.com/hyperlane-xyz/issues/issues/486 ### Backward compatibility Backward compatible? Yes Tooling changes needed? Need to update node to ^18 ### Testing - Manual on testnet3	1 year ago
J M Rossy	5edf2ae33f	Bump versions to 1.4.0 (#2510 ) Bump versions and export more types from token package	1 year ago
Kunal Arora	7918a320c9	reset to mapping of mapping of messageiD and adding crosschain (#2506 ) ### Description - Reverting to using `mapping(bytes32 => mapping(bytes32 => bool)) public verifiedMessageIds` to prevent a malicious party from changing sender addresses in the ISM and causing liveness failiure for the honest party. - Adding `CrossChainEnabledOptimism` libraries and contracts locally instead of importing from OpenZeppelin's library (removed) - Renaming `AbstractNativeISM` to `AbstractHookISM` for flexibility and clarity. ### Drive-by changes Nope ### Related issues Fixes #2497 ### Backward compatibility Backward compatible? Yes Any infrastructure implications? No ### Testing Unit Tests	1 year ago
Alex	0ddaf1c5cc	Fix incorrect getRemoteInterchainAccount derivation (#2446 ) ### Description A minor change to how we deploy InterchainAccountRouter's and a fix for remote ICA address derivation. The fix is outlined clearly in #2383 by Nam but essentially by assigning the `implementation` & `bytecode` variables in the constructor of `InterchainAccountRouter`, we are unable to correctly access them in `getRemoteInterchainAccount` if using a proxy. By moving initialisation of these variables to `initialize` we correctly store the values in the proxy storage, not the implementation storage. ### Drive-by changes The `InterchainAccountRouter` should no longer be used unproxied. ### Related issues - Fixes #2383 ### Backward compatibility No, new ICA deploy ### Testing - [x] Unit Tests --------- Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>	1 year ago
Yorke Rhodes	e3e7a0aeb9	deploy middlewares (#2496 ) ### Description - Fix middleware addresses - Deploy ICA on testnet - Deploy IQS on testnet - Deploy middlewares to mainnet ### Drive-by changes - Add more tx overrides fixes to deployer ### Related issues - Fixes #2455 ### Backward compatibility No, new addresses ### Testing Fork tests	1 year ago
Kunal Arora	7c872bc449	5164 hook support (#2471 ) ### Description - Adding support for any ERC-5164 compatible bridge adapter to be added as a hook. See https://eips.ethereum.org/EIPS/eip-5164 for more details on the EIP and https://github.com/MultiMessageAggregation/multibridge for adapter implementations for different vendors. ### Drive-by changes - Switched mapping(bytes32 => mapping(address => true) to mapping(bytes32 => bytes) for verifedMessageIds because the last boolean is redundant in the AbtrsactNativeISM contract. ### Related issues - Fixes #2417 ### Backward compatibility _Are these changes backward compatible?_ Yes _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing _What kind of testing have these changes undergone?_ Unit Tests	1 year ago
Yorke Rhodes	60f321f452	docs: elaborate on censorship resistance of two ISMs. (#2474 ) ### Description Changes from https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/2425 --------- Co-authored-by: serejke <serejke.best@gmail.com>	1 year ago
Yorke Rhodes	e92d3410fc	Add markdown docs generation (#2437 ) ### Description Adds markdown doc generation to solidity and token package May be preferable to our gitbook contract API docs	1 year ago
J M Rossy	7ff83bbd0b	Fix checkConfig in HyperlaneRouterDeployer (#2469 ) - Fix checkConfig in HyperlaneRouterDeployer - Bump packages to 1.3.7	1 year ago
Daniel Savu	7889385501	Relayer aggregation ism (#2411 ) ### Description Adds AggregationISM support to the relayer, by adding the scaffolding, sub-ism metadata fetching, and custom metadata encoding. ### Drive-by changes - adds `dry_run_verify(...)` to the `InterchainSecurityModule` trait and implements it for `EthereumInterchainSecurityModule` - changes the default ISM in the test environment from `routingIsm(multisigIsm)` to `routingIsm(aggregationIsm([multisigIsm, messageIdIsm], threshold = 1))` ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/1757 ### Backward compatibility _Are these changes backward compatible?_ Yes _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing The AggregationISM metadata encoding is tested using unit tests whose input was taken from the tests in `AggregationIsm.t.sol`, by printing the individual ISM metadatas and the final metadata. The overall AggregationISM is tested with the `run-locally` script.	1 year ago
Trevor Porter	35332f464c	Release 1.3.6 (#2451 ) ### Description Released 1.3.6, mostly to include #2445 and #2402 ### Drive-by changes n/a ### Related issues In the name of https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2366 ### Backward compatibility _Are these changes backward compatible?_ Yes _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing _What kind of testing have these changes undergone?_ None	1 year ago
Yorke Rhodes	2e2e0ffadb	Add proxy upgrade timelocks to deployer and checker (#2151 ) ### Description Adds `TimelockController` deployment code to `CoreDeployer`. If a `upgradeTimelockDelay` is configured on `CoreConfig`, this contract will be deployed. The `ProxyAdmin` will be owned by this contract, and the configured `owner` will have proposer, executor, and canceller roles on the timelock. ### Drive-by changes Configures `arbitrum` with `upgradeTimelockDelay: 7 days`. ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/1717 - Fixes https://github.com/hyperlane-xyz/issues/issues/503 ### Backward compatibility Yes ### Testing SDK unit tests and fork tests against arbitrum	1 year ago
Yorke Rhodes	aab8f19f8a	Add codecov github action (#2449 ) ### Description Adds simplest viable codecov setup	1 year ago
Yorke Rhodes	fcb1bebb96	Bump hardhat and solidity-coverage versions (#2433 ) ### Description Bumps solidity coverage and hardhat versions to (hopefully) fix CI coverage flakiness Also bumps node version following https://github.com/NomicFoundation/hardhat/pull/4075	1 year ago
Kunal Arora	445da4fb0d	Adding Optimism native bridge support (#2316 ) ### Description - Adds support for the native Optimism bridge (L1->L2) to send messageID to be verified by the custom ISM on the rollup. - Only the smart contract component. - Outside Mailbox and needs to be called separately. - Uses Openzeppelin's CrossChainEnabled pattern for ensuring the right cross chain sender address. ### Drive-by changes - None ### Related issues - Fixes https://github.com/hyperlane-xyz/issues/issues/379 - Opens https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2409 - Related to https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2381 ### Backward compatibility - Needs modifying the relayer to read OptimismISM's storage to wait for `receivedEmitters` mapping to get updated before retrying `process` on the mailbox. ### Testing - Unit Tests with Foundry forks and Optimism's L1-L2 messenger contracts. --------- Co-authored-by: Asa Oines <asaoines@gmail.com>	1 year ago
Trevor Porter	4bf065548c	Bump to 1.3.5 (#2401 ) ### Description Releases 1.3.5, mostly to include #2392 ### Drive-by changes n/a ### Related issues - Part of #2366 ### Backward compatibility _Are these changes backward compatible?_ Yes _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing _What kind of testing have these changes undergone?_ None	1 year ago
Yorke Rhodes	50f04db1fa	Make merkle proofs optional on multisig ISM (#2173 ) ### Description Validators currently sign `(root, index)` checkpoints and during verification, a `message` is passed as calldata, an `id()` is derived, and a `proof` of `id()` at `index` in `root` is verified This provides “all or nothing” censorship resistance guarantees because a validator can only sign roots to allow any contained messages to be processed. We have considered alternatives where validators sign `message` directly and we lose censorship resistance in exchange for eliminating merkle proof verification gas costs. However, if validators sign `(root, index, message)` tuples, we can skip merkle proof verification on the destination chain while still maintaining censorship resistance by providing two valid metadata formats: 1. existing validator signatures and merkle proof verification of inclusion 2. including merkle proof verification for pathway where validators are censoring `message` It’s worth noting the validator is required to index event data to produce this new signature format. However, this does not require historical indexing and new validators being spun up can simply begin indexing from tip. See https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/2187 for validator changes See https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/2248 for relayer and e2e test changes ### Drive-by changes Merkle index also optional ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2192 ### Backward compatibility - new ISM deployment is necessary (we could upgrade implementation in theory) - Validator and relayer upgrades ### Testing Unit (fuzz) Tests, E2E tests	2 years ago
Asa Oines	ec63ed19c5	Fix CI flakiness (#2269 ) ### Description - Don't panic if E2E test fails to fetch a metric - Run coverage commands sequentially ### Drive-by changes - Cleans up some lint errors in forge tests	2 years ago
Asa Oines	1e9d0be9b3	Fix DomainRoutingIsm tests (#2255 ) ### Description Fixes a bug in the DomainRoutingIsm tests that curiously only started showing in CI a few days ago. ### Drive-by changes None	2 years ago
J M Rossy	355b5ed44e	Bump versions to 1.3.4 (#2167 )	2 years ago
Asa Oines	6b058e7014	Add checkConfig to HyperlaneRouterDeployer (#2156 ) ### Description Adds a pre-deploy check to HyperlaneDeployer, with an implementation for HyperlaneRouterDeployer that does a best-effort check that the ISM and IGP are properly configured for each chain. ### Drive-by changes - Move TestIsm to TestMultisigIsm for compatibility with pre-deploy checks ### Related issues - Fixes #2038 ### Backward compatibility _Are these changes backward compatible?_ Yes _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing _What kind of testing have these changes undergone?_ Manual	2 years ago
Asa Oines	5f72e7fd92	Use node 16 when compiling contract types (#2146 ) ### Description To address https://github.com/NomicFoundation/hardhat/issues/3877 Also reverts #2140	2 years ago
Asa Oines	3b121e872d	Publish 1.3.3 (#2144 ) Publishes 1.3.3, moving the submodules back to their respective mains.	2 years ago
Yorke Rhodes	0903fe87b3	Try always building typechain types in core (#2140 ) - Always build typechain artifacts	2 years ago
Yorke Rhodes	60f7737a46	Try adjusting core tsconfig (#2138 ) Fixes `yarn build` failing on `main` https://github.com/hyperlane-xyz/hyperlane-monorepo/actions/runs/4765379482/jobs/8471042324	2 years ago
Asa Oines	2900737c8f	Add HyperlaneIsmFactoryDeployer (#2068 ) ### Description This PR separates ISM deployment from HyperlaneCoreDeployer. Furthermore, it adds support for Routing and Aggregation ISM deployment via a recursive IsmConfig type. The MultisigIsm address is removed from the artifacts. Instead, the default ISM will be fetched at run time and compared against a provided IsmConfig. If there are any differences, a new defaultIsm will be deployed. ### Drive-by changes None ### Related issues None ### Backward compatibility _Are these changes backward compatible?_ No _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ Yes, the default LegacyMultisigIsms will no longer be supported by the checker. The governance script will instead deploy a routing ISM and set that as the default ISM. ### Testing _What kind of testing have these changes undergone?_ Unit Tests	2 years ago
Asa Oines	1d0e067166	Add relayer support for MultisigIsm and RoutingIsm (#2074 ) ### Description This PR adds support in the relayer for MultisigIsm (non-legacy) and RoutingIsm metadata building. AggregationIsm support is not yet implemented. ### Drive-by changes None ### Backward compatibility _Are these changes backward compatible?_ Yes _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing _What kind of testing have these changes undergone?_ end-to-end	2 years ago
Asa Oines	f8d645e580	Add RoutingIsm (#1985 ) ### Description This PR adds `IRoutingIsm` and three implementations: - AbstractRoutingIsm, which folks building RoutingIsms can inherit from - DomainRoutingIsm, which routes based on message origin - InterchainAccountIsm, which routes based on the ISM in the InterchainAccountMessage ### Drive-by changes - Some related testing changes ### Related issues - Fixes #1521 ### Backward compatibility _Are these changes backward compatible?_ Yes _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing _What kind of testing have these changes undergone?_ Unit Tests	2 years ago
Yorke Rhodes	6d40e193b1	Fix contracts test coverage instrumentation (#2089 ) ### Description - Fixes bugs in solidity test coverage ### Drive-by Changes - Removes check for minimum coverage ### Related issues - Touches https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/1841 - Touches https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/1840 ### Testing See `coverage-sol` job or try `yarn coverage` locally for HTML breakdown	2 years ago
Asa Oines	267cf80a32	Publish 1.3.2 (#2086 ) ### Description Publishes 1.3.2 for utils/core/sdk, updates helloworld and token to their respective main branches and then moves them to 1.3.2 ### Drive-by changes None	2 years ago
Yorke Rhodes	55f40ad760	Merge audit v2 remediation to main (#1727 ) ### Description Merge [`audit-v2`](https://github.com/hyperlane-xyz/hyperlane-monorepo/releases/tag/audit-v2) into `main` See [changelog](`034e75b632`...audit-v2)	2 years ago
Yorke Rhodes	25dfcbaed7	Bump to 1.3.1 (#2072 )	2 years ago
Asa Oines	96e03b1681	Remove Create2Factory and associated deployer code (#2064 ) ### Description As discussed offline, the complexity of maintaining consistent addresses across chains is no longer worth it, especially as consistent addresses cannot be maintained across PI chains. ### Drive-by changes - Move governors into infra/src/govern - Take initialization args list as opposed to abi encoded args in deployer - Do not initialize IGP in the constructor since we need to initialize the proxy ### Related issues - Fixes #2040 ### Backward compatibility _Are these changes backward compatible?_ Yes _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing _What kind of testing have these changes undergone?_ None	2 years ago
Trevor Porter	8fb6384e34	Catch more errors in Portal relayer (#2049 ) ### Description Sometimes get annoying stuff like: ``` {"chain":"goerli","level":"info","message":"Processing chain"} TypeError: response.result.map is not a function at LiquidityLayerApp.<anonymous> (/hyperlane-monorepo/typescript/sdk/src/middleware/liquidity-layer/LiquidityLayerApp.ts:93:28) at Generator.next (<anonymous>) at fulfilled (/hyperlane-monorepo/typescript/sdk/dist/middleware/liquidity-layer/LiquidityLayerApp.js:5:58) at runMicrotasks (<anonymous>) at processTicksAndRejections (node:internal/process/task_queues:96:5) ``` ### Drive-by changes n/a ### Related issues n/a ### Backward compatibility _Are these changes backward compatible?_ Yes _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing _What kind of testing have these changes undergone?_ ran locally	2 years ago
Asa Oines	e87095dc18	Release 1.3.0 (#2056 ) ### Description This PR releases v1.3.0 of utils, core, and SDK.	2 years ago
Asa Oines	f25feecfa7	Scaffolding for multiple ISM types in the relayer (#2028 ) ### Description This PR adds scaffolding in the relayer to support building metadata for multiple ISM types. To add a new ISM type: - Add a new implementation of MetadataBuilder for that type - Add the type to the SupportedIsmTypes enum - Add the type to the match statement in BaseMetadataBuilder ### Drive-by changes None ### Related issues - #1757 ### Backward compatibility _Are these changes backward compatible?_ Yes _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing _What kind of testing have these changes undergone?_ E2E tests	2 years ago
Asa Oines	63558af85d	Use interfaces in agents (#2022 ) ### Description Move agents to use contract interfaces artifacts rather than the artifacts themselves. This ensures we don't anything that we can't guarantee is in every implementation of that interface. Particularly relevant for IGPs and ISMs. ### Drive-by changes - Moves `solidity/interfaces` to `solidity/contracts/interfaces` so that their artifacts can be used in `update_abis.sh` ### Related issues - #1757 ### Backward compatibility _Are these changes backward compatible?_ Yes _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing _What kind of testing have these changes undergone?_ None	2 years ago
Yorke Rhodes	6f7495320b	Regenerate test fixtures and unskip hardhat tests (#2035 )	2 years ago
Asa Oines	f8b04029ac	Fix flaky solidity test (#2013 ) ### Description It's failing during certain fuzzer conditions b/c the assertion is made before the assumption.	2 years ago
Asa Oines	e8d90775f7	Add Aggregation ISM (#1737 ) ### Description This PR introduces the Aggregation ISM, which requires interchain messages to be verified by an m-of-n ISM set. This PR also introduces a new MultisigISM, which does not make use of the "commitment" optimization in its metadata. The previous MultisigISM has been moved to LegacyMultisigISM. Both AggregationISM and MultisigISM have abstract contracts that require `valuesAndThreshold` implementations. This PR implements versions with static m-of-n sets, using the EIP-3448 MetaProxy standard. These implementations are intended to be combined with a future RoutingISM implementation to replace LegacyMultisigISM. ### Drive-by changes - genhtml in solidity code coverage ### Related issues - Fixes #1522 ### Backward compatibility _Are these changes backward compatible?_ Yes ### Testing _What kind of testing have these changes undergone? Unit Tests	2 years ago
Asa Oines	f5a74006ec	Add non-struct API for IQS and ICA middlewares (#1989 ) ### Description This PR adds functions to the ICA and IQS middlewares that do not take complex types. These simpler interfaces lower the barrier to entry for users, especially for those using tooling that does not support structs well (e.g. etherscan, tally) ### Drive-by changes - Rename destinationDomain -> destination - Remove messageId from InterchainCallDispatched, rename to RemoteCallDispatched ### Related issues None ### Backward compatibility _Are these changes backward compatible?_ Yes _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing _What kind of testing have these changes undergone?_ Unit Tests	2 years ago
Asa Oines	7f5d50ee9c	Interoperable Interchain Accounts (#1832 ) ### Description This PR introduces a version of Interchain Accounts that is fully interoperable with any compatible contract deployed on a remote chain. Rather than follow the previous `Router` pattern in which destination contracts were hard coded by the deployer, this version allows the user to optionally specify which destination contract should receive the interchain account message. In order to make this secure, interchain accounts are additionally name spaced by ISM and origin router. Note that this is not feature-complete until paired with a RoutingISM that switches based on the ISM included in the message ### Drive-by changes - Creates the `IRouter` and `IHyperlaneConnectionClient` interfaces - Moves middleware interfaces into their own directory - Moves middleware libs into their own directory - Changes `InterchainCallMessage` -> `InterchainQueryMessage` now that it's unused by anything else ### Related issues - Fixes #1747 - Fixes #1969 ### Backward compatibility _Are these changes backward compatible?_ No _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing _What kind of testing have these changes undergone?_ Unit Tests	2 years ago

... 3 4 5 6 7 ...

601 Commits (3ce70725ee62069272f6de51987fbc8a4b1ee7d6)