hyperlane-monorepo

Commit Graph

Author	SHA1	Message	Date
Daniel Savu	523a66219d	Validators on RC (#2461 ) ### Description Allows for deploying validators in the RC context, on both `testnet3` and `mainnet2` ### Drive-by changes Initially took the approach in https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/2372 to refactor out the validator keys in a dedicated file so it's easier to modify / add in the future. However, these are not expected to ever change so now the keys are hardcoded in `validators.ts`. There is a cyclic dependency here, because `scripts/get-key-addresses.ts` depends on the hardcoded addresses in `validators.ts` to know how many validator addresses to read from AWS, but to know which addresses to hardcode you need to first run the `get-key-addresses` script. This PR doesn't fix it but I'm mentioning it for future reference. Also copy-pastes a change from one of @tkporter's open PRs in `typescript/infra/src/agents/aws/validator-user.ts`, to get around an aws bucket creation error. ### Related issues - Fixes https://github.com/hyperlane-xyz/issues/issues/485 ### 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 that I know of - but this PR does impact deployments in general. Maybe double check there's enough memory and other hardware resources to support the new validators? ### Testing _What kind of testing have these changes undergone?_ Manual - checked the kubernetes pods and S3 checkpoints. --------- Co-authored-by: Trevor Porter <trkporter@ucdavis.edu> Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz> Co-authored-by: Asa Oines <asaoines@gmail.com>	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
Asa Oines	2c4b861204	Add support for new signed checkpoint types in verify-validators (#2516 ) ### Description This makes it easy to see who is running the latest version of the validator.	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
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	fc5698d7af	Fix compiler warning on token contracts (#2447 ) ### Description Fixes `Warning: This declaration shadows an existing declaration.` on token `yarn build`	1 year ago
Yorke Rhodes	aab8f19f8a	Add codecov github action (#2449 ) ### Description Adds simplest viable codecov setup	1 year ago
Trevor Porter	b98d882efe	Use configured collateral token metadata (#2445 ) ### Description Just copying the changes from https://github.com/hyperlane-xyz/hyperlane-token/pull/73, which I unfortunately didn't get in before the absorption ### Drive-by changes _Are there any minor or drive-by changes also included?_ ### Related issues In the name 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?_ Unit Tests, used it in hyperlane-deploy when deploying synthetic tokens relating to a collateral warp route that lives on Solana	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	f235e4ce0f	Add solhint to helloworld and token	1 year ago
Yorke Rhodes	d0b2a6a249	Fix sdk lint	1 year ago
Yorke Rhodes	ebaf652192	Fix builds and tests	1 year ago
Yorke Rhodes	d9cd552c62	Merge CI configs	1 year ago
Mattie Conover	0ed4e84406	Deployed scraper (#2432 ) ### Description Updated the scraper to fix a metric issue. ### Drive-by changes None ### Related issues ### 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	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
Nam Chu Hoai	73651d1e46	Scale down gnosis validators to 1 (#2407 ) Scale down gnosis validators to 1	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
Yorke Rhodes	feb6d2b4e9	Release new validators internally (#2390 ) ### Description Updates hyperlane context mainnet2 and testnet3 validator image tags (to whats already deployed)	1 year ago
Asa Oines	c445869793	Deploy scraper to testnet3 (#2351 ) ### Description With tag `2deb9b8-20230602-205342`	1 year ago
Asa Oines	663115d716	Deploy mainnet scraper (#2376 ) ### Description Updates the deployment to pick up #2375	1 year ago
Nam Chu Hoai	60ce3a5f4b	Deploy testnet3 key funder with quorum (#2307 ) Deploy testnet3 key funder with quorum	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	2 years 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
Asa Oines	63562c7211	Refactor agent event indexing (#2246 ) ### Description This PR refactors event indexing in the agents, allowing similar logic to be shared across multiple event types (i.e. messages, deliveries, gas payments) and database types (i.e. the Relayer rocks DB and Scraper SQL DB). Furthermore, it adds new syncing modes by way of `MessageSyncCursors` that take advantage of the monotonically increasing dispatched message nonce to sync more intelligently. ### Drive-by changes - Fixes a bug in the existing cursor that caused the same block range to be indexed three times - Modifies kathy to get rid of the idea of "rounds", just sends messages with a sleep in between - Minor modifications to the e2e test for performance - Expand macros in settings - Add scraper to e2e test ### Opportunities for improvement - We can further reduce RPC usage (or improve latency) by sharing the view of the latest finalized block number between cursors - We can speed up the effective time for (a relayer to start deliving messages \| the scraper to scraper recent events) by creating forward/backward cursors for gas payments and deliveries where the backwards cursor terminates at index_settings.from - We can remove the need for index_settings.from by terminating backwards cursors based on the block number that the first message was dispatched at ### Related issues - Fixes #[issue number here] ### 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 --------- Co-authored-by: Mattie Conover <git@mconover.dev>	2 years ago
Trevor Porter	9743d74272	Deploy key funder (#2206 ) ### Description Deploy key funder to include #2190 ### Drive-by changes no ### 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?_ Deployed	2 years ago
Mattie Conover	5e38cdf31a	Omniscient Relayer (#2195 ) ### Description Adds support for running a relayer which delivers messages from multiple origin chains instead of just one origin chain. ### Drive-by changes _Are there any minor or drive-by changes also included?_ - The E2E pipeline got a major re-work. It both runs faster and also tests the new changes. - SerialSubmitter has been abstracted to support additional operation types such as oracle updates - SerialSubmitter has been updated to actually confirm a transaction was included and is safe from re-orgs - SerialSubmitter has been updated to have higher throughput by pipelining operations ### Related issues - Blocked by #2148 - Fixes #1899 ### 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 Unit Tests	2 years ago
Trevor Porter	1e43a3e1de	Lower L2 funding multiplier from 10 to 5 (#2190 ) ### Description We increased the desired balances for relayers on L2s significantly to 0.5. The target key funder balance for L2s was previously 10x the relayer target balance - we probably shouldn't be bridging over 5 ETH. This lowers the multiplier to 5, so that we shoot for a 2.5 ETH key funder balance on L2s ### Drive-by changes none ### 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?_ None	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
Yorke Rhodes	1375a994d2	Decrease kathy frequency and make relayer target balance buffers larger (#2165 ) ### Description Config changes for kathy and key funder ### Related issues - Fixes https://github.com/hyperlane-xyz/issues/issues/440 ### Backward compatibility Yes ### Infrastructure - Deployed key funder on mainnet - Deployed kathy on mainnet and testnet ### Testing None	2 years ago

1 2 3 4 5 ...

833 Commits (e0d8eb375fb2cc9507cf7f8f734797e12ecadcda)