hyperlane-monorepo

Commit Graph

Author	SHA1	Message	Date
Yorke Rhodes	1baa12ebe7	Migrate from default ISM config object to cached addresses map (#2576 ) Caches the aggregation ISM addresses in the default ISM config for verification of governance proposal	1 year ago
Mattie Conover	d88fd4cd16	Agent Config Typescript Definitions (#2658 ) ### Description Updates the typescript definitions based on the rust code. This is the first in a series of PRs for handling Rust config streamlining. ### Drive-by changes - A couple of the core types I refined, please validate the definitions. ### Related issues Progress on #2215 Relates to #2491 ### Backward compatibility Yes ### Testing Unit Tests	1 year ago
Trevor Porter	f5b59c9a30	Remove zbctestnet (#2633 ) ### Description No longer needed because of the updated Eclipse plan - the RPC URL was shut down as well ### Drive-by changes no ### Related issues n/a ### Backward compatibility removes zbctestnet chain ### Testing deployed, builds	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
jaehunkim	018f0182a6	Fix hardhat test script in typescript/sdk/package.json (#2483 ) ### Description The previous `test:hardhat` script was not correctly finding and testing the `.hardhat-test.ts` files in the `src` directory. This commit updates the script to correctly find these files and pass them to the `hardhat test` command. Now, all Hardhat tests in the `src` directory and its subdirectories will be correctly run when the `test:hardhat` script is used. ### Testing Unit Tests Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>	1 year ago
Nam Chu Hoai	07d3acc5e9	Update testnet3 test recipients (#2582 )	1 year ago
Kunal Arora	c278ee75b9	Deploy AggregationISM to mainnet2 (#2563 )	1 year ago
Kunal Arora	ed7569d1ac	Deploy AggregationISM for rc kathy mainnet (#2541 ) ### Description - Deployed AggregationISM to rc mainnet2 - AggregationISM can take in env as a param (moved out of `testnet3/`) - Set as defaultISM for rc mainnet2 context ### Drive-by changes - Deployed `MerkleRootMultisigFactory` and `MessageIdMultisigFactory` for mainnet2 - RoutingISM deployment can run in parallel for each origin. ### Related issues Fixes #2478 ### Backward compatibility Backward compatible? Yes ### Testing Manual, see issue #2560	1 year ago
Yorke Rhodes	16eff8d4d6	Fix fork tests to handle timelock proxy owners (#2558 )	1 year ago
Kunal Arora	e1baef1d56	Deploy AggregationISM to testnet3 core (#2539 ) ### Description - Deployed the AggregationISM configured with default multisig validators on Testnet ### Drive-by changes - Fixed edge case of handling zero address for `connectionClient.interchainSecurityModule` - Dedupe setting ism in `HyperlaneDeployer.ts` ### Related issues - Fixes #2477 ### Backward compatibility Yes ### Testing Manual	1 year ago
Kunal Arora	a1ca86b350	Better config.interchainSecurityModule type handling for **deployer classes (#2537 ) ### Description I merge #2517 prematurely so here's an update with better string handling for config.interchainSecurityModule ### Drive-by changes None ### Related issues None ### Backward compatibility Yes ### Testing Manual --------- Co-authored-by: Yorke Rhodes <email@yorke.dev> Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>	1 year ago
Kunal Arora	e91be529db	AggregationISM set for rc kathy (#2517 ) ### Description - Using a separate set of validators for RC deployments and tests - Defining a recursive AggregationISM config which aggregates over two RoutingISMs, one for a set of MerkleRootMultisigISMs and one for a set of MessageIdMultisigISMs for each origin domain. ### Drive-by changes - Dployed MerkleRootMultisigISMFactory and MessageIdMultisigISMFactory for testnet3 in hyperlane context ### Related issues - Fixes #2224 ### Backward compatibility Backward compatible? Yes Any infrastructure implications? HyperlaneRouterChecker will fail silently if you provide an IsmConfig - #2534 ### Testing Manual Testnet --------- Co-authored-by: Yorke Rhodes <email@yorke.dev> Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>	1 year ago
J M Rossy	637172bb96	Update buildAgentConfig for backwards compat (#2525 ) - Change buildAgentConfig to create a combined new + old config schema - Add unit tests for buildAgentConfig utils	1 year ago
Yorke Rhodes	f5e98a745c	Publish 1.4.2 (#2523 ) ### Description Publish 1.4.2	1 year ago
Yorke Rhodes	a5209dbd9b	Remove legacy multisig prevention (#2522 ) ### Description Removes checks for legacy multisig deployment that are surfaced in `hyp-deploy`	1 year ago
J M Rossy	e1408fbc74	Bump versions to 1.4.1 (#2520 )	1 year ago
J M Rossy	f413a66749	Add solana and eclipse logos to SDK (#2515 ) - Add solana and eclipse logos to SDK - Fix chainId of solanatestnet	1 year ago
Yorke Rhodes	32715d8850	Deploys arbitrum timelock and fixes gnosis safe usage (#2518 ) ### Description - Deploys arbitrum timelock - Upgrades gnosis safe SDK to work with latest service versions ### Related issues - Fixes #2498 ### Backward compatibility Yes ### Testing Proposed to arbitrum safe with `check-deploy --govern` ![arbitrum_safe](https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/3020995/3c2aadd1-cfd4-4185-b806-1dff34134e0b)	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
Yorke Rhodes	364bf5943b	Fix core fork tests (#2508 ) ### Description - Move default ISM config to checker - Implement mailbox default ISM governance ### Drive-by changes - Make fork script kill child processes on exit - Removes default ISM configuration from core deployer ### Backward compatibility Yes ### Testing Core fork tests in CI	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
Yorke Rhodes	3182dc2328	Deploy icas again (#2513 ) ### Description Releases https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/2446 to testnet and mainnet ### Testing ICA fork tests passing Verified ![Screen Shot 2023-07-11 at 1 50 47 PM](https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/3020995/2cbd26c0-ed12-4ada-8fed-a9e9c056c045)	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
J M Rossy	395a069e0d	Refactor ChainMetadata types (#2491 ) ### Description - Refactor ChainMetadata types into new folder - Create metadata extensions for deployment artifacts, and agent config - Remove explicit ChainMetadata interface and infer from zod schema instead ### Related issues Implements new schema discussed in: - https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/1867 - https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/2203 - https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2214 Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2214 ### Backward compatibility No: users of chain metadata configs would need to slightly modify their shape (the `rpcUrl` field)	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
Trevor Porter	d12e3b966f	Deploy to solanadevnet & zbctestnet on testnet3 (#2412 ) ### Description * solanadevnet is on Solana Devnet, and zbctestnet is on the Eclipse/Zebec rollup testnet found at https://api.zebec.eclipsenetwork.xyz:8899/ * Deploys validators to our infra on testnet3 for `solanadevnet` and `zbctestnet`. These run on the `hyperlane` context. * Added the ability to set the docker image / tag for specific chain deployments. This way we can run the sealevel validators with their own image without affecting the other deployments * Deployed a sealevel-supporting relayer to rc that relays messages for solanadevnet and zbctestnet * Some minor changes to key management - e.g. the recent change to `getCloudAgentKey` wasn't effective because relayer keys don't ever specify their own chain * Added a `--protocol` flag to the get-key-addresses command so we can view keys for different protocols Everything works really well! messages are being delivered Validator sets: ``` - solanadevnet: { - threshold: 2, - validators: [ - '0xec0f73dbc5b1962a20f7dcbe07c98414025b0c43', - '0x9c20a149dfa09ea9f77f5a7ca09ed44f9c025133', - '0x967c5ecdf2625ae86580bd203b630abaaf85cd62', - ], - }, - zbctestnet: { - threshold: 2, - validators: [ - '0xf33cca115fd1bc888b31f5ce96c0277e3af31120', - '0xc1a44a2ff3379e0dfa4ccf7e8b98bdc3012721be', - '0x1ec68fea9a0698a0d2b396770e7d2d61d9a3e654', - ], - }, ``` ### Drive-by changes n/a ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2288 - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2289 ### 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?_ Deployed! --------- Co-authored-by: Asa Oines <asaoines@gmail.com>	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
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	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
Yorke Rhodes	d0b2a6a249	Fix sdk lint	1 year ago
Asa Oines	e317c6c85d	Sealevel chains should always use hex keys for relayers (#2402 ) ### Description This PR adds support for protocol-type awareness in infra. A new field `type` is added to chainMetadata. This field is inspected during key creation and relayer helm chart creation. Relayer keys for sealevel chains are set explicitly to always be hex keys. ### Drive-by changes None ### Related issues - https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2350 ### Backward compatibility _Are these changes backward compatible?_ Yes	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
Trevor Porter	186fcdab36	Existing deployment support in Router tooling, small ISM factory fixes (#2392 ) ### Description To accommodate warp routes that exist on EVM chains and other execution environments, we need the ability to enroll remote routers on EVM-based routers that weren't deployed by the router deployer. This adds a new optional `existingDeployment` property to the `RouterConfig`, which means that deployment will not be attempted to this chain, but it will be enrolled as a remote router on any contracts that are deployed to. The general flow looks something like: * Deploy the warp route contracts on all EVM chains, enrolling each other as routers * Deploy the warp route contracts on the alt execution environment chains, also configuring the existing EVM contract deployments as `existingDeployment`s so that they are enrolled as routers on the alt execution environment contracts * Now equipped with all the router addresses, any new non-EVM router addresses are configured as `existingDeployment`s, which now enrolls these routers on the EVM chains Note there's still a lot left to be desired even with this change -- e.g. much of the tooling expects the MultiProvider to include metadata (& even providers) for each and every chain. Because the MultiProvider is of course EVM only, things get a bit weird. For now, I've been able to deploy warp routes with configs relating to a sealevel chain successfully by just running a local Anvil instance and setting the RPC URL of the sealevel config to that anvil instance. We'll want to readdress this at some point, but for now I'd prefer to have a flow that just works and we can be more intentional about bigger deploy / tooling changes to support alt execution environments in the future This also includes some small changes to the ISM factory - because we werent actually waiting for the `enrollValidators` tx to succeed before trying `setThreshold`, the gas estimation of `setThreshold` would fail because the threshold of 1 exceeded the current on-chain validator set size of 0. It also sometimes resulted in nonce contention I was able to get everything in hyperlane-deploy working locally by having dependencies be local filepaths The order of operations for things iiuc looks like: 1. Merge this 2. Ship new SDK version 3. Update hyperlane-token to use this new SDK version 4. Ship new hyperlane-token version 5. Update hyperlane-deploy to use the new SDK version and the new hyperlane-token ### Drive-by changes none ### Related issues - partially 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?_ unit tests, ran deploy tooling	1 year ago
Mattie Conover	efad4e1326	Omniscient relayer infra (#2299 ) ### Description - Adds support for omniscient relayers - Updates config formats to allow better overideability by agent role - Enables deploying selected agents rather than having to deploy them all at once - Merges scraper scripts and configuration ### Drive-by changes Lots of cleanup was made in the infrastructure scripts and source as it was already being touched by the above. While this PR touches a lot of files, many of the changes are just because we have so many scripts and a small change to something they all use instantly can lead to many files changed. ### Related issues - Fixes hyperlane-xyz/issues#438 - Fixes hyperlane-xyz/issues#447 - Fixes #1664 ### 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 ### Testing _What kind of testing have these changes undergone?_ Manual Unit Tests	1 year ago
Yorke Rhodes	8d9ee49f67	Fix env tests for new multisig variants (#2283 ) Fixes env tests failing in CI https://github.com/hyperlane-xyz/hyperlane-monorepo/actions/runs/5081007361/jobs/9128835519. Adds logging to ism factory deployer and ism deployments.	2 years 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
Nam Chu Hoai	85a1bf0fba	Deploy LL + CircleBridgeAdapter to mainnet (#2166 ) ### Description Deploy LL + CircleBridgeAdapter to mainnet with the relevant changes and artifacts	2 years ago
J M Rossy	355b5ed44e	Bump versions to 1.3.4 (#2167 )	2 years ago
Nam Chu Hoai	16c2c7eb75	Deploy gnosis IQS (#2044 ) ### Description PR deploys the iqs router on gnosis (deployed and verified manually)	2 years ago
Nam Chu Hoai	6bac228efb	Verify proxy even if implementation is verified (#2164 ) ### Description `ContractVerifier` would skip the proxy verification if the implementation was already verified. This changes it so that we will still attempt proxy verification.	2 years ago
Nam Chu Hoai	482c8e77f5	Minor fixes to get LL deploys running smoothly (#2125 ) ### Description This PR makes some minor modifications to the deployment structure for the Liquidity Layer. The most important thing is the embedding of the `proxyAdmin` addresses in the LL addresses file which is not pretty, but I did not want to put it in the SDK right now either, but could be convinced. In the process of running this, the LL router IGPs have been updated which is non-material, but otherwise the deploy script runs as a no-op now.	2 years ago
J M Rossy	84d7e72910	Various SDK tweaks and fixes (#2129 ) ### Description - Rename RpcPagination fields in ChainMetadata for clarity - Add optional maxBlockAge field to RpcPagination - Use RetryProvider and StaticJsonRpcProvider by default in MultiProvider - Improves RetryProvider and fixes #2115 - Enable users to customize MultiProvider provider creation behavior - Replace `ExplorerFamily` with template literal type - Improve ChainMetadata validation - Add back hyperlaneContractAddresses ### Backward compatibility No, small breaking changes: - Rename RpcPagination to RpcPaginationOptions - Rename providerBuilder to defaultProviderBuilder - Remove RetryProvider - Remove unused events functions, including getEvents, queryAnnotatedEvents, Annotated, and TSContract	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	3b121e872d	Publish 1.3.3 (#2144 ) Publishes 1.3.3, moving the submodules back to their respective mains.	2 years ago
Asa Oines	49b345854b	Add static fromAddressesMap constructor to apps (#2136 ) ### Description Adds a third constructor. Allows apps to be constructed from: - Environment name - ContractsMap - AddressesMap ### Drive-by changes None	2 years ago
Asa Oines	e756732964	Use proper ISM in ICA contracts (#2128 ) ### Description Currently, ICAs are configured without an ISM, which results in them falling back to the mailbox default. Instead, they should delegate security to whichever ISM was specified in the message. This PR updates the deployer to deploy the proper ISM by default, and the checker/governor with code that will allow the existing deployments to move to that ISM. ### Drive-by changes - My formatter seems to be making changes to src/sdk/index.ts ### 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
Asa Oines	f30666eea3	Deploy ISM factories to testnet/mainnet (#2135 ) ### Description Ran: ``` yarn ts-node scripts/deploy.ts -m ism ``` ### Drive-by changes None	2 years ago
Asa Oines	4f0fdd1e8f	Use arbitrary addresses map in filterAddressesMap (#2131 )	2 years ago

1 2 3 4 5 ...

292 Commits (e582357de881d2b07bfe439ddb3d241093357de3)