hyperlane-monorepo

Commit Graph

Author	SHA1	Message	Date
Kunal Arora	cf82687507	feat:remove create-key circular dependency (#3159 ) ### Description Diagnosis: circular dependency created by igp requiring multisig size and threshold for building coreConfig which is needed while creating new keys. This arises in the scenario where you add the chain to chainMetadata and not to defaultMultisigConfigs (say newChainConfigs) - separated agents and helloworld configs from core and segregated scripts for `core-utils.ts` and `agent-utils.ts` for avoiding loading of envConfig.coreConfig - add argv commands to prompt for new chains or updated chains and validator/threshold combo: `yarn ts-node scripts/create-keys -e testnet4 --context hyperlane --new-chains basesepolia=2/3` (here 2 is desired threshold and 3 is desired multisig set size) - if you provide a newChainConfigs chain and don't supply an argv, the create-keys script will revert - persist addresses in gcp (already present) and under sdk (this PR) with types preserved ### Drive-by changes - imports - might break other scripts like delete-keys, etc in infra (not tested) ### Related issues - fixes https://github.com/hyperlane-xyz/issues/issues/887 ### Backward compatibility Yes ### Testing Manual --------- Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>	10 months ago
Yorke Rhodes	54aeb6420b	feat/CLI tool for monitoring warp route balances (#3231 ) ### Description Replay https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3204 on main Co-authored-by: -f <kunalarora1729@gmail.com>	10 months ago
Yorke Rhodes	0ff3e2b171	Deploy injective and inEVM (#3140 ) ### Description - Deploy core to injective and inEVM networks ### Drive-by changes - Update cw-hyperlane dependency ### Backward compatibility Yes ### Testing - Fork tests - e2e tests --------- 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> Co-authored-by: Nam Chu Hoai <nambrot@googlemail.com>	10 months ago
github-actions[bot]	0865c948c3	Version Packages (#3217 ) This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @hyperlane-xyz/core@3.6.2 ### Patch Changes - @hyperlane-xyz/utils@3.6.2 ## @hyperlane-xyz/cli@3.6.2 ### Patch Changes - 99fe93a5b: Removed IGP from preset hook config - @hyperlane-xyz/sdk@3.6.2 - @hyperlane-xyz/utils@3.6.2 ## @hyperlane-xyz/helloworld@3.6.2 ### Patch Changes - @hyperlane-xyz/core@3.6.2 - @hyperlane-xyz/sdk@3.6.2 ## @hyperlane-xyz/sdk@3.6.2 ### Patch Changes - @hyperlane-xyz/core@3.6.2 - @hyperlane-xyz/utils@3.6.2 ## @hyperlane-xyz/utils@3.6.2 ## @hyperlane-xyz/infra@3.6.2 ### Patch Changes - @hyperlane-xyz/helloworld@3.6.2 - @hyperlane-xyz/sdk@3.6.2 - @hyperlane-xyz/utils@3.6.2 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	10 months ago
Paul Balaji	166e9d316a	feat: improve create-key logging (#3207 )	10 months ago
Nam Chu Hoai	1adce84e33	Reduce v3 kathy frequency (#3104 ) ### Description Reduces frequency so that we only send roughly once every hour - [x] Reduce alert thresholds - [x] Deploy	10 months ago
Yorke Rhodes	8fe24830ee	Deploy viction core and warp routes (#3067 ) ### Description Deploys core and warp to viction ### Related issues - Fixes https://github.com/hyperlane-xyz/issues/issues/850 - Fixes https://github.com/hyperlane-xyz/issues/issues/859 ### Backward compatibility Yes ### Testing Fork tests --------- 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> Co-authored-by: Nam Chu Hoai <nambrot@googlemail.com>	10 months ago
Kunal Arora	ff771351b8	feat:update deployments to use `FallbackRoutingHook` (#3179 ) ### Description - mainnet3, testnet4 should be using fallback routing hooks because it's more "porous" for first-time deployers of hyperlane to have merkleTreeHook out of the box ### Drive-by changes - added overrides to configureHook in basedeployer and setHook in hookdeployer - added fetching local rpc first logic in infra/chains and then secrets rpc if needed. This would mean the forking and live setup will be closer as the rpc urls will be the same between the two. ### Related issues None ### Backward compatibility Yes ### Testing Fork	10 months ago
Trevor Porter	1eaed03694	Blacklist (optimism)goerli griefer, deploy w/ new image on testnet4 (#3184 ) ### Description Blacklists a griefer that sent a bunch of messages before we had IGPs properly configured on testnet4 ### 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 -->	10 months ago
Yorke Rhodes	778312d996	Improve ergonomics of fork tests (#2911 ) ### Description https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/2888 introduced breaking changes to non-`arbitrum` chains but fork tests would not cover This PR adds a `fork-all` script for running fork tests on all `protocol == ethereum` chains in an environment It also improves the interface of the `fork` script to accept a target chain ### Drive-by changes - Remove noisy `console.log`s - swap `polygon, ethereum, polygonzkevm` RPCs - Fixes `ownerOverrides: proxyAdmin` for chains without gnosis safes ### Backward compatibility Yes	10 months ago
Yorke Rhodes	fa465b7233	Remove dupe FastHypERC20 for verifiable contracts (#3091 ) ### Description Duplicate FastHypERC20 implementations got into main following the v3 merge that prevent flattening used in verification ### Related issues - Unblocks https://github.com/hyperlane-xyz/issues/issues/886 ### Backward compatibility Yes ### Testing Unit Tests	10 months ago
github-actions[bot]	72774b3b92	Version Packages (#3153 ) # Releases ## @hyperlane-xyz/core@3.6.1 ### Patch Changes - e4e4f93fc: Support pausable ISM in deployer and checker - Updated dependencies [`78e50e7da`] - @hyperlane-xyz/utils@3.6.1 ## @hyperlane-xyz/cli@3.6.1 ### Patch Changes - Updated dependencies [`e4e4f93fc`] - @hyperlane-xyz/utils@3.6.1 - @hyperlane-xyz/sdk@3.6.1 ## @hyperlane-xyz/helloworld@3.6.1 ### Patch Changes - Updated dependencies [`e4e4f93fc`] - @hyperlane-xyz/sdk@3.6.1 - @hyperlane-xyz/core@3.6.1 ## @hyperlane-xyz/sdk@3.6.1 ### Patch Changes - ae4476ad0: Bumped mantapacific reorgPeriod to 1, a reorg period in chain metadata is now required by infra. - f3b7ddb69: Add optional grpcUrl field to ChainMetadata - e4e4f93fc: Support pausable ISM in deployer and checker - Updated dependencies [`e4e4f93fc`] - @hyperlane-xyz/utils@3.6.1 - @hyperlane-xyz/core@3.6.1 ## @hyperlane-xyz/utils@3.6.1 ### Patch Changes - 3c298d064: Add isAddress function to check if string matches EVM, Cosmos, or Solana address formats - df24eec8b: Fix for address utils falsy fallbacks - 78e50e7da: addressToBytes32 changed to work for all protocol types ## @hyperlane-xyz/infra@3.6.1 ### Patch Changes - ae4476ad0: Bumped mantapacific reorgPeriod to 1, a reorg period in chain metadata is now required by infra. - e4e4f93fc: Support pausable ISM in deployer and checker - Updated dependencies [`e4e4f93fc`] - @hyperlane-xyz/utils@3.6.1 - @hyperlane-xyz/sdk@3.6.1 - @hyperlane-xyz/helloworld@3.6.1 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	10 months ago
Daniel Savu	528a19022b	Deploy eclipse testnet (#3172 ) ### 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 --> --------- Co-authored-by: Trevor Porter <trkporter@ucdavis.edu>	10 months ago
Trevor Porter	78e50e7da4	Validator observability infra (#3116 ) ### Description - Configures the relayers to start tracking the latest checkpoints of the manta TIA WR, arbitrum TIA WR, and helloworld sets (and, implicitly, the default ISM sets too) - deployed all agent roles & networks with the new image - created alerts and added to the nexus dashboard One thing that's a bit of a bummer is the metrics are only updated whenever we try to construct metadata for a message. Naturally the validators will poll & sign checkpoints slightly out of sync, so pretty frequently the relayer attempts to deliver a message where say 4/6 signatures are needed, and 2 of the validators happen to just have not polled & signed the checkpoint yet. The message is then successfully delivered, and the 2 remaining validators probably sign the checkpoint in a matter of seconds, but the metrics aren't updated to reflect this unless there's another message whose metadata is being constructed. This just means that the graph is a bit ugly when things are working. But when things aren't working, we'll still be able to clearly see which validators are behind. We may want to consider changing the metrics if this proves confusing. Some ideas: 1. Move to a separate task that occasionally polls the latest checkpoints of the configured app contexts 2. Also track the threshold. This way we can construct alerts & dashboards based off the threshold and not be overly concerned if there are some stragglers ### Drive-by changes added `bytesToBytes32` so that we can construct matching lists, which the agents expect to be 0x-prefixed, using a router address config that may include protocol-specific address formats ### Related issues Fixes #3109 ### Backward compatibility yes ### Testing deployed	11 months ago
Trevor Porter	ae4476ad09	Move to reorg period of 1 for mantapacific (#3126 ) ### Description - Moves to a reorg period of 1 for mantapacific instead of 0 - this should avoid the IGP indexing bugs we're seeing where we first get the latest block, then make an eth_getLogs RPC, but the node servicing the latter RPC doesn't yet know of the new latest block ### Drive-by changes Remove some duplication of the reorg period ### Related issues n/a ### Backward compatibility backward compatible ### Testing none yet, other than deploying	11 months ago
Yorke Rhodes	0727a6178e	Pausable ISM (#3141 ) ### Description - Adds pausable hook and ism config support to deployers - Configure testnet pausable hook and ISM - Add pausable ism checking ### Drive-by changes - Refactors ownable config ### Related issues - https://github.com/hyperlane-xyz/issues/issues/706 ### Backward compatibility - Yes ### Testing - Unit Tests and fork tests	11 months ago
github-actions[bot]	493c160b2e	Version Packages (#3111 ) This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @hyperlane-xyz/sdk@3.6.0 ### Minor Changes - 0488ef31d: Add dsrv, staked and zeeprime as validators - 8d8ba3f7a: HyperlaneIsmFactory is now wary of (try)getDomainId or (try)getChainName calls which may fail and handles them appropriately. ### Patch Changes - 67a6d971e: Added `shouldRecover` flag to deployContractFromFactory so that the `TestRecipientDeployer` can deploy new contracts if it's not the owner of the prior deployments (We were recovering the SDK artifacts which meant the deployer won't be able to set the ISM as they needed) - 612d4163a: Add mailbox version const to SDK - @hyperlane-xyz/core@3.6.0 - @hyperlane-xyz/utils@3.6.0 ## @hyperlane-xyz/core@3.6.0 ### Patch Changes - @hyperlane-xyz/utils@3.6.0 ## @hyperlane-xyz/cli@3.6.0 ### Patch Changes - 67a6d971e: Added `shouldRecover` flag to deployContractFromFactory so that the `TestRecipientDeployer` can deploy new contracts if it's not the owner of the prior deployments (We were recovering the SDK artifacts which meant the deployer won't be able to set the ISM as they needed) - Updated dependencies [`67a6d971e`] - Updated dependencies [`612d4163a`] - Updated dependencies [`0488ef31d`] - Updated dependencies [`8d8ba3f7a`] - @hyperlane-xyz/sdk@3.6.0 - @hyperlane-xyz/utils@3.6.0 ## @hyperlane-xyz/helloworld@3.6.0 ### Patch Changes - Updated dependencies [`67a6d971e`] - Updated dependencies [`612d4163a`] - Updated dependencies [`0488ef31d`] - Updated dependencies [`8d8ba3f7a`] - @hyperlane-xyz/sdk@3.6.0 - @hyperlane-xyz/core@3.6.0 ## @hyperlane-xyz/utils@3.6.0 ## @hyperlane-xyz/infra@3.6.0 ### Patch Changes - 67a6d971e: Added `shouldRecover` flag to deployContractFromFactory so that the `TestRecipientDeployer` can deploy new contracts if it's not the owner of the prior deployments (We were recovering the SDK artifacts which meant the deployer won't be able to set the ISM as they needed) - Updated dependencies [`67a6d971e`] - Updated dependencies [`612d4163a`] - Updated dependencies [`0488ef31d`] - Updated dependencies [`8d8ba3f7a`] - @hyperlane-xyz/sdk@3.6.0 - @hyperlane-xyz/helloworld@3.6.0 - @hyperlane-xyz/utils@3.6.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	11 months ago
Kunal Arora	9561931571	fix: failing ci tests for `SmartProvider` and `OpStackIsm.t.sol` (#3148 ) ### Description - Problem: OpStackIsm.t.sol was failing because of very stale block number for fork Fix: Excluding foundry fork testing from CI and updating block number - Problem: SmartProvider getLogs tests failing because the the results end up being an empty list and getConfirmations results a smaller number of confirmations than expected (712 vs 1705184) fix: excluded from ci ### Drive-by changes None ### Related issues None ### Backward compatibility Yes ### Testing Manual	11 months ago
Kunal Arora	67a6d971ed	fix: `testRecipient` CLI bug (#3138 ) ### Description - we were recovering `TestRecipient` from sdk artifacts which means the deployer won't have ownership. So, I added a optional `shouldRecover` boolean which I turned off for TestRecipient deployer (this is only for our artifacts, if they have their own testRecipient, it will still recover that if provided) - moved `TestRecipientDeployer` from cli to sdk and removed duplicated code from infra ### Drive-by changes None ### Related issues - fixes https://github.com/hyperlane-xyz/issues/issues/895 ### Backward compatibility Yes ### Testing Manual (between anvil1 and optimismgoerli)	11 months ago
Nam Chu Hoai	457473c611	set gasprice on bsctestnet (#3120 ) ### Description Sets a somewhat arbitrary gas price on bsctestnet to get transactions going for the key-funder (and presumably kathy as well). It's a pretty blunt hammer for a not-helpful `transaction underpriced` error, but IMO fine enough ### Drive-by changes handleTx would not handle confirmations=0, and just set it to 1	11 months ago
github-actions[bot]	85efe3c6f4	Version Packages (#3110 ) # Releases ## @hyperlane-xyz/core@3.5.1 ### Patch Changes - @hyperlane-xyz/utils@3.5.1 ## @hyperlane-xyz/cli@3.5.1 ### Patch Changes - Updated dependencies [`a04454d6d`] - @hyperlane-xyz/sdk@3.5.1 - @hyperlane-xyz/utils@3.5.1 ## @hyperlane-xyz/helloworld@3.5.1 ### Patch Changes - Updated dependencies [`a04454d6d`] - @hyperlane-xyz/sdk@3.5.1 - @hyperlane-xyz/core@3.5.1 ## @hyperlane-xyz/sdk@3.5.1 ### Patch Changes - a04454d6d: Use getBalance instead of queryContractSmart for CwTokenAdapter - @hyperlane-xyz/core@3.5.1 - @hyperlane-xyz/utils@3.5.1 ## @hyperlane-xyz/utils@3.5.1 ## @hyperlane-xyz/infra@3.5.1 ### Patch Changes - Updated dependencies [`a04454d6d`] - @hyperlane-xyz/sdk@3.5.1 - @hyperlane-xyz/helloworld@3.5.1 - @hyperlane-xyz/utils@3.5.1 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	11 months ago
Nam Chu Hoai	4ce89df7ef	Limit keyfunder pods execution (#3100 ) ### Description Right now, the key funder process can stall, causing us to stall forever. This PR adds a limit to the job spec	11 months ago
Trevor Porter	2b49baab02	Bump neutron gas price (#3096 ) ### Description Updates the neutron gas price to be slightly above the min that was recently updated :\| https://github.com/cosmos/chain-registry/blob/master/neutron/chain.json#L20 Deployed the Neutron relayer to include our recent changes that allow for the gas price to be easily configured ### 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 -->	11 months ago
github-actions[bot]	67585a2ee0	Version Packages (#3074 ) This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @hyperlane-xyz/sdk@3.5.0 ### Minor Changes - 655b6a0cd: Redeploy Routing ISM Factories ### Patch Changes - 08ba0d32b: Remove dead arbitrum goerli explorer link - f7d285e3a: Adds Test Recipient addresses to the SDK artifacts - @hyperlane-xyz/core@3.5.0 - @hyperlane-xyz/utils@3.5.0 ## @hyperlane-xyz/core@3.5.0 ### Patch Changes - @hyperlane-xyz/utils@3.5.0 ## @hyperlane-xyz/cli@3.5.0 ### Patch Changes - 05a943b4a: Skip mandatory balance check for remotes in send commands - Updated dependencies [`655b6a0cd`] - Updated dependencies [`08ba0d32b`] - Updated dependencies [`f7d285e3a`] - @hyperlane-xyz/sdk@3.5.0 - @hyperlane-xyz/utils@3.5.0 ## @hyperlane-xyz/helloworld@3.5.0 ### Patch Changes - Updated dependencies [`655b6a0cd`] - Updated dependencies [`08ba0d32b`] - Updated dependencies [`f7d285e3a`] - @hyperlane-xyz/sdk@3.5.0 - @hyperlane-xyz/core@3.5.0 ## @hyperlane-xyz/utils@3.5.0 ## @hyperlane-xyz/infra@3.5.0 ### Minor Changes - 655b6a0cd: Redeploy Routing ISM Factories ### Patch Changes - f7d285e3a: Adds Test Recipient addresses to the SDK artifacts - Updated dependencies [`655b6a0cd`] - Updated dependencies [`08ba0d32b`] - Updated dependencies [`f7d285e3a`] - @hyperlane-xyz/sdk@3.5.0 - @hyperlane-xyz/helloworld@3.5.0 - @hyperlane-xyz/utils@3.5.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	12 months ago
Daniel Savu	5c8d483b37	feat: cargo release profile in ci (#2980 )	12 months ago
Yorke Rhodes	f7d285e3a5	Add test recipients to SDK addresses (#3086 ) ### Description Add test recipients to SDK addresses --------- Co-authored-by: J M Rossy <jm.rossy@gmail.com>	12 months ago
Yorke Rhodes	655b6a0cd8	Redeploy routing ISM factories (#3085 )	12 months ago
Daniel Savu	1f651b7afc	chore: remove neutron-related deployments from testnet4 context (#3071 ) ### Description Removes most occurences of lines that contain the `neutron` string from the testnet4 context. Where validators are set (e.g. [here](`3e685f9fb0/typescript/infra/config/environments/testnet4/validators.ts (L29)`)), the neutron context is required for type safety but can stay empty	12 months ago
Trevor Porter	6f9b4e6660	Bump desired AVAX balance (#3068 ) ### Description Avalanche is like 5x more expensive now, see relayer txs https://snowtrace.io/address/0x74Cae0ECC47B02Ed9B9D32E000Fd70B9417970C5. A single funding of 0.3 is only enough to cover like 2 messages ### 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 -->	12 months ago
Yorke Rhodes	10c0ab17d1	Deploy eclipse fi warp (#3062 )	12 months ago
github-actions[bot]	0d9d1d26fa	Version Packages (#3028 ) # Releases ## @hyperlane-xyz/sdk@3.4.0 ### Minor Changes - b832e57ae: Replace Fallback and Retry Providers with new SmartProvider with more effective fallback/retry logic ### Patch Changes - 7919417ec: Granular control of updating predeployed routingIsms based on routing config mismatch - Add support for routingIsmDelta which filters out the incompatibility between the onchain deployed config and the desired config. - Based on the above, you either update the deployed Ism with new routes, delete old routes, change owners, etc. - `moduleMatchesConfig` uses the same - fd4fc1898: - Upgrade Viem to 1.20.0 - Add optional restUrls field to ChainMetadata - Add deepCopy util function - Add support for cosmos factory token addresses - e06fe0b32: Supporting DefaultFallbackRoutingIsm through non-factory deployments - 79c96d718: Remove healthy RPC URLs and remove NeutronTestnet - Updated dependencies [`fd4fc1898`] - Updated dependencies [`e06fe0b32`] - @hyperlane-xyz/utils@3.4.0 - @hyperlane-xyz/core@3.4.0 ## @hyperlane-xyz/core@3.4.0 ### Patch Changes - e06fe0b32: Supporting DefaultFallbackRoutingIsm through non-factory deployments - Updated dependencies [`fd4fc1898`] - @hyperlane-xyz/utils@3.4.0 ## @hyperlane-xyz/cli@3.4.0 ### Patch Changes - e06fe0b32: Supporting DefaultFallbackRoutingIsm through non-factory deployments - dcf8b800a: Fixes for commands with --yes flag - 9c7dbcb94: Remove domainId and protocolType setting when creating chain config - Updated dependencies [`7919417ec`] - Updated dependencies [`fd4fc1898`] - Updated dependencies [`e06fe0b32`] - Updated dependencies [`b832e57ae`] - Updated dependencies [`79c96d718`] - @hyperlane-xyz/sdk@3.4.0 - @hyperlane-xyz/utils@3.4.0 ## @hyperlane-xyz/helloworld@3.4.0 ### Patch Changes - Updated dependencies [`7919417ec`] - Updated dependencies [`fd4fc1898`] - Updated dependencies [`e06fe0b32`] - Updated dependencies [`b832e57ae`] - Updated dependencies [`79c96d718`] - @hyperlane-xyz/sdk@3.4.0 - @hyperlane-xyz/core@3.4.0 ## @hyperlane-xyz/utils@3.4.0 ### Patch Changes - fd4fc1898: - Upgrade Viem to 1.20.0 - Add optional restUrls field to ChainMetadata - Add deepCopy util function - Add support for cosmos factory token addresses ## @hyperlane-xyz/infra@3.4.0 ### Patch Changes - e06fe0b32: Supporting DefaultFallbackRoutingIsm through non-factory deployments - Updated dependencies [`7919417ec`] - Updated dependencies [`fd4fc1898`] - Updated dependencies [`e06fe0b32`] - Updated dependencies [`b832e57ae`] - Updated dependencies [`79c96d718`] - @hyperlane-xyz/sdk@3.4.0 - @hyperlane-xyz/utils@3.4.0 - @hyperlane-xyz/helloworld@3.4.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	12 months ago
Daniel Savu	8d8e3b8bc1	Deploy relayer balance fix (#3037 )	12 months ago
Nam Chu Hoai	e65c2a321c	Manage core governance (#3029 ) ### Description Changes that were required to run the deployer/check to enroll more validators. Some of the changes like removing artifacts from the SDK or changing the chains in infra probably shouldn't be checked in. ### Drive-by changes - Added another error message for mailbox initialization check (since there is no view call to make) - Ignoring validator announce violations in the governor ### Related issues Fixes https://github.com/hyperlane-xyz/issues/issues/673 --------- Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>	12 months ago
J M Rossy	b832e57aef	Replace Fallback/Retry providers with SmartProvider (#3032 ) ### Description - Port `HyperlaneSmartProvider` from explorer - Use as default ethers v5 provider - Includes `HyperlaneJsonRpcProvider` and `HyperlaneEtherscanProvider` for more granular control ### Related issues Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2024 ### Backward compatibility No, the RetryProvider was removed ### Testing Unit tests with Foundry/anvil E2E tests with Goerli via mocha E2E tests via metadata-health CI	12 months ago
Ford	79bd348585	chore(docs): typo fixes (#3051 )	12 months ago
J M Rossy	79c96d7187	Metadata Health Checks (#3030 ) ### Description - Create test to ensure SDK metadata RPCs and Explorers are healthy - Exercise explorer link utils - Enable `sort-keys` eslint rule for SDK metadata - Cleanup metadata and remove unhealthy RPC urls - Remove NeutronTestnet ### Related issues Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2997 ### Backward compatibility Yes	12 months ago
Trevor Porter	95ab709d96	Deploy kathy (#3040 ) ### Description Deploy kathy - seems testnet4 kathy was having issues, this fixes it ### 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 -->	12 months ago
Trevor Porter	313a2ab357	Kathy keys using correct env/context helloworld chains, small fixes (#3035 ) ### Description - Noticed an issue with #3023 where mainnet3 helloworld addresses were always used. This uses the correct environment and context - Also noticed errors with key funder infra because the neutron rpc url wasn't present - fixed the previous hack to accommodate this - Filter out non evm or blessed chains from key funder as well ### Drive-by changes n/a ### Related issues related to #3024 ### Backward compatibility yes ### Testing ran locally	12 months ago
Trevor Porter	1a64cef37e	Refactor key management in infra and key funder (#3023 ) ### Description * Remove the `bank` role, which we haven't used since the inception of abacus / hyperlane * Big changes to `key-utils.ts` so that there's a single source of truth on what kind of keys are used depending on the role & chain. Before this was sprinkled in a few different places * You can now get an object of `{ [chain]: { [role]: keys[] } }`, so it's super clear what kind of key relates to which chain. For example, before we would use the AWS-based relayer key for EVM chains, and then a GCP-based relayer key for non-EVM chains. But this wasn't really honored by key funder - it had no way of knowing to only fund the AWS relayer on EVM chains, and only fund the GCP relayer on non-EVM chains. Same situation for Kathy, where we want to use AWS keys for EVM chains but the GCP key for non-EVM chains * On v2 and prior to that we were using the AWS-based key for Kathy. Originally, we also launched v3 this way. However it was changed on v3 to use the GCP key for Kathy, causing us to fund both types of addresses on v3. This makes it more clear that we should be using the AWS-based key for Kathy on EVM chains ### 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 -->	1 year ago
Kunal Arora	e06fe0b327	fix:enable `DefaultFallbackRoutingIsm` through non-factory deployment (#3009 ) ### Description - `DefaultFallbackRoutingIsm` needs the mailbox address which meant `DefaultFallbackRoutingIsmFactory` needed the mailbox address which is not ideal. So, I switched to non-factory deployments for this specific ISM type. - CLI does the ISM deployment inside core deployment instead of ISM first and core then. - Using the coreDeployer's `cachedAddresses` to store the latest ie toplevel ISM. ### Drive-by changes - fixed bug in `ismFactory.fromAddressMap` to not use the multiprovider filtered by contract map. This is undesirable as CLI user can provide chain selection and artifacts which doesn't include all the chains in the configs (and when we call `multiprovider.getDomainId` for the origin which may now be missing from the filtered MP, we get an error). ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2895 ### Backward compatibility Yes ### Testing Manual through CLI	1 year ago
github-actions[bot]	8b16adee48	Version Packages (#3002 ) # Releases ## @hyperlane-xyz/cli@3.3.0 ### Minor Changes - 7e620c9df: Allow CLI to accept hook as a config ### Patch Changes - f44589e45: Improve warp and kurtosis deploy command UX - 2da6ccebe: Allow users to only configure validators for their chain - Don't restrict user to having two chains for ism config - If the user accidentally picks two chains, we prompt them again to confirm if they don't want to use the hyperlane validators for their multisigConfig - 9f2c7ce7c: Removing agentStartBlocks and using mailbox.deployedBlock() instead - 9705079f9: Improve UX of the send and status commands - c606b6a48: Add figlet to CLI - Updated dependencies [`7e620c9df`] - Updated dependencies [`350175581`] - Updated dependencies [`9f2c7ce7c`] - @hyperlane-xyz/sdk@3.3.0 - @hyperlane-xyz/utils@3.3.0 ## @hyperlane-xyz/core@3.3.0 ### Patch Changes - 350175581: Rename StaticProtocolFee hook to ProtocolFee for clarity - @hyperlane-xyz/utils@3.3.0 ## @hyperlane-xyz/helloworld@3.3.0 ### Patch Changes - Updated dependencies [`7e620c9df`] - Updated dependencies [`350175581`] - Updated dependencies [`9f2c7ce7c`] - @hyperlane-xyz/sdk@3.3.0 - @hyperlane-xyz/core@3.3.0 ## @hyperlane-xyz/sdk@3.3.0 ### Patch Changes - 7e620c9df: Allow CLI to accept hook as a config - 350175581: Rename StaticProtocolFee hook to ProtocolFee for clarity - 9f2c7ce7c: Removing agentStartBlocks and using mailbox.deployedBlock() instead - Updated dependencies [`350175581`] - @hyperlane-xyz/core@3.3.0 - @hyperlane-xyz/utils@3.3.0 ## @hyperlane-xyz/utils@3.3.0 ## @hyperlane-xyz/infra@3.3.0 ### Patch Changes - 7e620c9df: Allow CLI to accept hook as a config - 9f2c7ce7c: Removing agentStartBlocks and using mailbox.deployedBlock() instead - Updated dependencies [`7e620c9df`] - Updated dependencies [`350175581`] - Updated dependencies [`9f2c7ce7c`] - @hyperlane-xyz/sdk@3.3.0 - @hyperlane-xyz/helloworld@3.3.0 - @hyperlane-xyz/utils@3.3.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	1 year ago
Daniel Savu	e791336115	Deploy relayer balance metrics (#3027 )	1 year ago
Kunal Arora	7e620c9dfa	feat:configure hooks in the CLI (#2964 ) ### Description - enable configuring hooks in the CLI (merkle, igp, protocolFee, aggregation, routing) - use preset by default without prompting ### 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 -->	1 year ago
Trevor Porter	9fc0866b29	Fix base bridging and a race condition in key funder (#3012 ) ### Description Turns out bridging from L1 to Base has been broken the whole time :( it's because the version of @eth-optimism/sdk we were using was 1.8.0 (according to yarn.lock) which was released in late 2022 https://github.com/ethereum-optimism/optimism/releases/tag/%40eth-optimism%2Fsdk%401.8.0, far before Base was launched. So we'd always get this error in key funder because we rely on the optimism SDK knowing about Base's chain ID: ``` {"chain":"base","error":"Error: cannot get contract AddressManager for unknown L2 chain ID 8453, you must provide an address\n at getOEContract (/hyperlane-monorepo/node_modules/@eth-optimism/sdk/src/utils/contracts.ts:58:11)\n at getAllOEContracts (/hyperlane-monorepo/node_modules/@eth-optimism/sdk/src/utils/contracts.ts:121:46)\n at new CrossChainMessenger (/hyperlane-monorepo/node_modules/@eth-optimism/sdk/src/cross-chain-messenger.ts:170:39)\n at ContextFunder.bridgeToOptimism (/hyperlane-monorepo/typescript/infra/scripts/funding/fund-keys-from-deployer.ts:652:33)\n at ContextFunder.bridgeToL2 (/hyperlane-monorepo/typescript/infra/scripts/funding/fund-keys-from-deployer.ts:637:23)\n at processTicksAndRejections (node:internal/process/task_queues:96:5)\n at async ContextFunder.bridgeIfL2 (/hyperlane-monorepo/typescript/infra/scripts/funding/fund-keys-from-deployer.ts:492:9)\n at async gracefullyHandleError (/hyperlane-monorepo/typescript/infra/scripts/funding/fund-keys-from-deployer.ts:774:5)\n at async /hyperlane-monorepo/typescript/infra/scripts/funding/fund-keys-from-deployer.ts:394:29\n at async Promise.all (index 9)","level":"error","message":"Error bridging to L2"} ``` The fix was just to upgrade to a newer optimism SDK version A mystery to me is that we'd get that log ^ but sometimes the key funder pod would show as having ran successfully. My best guess here is there was a race condition in `fund` when we had a variable local to the function called `failureOccurred` that many promises which were `Promise.all`'d would read and write to it via `failureOccurred \|\|= await someFallibleFn()`. I changed the logic here to not have multiple concurrent promises contend for the variable Also made a small change to not include mantapacific in the list of relayer keys for the Hyperlane context. It's not ever used, and had a downstream effect of us trying to fund the Kathy key on mantapacific, which we don't want to actually do ### Drive-by changes n/a ### Related issues n/a ### Backward compatibility ye ### Testing ran locally	1 year ago
Trevor Porter	7297c8d6f2	Deploy kathy w/ PolygonZkEvm fix (#3011 ) ### Description Deploy Kathy with #3001 ### Drive-by changes Small fix to deploy kathy successfully - because the relayer chains doesn't include neutron and kathy will try to create a multiprovider for all chains the env, we need to use the environment chain names as the helm `hyperlane.chains` value ### 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 -->	1 year ago
Trevor Porter	e21e020b89	Fix Kathy sending from PolygonZkEvm & require MultiProtocolProvider chains to match addresses in MultiProtocolApp (#3001 ) ### Description Fixes 2 issues: 1. Estimates gas in Kathy by explicitly specifying the `from` address due to this bug with PolygonZkEvm when using a non-zero value https://github.com/0xPolygonHermez/zkevm-node/issues/2869 2. Now that we've added neutron & mantapacific as mainnet chains but we don't have helloworld deployments on these chains, Kathy was trying to send to & from these chains. To fix, I changed the constructor of `MultiProtocolApp` to intersect the multiProvider to only work with the chains specified in `addresses` ### Drive-by changes n/a ### Related issues n/a ### Backward compatibility ye ### Testing Ran kathy locally successfully & sent from polygonzkevm	1 year ago
Trevor Porter	852b8d806b	Deploy new agent release (#3004 ) ### Description Deploying with new release ### 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 -->	1 year ago
Kunal Arora	9f2c7ce7c4	fix:remove `agentStartBlock` and use `mailbox.deployedBlock()` instead (#3005 ) ### Description - CLI was using a static start block numbers for core chains or getting the latest block number from a PI chain for agent config which is redundant and dangerous. Instead, I updated to using the `mailbox.deployedBlock()` which should precede all other indexable contract deployment and is hence safer. ### Drive-by changes - filtering the agent configs in CLI is redundant since the `HyperlaneDeploymentArtifactsSchema` requires all the specified entries and if `writeAgentConfig` gets an artifacts which doesn't contain these, we should throw an error and not filter them. ### Related issues - related to https://github.com/hyperlane-xyz/issues/issues/736 ### Backward compatibility Yes ### Testing Manual b/w anvil1 and anvil2	1 year ago
Nam Chu Hoai	6bb5be16a9	Update gas oracle values (#2996 ) ### Description Updates the values given the current market conditions ### Drive-by changes Add a sleep for avoid getting rate limited	1 year ago
Trevor Porter	b60e5d9b29	Deploy new agents w/ Polygon gas fix (#2999 ) ### Description Deploys w/ https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/2998 ### Drive-by changes - Had to remove mantapacific from the list of scraper chains because it's not present in the DB domain table atm ### Related issues n/a ### Backward compatibility n/a ### Testing Deployed	1 year ago

1 2 3 4 5 ...

579 Commits (cf826875074188513a88225903212238515cd75a)