hyperlane-monorepo

Commit Graph

Author	SHA1	Message	Date
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
J M Rossy	f3b7ddb699	Add optional gRpcUrls field to ChainMetadata schema (#3163 ) ### Description - Add optional gRpcUrls field to ChainMetadata schema - Enforce inclusion of restUrls and gRpcUrls for cosmos chains - Fix neutron rest url ### Related Issues Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3161 ### Backward compatibility Yes ### Testing Unit test	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	10 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	10 months ago
Nam Chu Hoai	3339f78537	Support unoptimized InterchainGasPaymaster bytecode (#3137 ) ### Description Testnet4 has unoptimized Bytecode that did not get added as a constant in the checker ### Drive-by changes CLI test was referencing the wrong folder	10 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	10 months ago
J M Rossy	3c298d0646	Fix Smart Provider e2e test (#3150 ) ### Description Remove hard-coding of min block number and topic1 value. ### Drive-by changes Add convenience `isAddress` util function ### Related issues https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3148 ### Backward compatibility Yes	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	8d8ba3f7ab	fix:`HyperlaneIsmFactory` doesn't fail with missing chainMetadata errors (#3142 ) ### Description HyperlaneIsmFactory is now wary of (try)getDomainId or (try)getChainName calls which may fail and handles them appropriately. - switched from chainName to domain in `routingModuleDelta` - replace `getDomainId` with `tryGetDomainId` and `getChainName` with `tryGetChainName` wherever necessary. ### Drive-by changes None ### Related issues None ### Backward compatibility Yes ### Testing Hardhat unit tests	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	c720ee1d6a	One last round of validators (#3112 ) ### Description Zeeprime added a celo validator and we actually had already announced the staked validators, so just adding now	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
Nam Chu Hoai	efc2410ed6	Fix IGP bytecode checking (#3128 ) ### Description Can't really explain it, but we had some misnamed bytecode constants that I had to fix up. Also checked the bytecodes in the IGP checker	11 months ago
J M Rossy	612d4163ac	Add mailbox version const to SDK (#3125 )	11 months ago
Nam Chu Hoai	0488ef31d2	Add validators (#3087 ) ### Description Adds the last of dsrv, staked, and zeeprime	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
Trevor Porter	3f88aa6f6e	Observability of validators for relayers (#3057 ) ### Description Goal of this was to have insight into validators of important sets being "up" Introduces a new metric used by relayers: `hyperlane_observed_validator_latest_index`, e.g.: ``` hyperlane_observed_validator_latest_index{agent="relayer",app_context="default_ism",destination="test1",hyperlane_baselib_version="0.1.0",origin="test2",validator="0x9965507d1a55bcc2695c58ba16fb37d819b0a4dc"} 664 hyperlane_observed_validator_latest_index{agent="relayer",app_context="default_ism",destination="test1",hyperlane_baselib_version="0.1.0",origin="test3",validator="0x976ea74026e726554db657fa54763abd0c3a0aa9"} 641 hyperlane_observed_validator_latest_index{agent="relayer",app_context="default_ism",destination="test2",hyperlane_baselib_version="0.1.0",origin="test1",validator="0x15d34aaf54267db7d7c367839aaf71a00a2c6a65"} 670 hyperlane_observed_validator_latest_index{agent="relayer",app_context="default_ism",destination="test2",hyperlane_baselib_version="0.1.0",origin="test3",validator="0x976ea74026e726554db657fa54763abd0c3a0aa9"} 665 hyperlane_observed_validator_latest_index{agent="relayer",app_context="default_ism",destination="test3",hyperlane_baselib_version="0.1.0",origin="test1",validator="0x15d34aaf54267db7d7c367839aaf71a00a2c6a65"} 652 hyperlane_observed_validator_latest_index{agent="relayer",app_context="default_ism",destination="test3",hyperlane_baselib_version="0.1.0",origin="test2",validator="0x9965507d1a55bcc2695c58ba16fb37d819b0a4dc"} 664 hyperlane_observed_validator_latest_index{agent="relayer",app_context="testapp",destination="test1",hyperlane_baselib_version="0.1.0",origin="test2",validator="0x9965507d1a55bcc2695c58ba16fb37d819b0a4dc"} 658 hyperlane_observed_validator_latest_index{agent="relayer",app_context="testapp",destination="test1",hyperlane_baselib_version="0.1.0",origin="test3",validator="0x976ea74026e726554db657fa54763abd0c3a0aa9"} 641 ``` Tapping into metadata building for multisig ISMs, the relayer will update the metric with the latest indices for the validators in a set. In order to prevent the cardinality being ridiculously high, only certain validator sets are tracked. This is done by introducing an `app_context` label (I'm very open to other names here, for some reason whenever idk how to name some kind of identifier I end up calling it a context 😆) The app context can either be: - if a new setting, --metricAppContexts, is specified, a message will be classified based off the first matching list it matches. E.g. `--metricAppContexts '[{"name": "testapp", "matchingList": [{"recipient_address": "0xd84379ceae14aa33c123af12424a37803f885889", "destination_domain": 13371 }] }]'`. This is nice for e.g. warp route deployments, where the ISM is maybe not a default ISM, and can be changed - if a message doesn't get classified this way, it can also be classified with the "default_ism" app context, which is just for any message that happens to use the default ISM as its "root" ISM This way we have insight in to the default ISM and any application-specific ISMs. Some things to note: - it's possible for a message to actually have more than one validator set, e.g. if it's using an aggregation ISM. In this case, we'll have metrics on the union of all validator sets for that app context - Some effort is required to make sure that metrics don't stick around for a validator that has actually been removed from the set. To handle this, we cache the validator set for an app context and clear out the entire set each time we set the metrics ### Drive-by changes - Zod's nonempty function for strings is deprecated, moves to `.min(1)` instead ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/1762 ### Backward compatibility yes ### Testing Ran locally - I think i'll probably add something in e2e tests, but opening now	11 months ago
J M Rossy	a04454d6d7	Fix for CwTokenAdapter getBalance method (#3107 ) ### Description Use getBalance instead of queryContractSmart for CwTokenAdapter ### Drive-by Changes Fix SmartProvider unit test ### Backward compatibility Yes ### Testing Tested in warp UI	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
Andrijan Ostrun	0e60c225ff	Fix initializing existing mailbox with failing gas estimation (#3099 ) ### Description Add additional check to handle a situation when the transaction fails during the gas estimation phase. ### Backward compatibility Yes ### Testing Manual	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>	11 months ago
J M Rossy	05a943b4ad	CLI pre-flight check fix (#3089 ) ### Description Only check origin balances for CLI send commands ### Related issues Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3079 ### Backward compatibility Yes ### Testing Tested command locally	11 months ago
Daniel Savu	5c8d483b37	feat: cargo release profile in ci (#2980 )	11 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>	11 months ago
Yorke Rhodes	655b6a0cd8	Redeploy routing ISM factories (#3085 )	11 months ago
J M Rossy	1918560609	Reduce verbosity of smartprovider logging (#3084 )	11 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	11 months ago
J M Rossy	08ba0d32b9	Remove dead goerli arbiscan link (#3073 )	11 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 -->	11 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
J M Rossy	fd4fc1898c	Upgrade Viem & fix neutron chainmetadata (#3049 ) ### Description - Upgrade Viem and wagmi chains versions - Add optional RestUrl field to ChainMetadata - Set rest url for Neutron - Add simple deepCopy function Prerequisite for https://github.com/hyperlane-xyz/hyperlane-warp-ui-template/issues/80 ### Backward compatibility Yes ### Testing Tested in Warp UI	12 months ago
J M Rossy	dcf8b800a9	Fixes for commands with --yes flag (#3063 ) ### Description Consistently respect --yes flag for all user prompts in the core and warp deploy commands ### Related issues Fixes #3056 ### Backward compatibility Yes ### Testing Locally with CI test alterations	12 months ago
Nam Chu Hoai	9c7dbcb947	Default domainId and protocolType (#3041 ) ### Description We only support EVM chains today, so folks pretty much should always use the chainId as the domainId and not choose any other protocol type other than ethereum. So removing the optionality for now until that changes	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
Kunal Arora	7919417ecd	feat: add routing delta for more granular routingIsm config updates (#3017 ) ### Description - 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 ### Drive-by changes - checking exclusion of domains in the onchain deployed config ### Related issues - fixes https://github.com/hyperlane-xyz/issues/issues/818 ### Backward compatibility Yes ### Testing Unit tests --------- 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
Nam Chu Hoai	980ef1fc4e	Revert "Add figlet to CLI (#3008 )" (#3033 ) This reverts commit `c606b6a485`. ### 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 -->	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 -->	12 months 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	12 months 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>	12 months ago
Daniel Savu	e791336115	Deploy relayer balance metrics (#3027 )	12 months ago
Kunal Arora	2da6ccebe8	fix:don't prompt user for multisig config if chain is core (#3021 ) ### Description - 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 ### Drive-by changes None ### Related issues - fixes https://github.com/hyperlane-xyz/issues/issues/811 ### Backward compatibility Yes ### Testing Manual between arbitrumgoerli and anvil1	12 months ago

1 2 3 4 5 ...

1009 Commits (528a19022be131efb5dba6b6fa9e3f52372adbec)