-
Notifications
You must be signed in to change notification settings - Fork 389
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ancient8 deploy #3075
ancient8 deploy #3075
Conversation
🦋 Changeset detectedLatest commit: 65d50f5 The changes in this PR will be included in the next version bump. This PR includes changesets to release 6 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
85b0106
to
c8cf499
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm so far!
"fallbackRoutingHook": "0x863E8c26621c52ACa1849C53500606e73BA272F0", | ||
"storageGasOracle": "0x6b1bb4ce664Bb4164AEB4d3D2E7DE7450DD8084C", | ||
"interchainGasPaymaster": "0x86fb9F1c124fB20ff130C41a79a432F770f67AFD", | ||
"protocolFee": "0x267B6B6eAf6790faE5D5E9070F28a9cE64CbF279" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reminder: testRecipient
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/[email protected] ### Minor Changes - 655b6a0: Redeploy Routing ISM Factories ### Patch Changes - 08ba0d3: Remove dead arbitrum goerli explorer link - f7d285e: Adds Test Recipient addresses to the SDK artifacts - @hyperlane-xyz/[email protected] - @hyperlane-xyz/[email protected] ## @hyperlane-xyz/[email protected] ### Patch Changes - @hyperlane-xyz/[email protected] ## @hyperlane-xyz/[email protected] ### Patch Changes - 05a943b: Skip mandatory balance check for remotes in send commands - Updated dependencies [655b6a0] - Updated dependencies [08ba0d3] - Updated dependencies [f7d285e] - @hyperlane-xyz/[email protected] - @hyperlane-xyz/[email protected] ## @hyperlane-xyz/[email protected] ### Patch Changes - Updated dependencies [655b6a0] - Updated dependencies [08ba0d3] - Updated dependencies [f7d285e] - @hyperlane-xyz/[email protected] - @hyperlane-xyz/[email protected] ## @hyperlane-xyz/[email protected] ## @hyperlane-xyz/[email protected] ### Minor Changes - 655b6a0: Redeploy Routing ISM Factories ### Patch Changes - f7d285e: Adds Test Recipient addresses to the SDK artifacts - Updated dependencies [655b6a0] - Updated dependencies [08ba0d3] - Updated dependencies [f7d285e] - @hyperlane-xyz/[email protected] - @hyperlane-xyz/[email protected] - @hyperlane-xyz/[email protected] Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
### 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 -->
### Description Add additional check to handle a situation when the transaction fails during the gas estimation phase. ### Backward compatibility Yes ### Testing Manual
### Description Right now, the key funder process can stall, causing us to stall forever. This PR adds a limit to the job spec
### Description Use getBalance instead of queryContractSmart for CwTokenAdapter ### Drive-by Changes Fix SmartProvider unit test ### Backward compatibility Yes ### Testing Tested in warp UI
### 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 #1762 ### Backward compatibility yes ### Testing Ran locally - I think i'll probably add something in e2e tests, but opening now
### Description Deduplicates ethereum logs by collecting them into a HashSet before returning a Vec. I couldn't find a way to deduplicate using an ethers config, but since `fetch_logs` is only called once in hyperlane-base, I'm doing the deduplication there "globally". I also noted in doc comments that duplicates may be returned. ### Related issues - Fixes #3070 ### Backward compatibility Yes ### Testing Will rely on e2e passing but haven't added unit tests for this scenario
# Releases ## @hyperlane-xyz/[email protected] ### Patch Changes - @hyperlane-xyz/[email protected] ## @hyperlane-xyz/[email protected] ### Patch Changes - Updated dependencies [a04454d] - @hyperlane-xyz/[email protected] - @hyperlane-xyz/[email protected] ## @hyperlane-xyz/[email protected] ### Patch Changes - Updated dependencies [a04454d] - @hyperlane-xyz/[email protected] - @hyperlane-xyz/[email protected] ## @hyperlane-xyz/[email protected] ### Patch Changes - a04454d: Use getBalance instead of queryContractSmart for CwTokenAdapter - @hyperlane-xyz/[email protected] - @hyperlane-xyz/[email protected] ## @hyperlane-xyz/[email protected] ## @hyperlane-xyz/[email protected] ### Patch Changes - Updated dependencies [a04454d] - @hyperlane-xyz/[email protected] - @hyperlane-xyz/[email protected] - @hyperlane-xyz/[email protected] Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
### Description Adds the last of dsrv, staked, and zeeprime
### Description - viction RPC URL maxes out at 1K blocks for eth_getLogs - restored the index params for scroll that were accidentally changed in https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3067/files#diff-edae1a4e631a67121d92119998e37740c0190bec5060e3c842cc86e4d3d26a4dL701 - deploys the agents - fixes announce-validators.ts if there are non-evm chains in the env ### 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 -->
Description
Drive-by changes
Related issues
Backward compatibility
Testing