hyperlane-monorepo

Commit Graph

Author	SHA1	Message	Date
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>	12 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	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
J M Rossy	1918560609	Reduce verbosity of smartprovider logging (#3084 )	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
J M Rossy	08ba0d32b9	Remove dead goerli arbiscan link (#3073 )	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
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	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	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	1 year ago
Yorke Rhodes	c606b6a485	Add figlet to CLI (#3008 )	1 year ago
J M Rossy	c65b598719	Remove demand option for router arg of send transfer (#3018 ) Fix for missing bit of #3006	1 year ago
J M Rossy	9705079f99	Improve UX of send and status commands (#3006 ) ### Description - Improve shared context utility with conditional typing and core artifact handling - Improve UX of send and status commands with prompts - Prompt for key if required and not provided ### Drive-by Changes Update the token readme for https://github.com/hyperlane-xyz/issues/issues/715 ### Backward compatibility Yes ### Testing Manual	1 year ago
Kunal Arora	d0c1f8f11e	Rename `hook-config.yaml` to `hooks.yaml` in `ci-test.sh` (#3016 ) ### Description - CI fails otherwise ### 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 Manual	1 year ago
J M Rossy	eb83cf891c	Enable for-in lint rule (#3013 ) ### Description https://eslint.org/docs/latest/rules/guard-for-in ### Drive-by changes Fix lint error in SDK Sealevel adapter ### Backward compatibility Yes	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
Yorke Rhodes	98f7e21b99	Previous yarn test --since failed to catch deps (#3007 )	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
Yorke Rhodes	3501755816	Add storage layout diff checks (#2991 )	1 year ago
J M Rossy	f44589e454	Improve warp and kurtosis deploy command dx (#2994 ) ### Description Add artifact selection step to warp deploy Improve chain selection for kurtosis agent deploy ### Drive-by changes Add chain metadata consts validation unit test ### Related issues Fixes https://github.com/hyperlane-xyz/issues/issues/774 ### Backward compatibility Small break in kurtosis deploy args, likely won't be noticed. ### Testing Manual	1 year ago
Kunal Arora	2a547eee18	`multisigIsm` -> `interchainSecurityModule` for core deployments artifact (#2993 ) ### Description - changing `multisigIsm` to`interchainSecurityModule` for core deployments artifact ### 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

1 2 3 4 5 ...

994 Commits (8ccfdb7f0119ce28ceaef4fbcfc05bafec97225a)