hyperlane-monorepo

Commit Graph

Author	SHA1	Message	Date
Daniel Savu	b54c14cd31	chore: re-enforce a whitelist policy in the RC relayer (#4032 ) ### 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 -->	5 months ago
Paul Balaji	c5a5e264b8	chore: enable `osmosis` on relayer (#4028 ) - chore: enable `osmosis` on relayer - drive-by add default chain signer/key/type to agent config - `signer.key` is copied from `neutron` --------- Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Trevor Porter	832351d0d0	chore: set agent and environment specific resource requests (#4027 ) ### Description - based off https://abacusworks.grafana.net/d/FSR9YWr7k, updated resource requests for all agents. Because mainnet3 sees so many more messages and more chains, the resource needs there are higher - allows for resources to be defined in infra - previously we'd just use the default value in the values.yaml of the helm charts. Also makes the resources specific to the type of agent, which is nice because relayers require much higher spec than validators - I haven't deployed this yet, will do so when I get a review ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Fixes https://github.com/hyperlane-xyz/issues/issues/1288 ### 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 -->	5 months ago
Paul Balaji	23ad36ab98	feat(infra): allow specifying chains to deploy validators for in infra (#4014 ) - allow someone to provide a specific set of chains to deploy validators for deploying validator: ![image](https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/10051819/906c3c45-27e1-43ca-ac21-176ade91a500) deploying relayer: ![image](https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/10051819/a5c6af09-1f6a-4c1a-8652-05fbb10ced30) --------- Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Trevor Porter	9aca29260b	chore: deploy relayer with new image and ezETH metrics (#3993 ) ### 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 -->	5 months ago
Trevor Porter	c84a1dc73b	feat: address blacklisting in the relayer (#4000 ) ### Description See context here https://discord.com/channels/935678348330434570/1236041564673806427/1252918894755319920 and https://discord.com/channels/935678348330434570/1252953507833708605/1252954456400592997 This is a rudimentary first step toward blacklisting addresses. Future options are outlined in https://discord.com/channels/935678348330434570/1236041564673806427/1252918894755319920. Eventually we can also fetch these addresses directly within the agent from an updated list that we cache and re-fetch occasionally. For now, this just relies on configured addresses. The approach is: - Allow hex addresses to be configured. These are intentionally treated as a Vec<u8> instead of an H160 / H256. This is because treating them as H160 is a leak of Ethereum-specific logic into non-chain-specific code in the relayer, and treating them as H256 would pad Ethereum addresses with a bunch of zeroes which would diminish the accuracy of our heuristic implemented in this. The subsequence stuff is a bit unfortunate because it's O(n^2) but 🤷‍♂️ - The heuristic is as follows - if any of the configured addresses are found as a subsequence in the message sender, recipient, or body, it's thrown out by the message processor, and the message will never make its way to the op_submitter. This heuristic for the body is to prevent warp route transfers that include that address. We could maybe convert Vec<u8> to H256 for the sender and recipient, I'm open to this - I just went with the substring approach bc it felt easiest tbh. ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Fixes https://github.com/hyperlane-xyz/issues/issues/1285 ### 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 -->	5 months ago
Nam Chu Hoai	c6ba381e44	chore: add more multisigs (#3974 ) ### Description Add multisig owners for linea, mode and blast. Expected violations are mailbox,proxyadmin, and ism violations (since the routing ism expected owner is now different) --------- Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>	5 months ago
github-actions[bot]	b758a5949c	Version Packages (#3991 ) 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.16.0 ### Minor Changes - 5cc64eb09: Add validator addresses for linea, fraxtal, sei. Estimate gas and add 10% buffer inside HyperlaneIsmFactory as well. ### Patch Changes - f9bbdde76: Fix initial total supply of synthetic token deployments to 0 - @hyperlane-xyz/core@3.16.0 - @hyperlane-xyz/utils@3.16.0 ## @hyperlane-xyz/core@3.16.0 ### Patch Changes - @hyperlane-xyz/utils@3.16.0 ## @hyperlane-xyz/cli@3.16.0 ### Patch Changes - Updated dependencies [`f9bbdde76`] - Updated dependencies [`5cc64eb09`] - @hyperlane-xyz/sdk@3.16.0 - @hyperlane-xyz/utils@3.16.0 ## @hyperlane-xyz/helloworld@3.16.0 ### Patch Changes - Updated dependencies [`f9bbdde76`] - Updated dependencies [`5cc64eb09`] - @hyperlane-xyz/sdk@3.16.0 - @hyperlane-xyz/core@3.16.0 ## @hyperlane-xyz/utils@3.16.0 ## @hyperlane-xyz/infra@3.16.0 ### Minor Changes - 5cc64eb09: Add support for new chains: linea, fraxtal, sei. Support osmosis remote. Drive-by fix to always fetch explorer API keys when running deploy script. ### Patch Changes - 5cc64eb09: Allow selecting a specific chain to govern in check-deploy script - Updated dependencies [`f9bbdde76`] - Updated dependencies [`5cc64eb09`] - @hyperlane-xyz/sdk@3.16.0 - @hyperlane-xyz/helloworld@3.16.0 - @hyperlane-xyz/utils@3.16.0 ## @hyperlane-xyz/ccip-server@3.16.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	5 months ago
Trevor Porter	47338f983d	fix: set resource requests for prometheus server & node exporter (#3998 ) ### Description See https://discord.com/channels/935678348330434570/935679524534911007/1252943931121864824 - an attempt to fix some intermittent issues we've seen with prometheus ### 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 -->	5 months ago
Daniel Savu	030eaf1204	chore: bump agent docker images (#3999 ) ### 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 -->	5 months ago
Daniel Savu	3bb9d0a767	fix(cosmos): validator checkpoint & agent indexing improvements (#3958 ) - propagates RPC errors to the indexing logic, so errors cause sleeps instead of overwhelming the RPCs. This also greatly reduces cosmos log noisiness: from 9.5k logs per min, to 2.5k logs per min. - checks for published checkpoints in reverse, to prioritize recent messages among those from before the validator was spun up - fixes a validator bug where errors in checkpoint publishing would cause the entire checkpoint queue to be reiterated through, from scratch - Builds on top of https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3887 so we can test this out on osmosis ### 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 -->	5 months ago
Paul Balaji	9c7cf45c41	feat: reduce extraneous entries in generated registry/agent artifacts (#3988 ) - filters out remote domain metadata from configs written to disk ``` "ancient8": { // this gets removed "arbitrum": { "aggregationHook": "0xblahblahblah", "interchainSecurityModule": "0xblahblah" ...etc }, // keep the usual entries like this "aggregationHook": "0x1EF4ED658d542524d1D547ba2F94d3B038a55b8f", "batchContractAddress": "0x4C97D35c668EE5194a13c8DE8Afc18cce40C9F28", "blockExplorers": [ ...etc ``` - no longer include secret overrides in the configs written to disk - i.e. use public registry RPCs and chain metadata (want our output to be like that of update-agent-config, but with updated contract addresses only) --------- Signed-off-by: Paul Balaji <paul@hyperlane.xyz>	5 months ago
Paul Balaji	5cc64eb095	feat: deploy to new chains (fraxtal, linea, sei) (#3887 ) https://github.com/hyperlane-xyz/issues/issues/1279 - adds `fraxtal`, `linea`, `sei` - supports `osmosis` as a remote - ~drive-by hack to skip reconfiguring the same gas oracle (cc @tkporter)~ - drive-by fix to bring the logic of estimating tx + adding 10% buffer into the ism factory (as originally seen in the multiprovider handleDeploy function) - drive-by fix for creating custom safes - drive-by support of `osmosis` as a remote chain - drive-by addition of `osmosis` to the rust agent --------- Signed-off-by: Paul Balaji <paul@hyperlane.xyz> Co-authored-by: Trevor Porter <tkporter4@gmail.com> Co-authored-by: nambrot <nambrot@googlemail.com>	5 months ago
github-actions[bot]	6b5a763e78	Version Packages (#3980 ) 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.15.1 ### Patch Changes - 6620fe636: fix: `TokenRouter.transferRemote` with hook overrides - @hyperlane-xyz/utils@3.15.1 ## @hyperlane-xyz/cli@3.15.1 ### Patch Changes - 921e449b4: Support priorityFee fetching from RPC and some better logging - Updated dependencies [`acaa22cd9`] - Updated dependencies [`921e449b4`] - @hyperlane-xyz/sdk@3.15.1 - @hyperlane-xyz/utils@3.15.1 ## @hyperlane-xyz/helloworld@3.15.1 ### Patch Changes - 6620fe636: fix: `TokenRouter.transferRemote` with hook overrides - Updated dependencies [`6620fe636`] - Updated dependencies [`acaa22cd9`] - Updated dependencies [`921e449b4`] - @hyperlane-xyz/core@3.15.1 - @hyperlane-xyz/sdk@3.15.1 ## @hyperlane-xyz/sdk@3.15.1 ### Patch Changes - acaa22cd9: Do not consider xERC20 a collateral standard to fix fungibility checking logic while maintaining mint limit checking - 921e449b4: Support priorityFee fetching from RPC and some better logging - Updated dependencies [`6620fe636`] - @hyperlane-xyz/core@3.15.1 - @hyperlane-xyz/utils@3.15.1 ## @hyperlane-xyz/utils@3.15.1 ## @hyperlane-xyz/infra@3.15.1 ### Patch Changes - Updated dependencies [`6620fe636`] - Updated dependencies [`acaa22cd9`] - Updated dependencies [`921e449b4`] - @hyperlane-xyz/helloworld@3.15.1 - @hyperlane-xyz/sdk@3.15.1 - @hyperlane-xyz/utils@3.15.1 ## @hyperlane-xyz/ccip-server@3.15.1 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	5 months ago
github-actions[bot]	27580329eb	Version Packages (#3967 ) 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.15.0 ### Minor Changes - 51bfff683: Mint/burn limit checking for xERC20 bridging Corrects CLI output for HypXERC20 and HypXERC20Lockbox deployments ### Patch Changes - @hyperlane-xyz/utils@3.15.0 ## @hyperlane-xyz/cli@3.15.0 ### Minor Changes - 51bfff683: Mint/burn limit checking for xERC20 bridging Corrects CLI output for HypXERC20 and HypXERC20Lockbox deployments ### Patch Changes - Updated dependencies [`51bfff683`] - @hyperlane-xyz/sdk@3.15.0 - @hyperlane-xyz/utils@3.15.0 ## @hyperlane-xyz/sdk@3.15.0 ### Minor Changes - 51bfff683: Mint/burn limit checking for xERC20 bridging Corrects CLI output for HypXERC20 and HypXERC20Lockbox deployments ### Patch Changes - Updated dependencies [`51bfff683`] - @hyperlane-xyz/core@3.15.0 - @hyperlane-xyz/utils@3.15.0 ## @hyperlane-xyz/helloworld@3.15.0 ### Patch Changes - Updated dependencies [`51bfff683`] - @hyperlane-xyz/sdk@3.15.0 - @hyperlane-xyz/core@3.15.0 ## @hyperlane-xyz/utils@3.15.0 ## @hyperlane-xyz/infra@3.15.0 ### Patch Changes - Updated dependencies [`51bfff683`] - @hyperlane-xyz/sdk@3.15.0 - @hyperlane-xyz/helloworld@3.15.0 - @hyperlane-xyz/utils@3.15.0 ## @hyperlane-xyz/ccip-server@3.15.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	6 months ago
github-actions[bot]	cb9c2aa571	Version Packages (#3910 ) 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/cli@3.14.0 ### Minor Changes - f4bbfcf08: AVS deployment on mainnet ### Patch Changes - @hyperlane-xyz/sdk@3.14.0 - @hyperlane-xyz/utils@3.14.0 ## @hyperlane-xyz/core@3.14.0 ### Patch Changes - a8a68f6f6: fix: make XERC20 and XERC20 Lockbox proxy-able - @hyperlane-xyz/utils@3.14.0 ## @hyperlane-xyz/helloworld@3.14.0 ### Patch Changes - Updated dependencies [`a8a68f6f6`] - @hyperlane-xyz/core@3.14.0 - @hyperlane-xyz/sdk@3.14.0 ## @hyperlane-xyz/sdk@3.14.0 ### Patch Changes - Updated dependencies [`a8a68f6f6`] - @hyperlane-xyz/core@3.14.0 - @hyperlane-xyz/utils@3.14.0 ## @hyperlane-xyz/utils@3.14.0 ## @hyperlane-xyz/infra@3.14.0 ### Patch Changes - @hyperlane-xyz/helloworld@3.14.0 - @hyperlane-xyz/sdk@3.14.0 - @hyperlane-xyz/utils@3.14.0 ## @hyperlane-xyz/ccip-server@3.14.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	6 months ago
Daniel Savu	5a31e7b5d3	chore: debug slow relayer startup (#3932 ) ### Description Opened this PR to debug slow relayer startup, but it actually looks like that's already been fixed by hook indexing. The requirement for fast startup is that the processor sees new messages and then one of the following happens: - (1) if the message is meant for an unknown domain, it drops it ([this log](`6d132b02a3/rust/agents/relayer/src/msg/processor.rs (L269)`)), otherwise - it forwards the message to the submitter, which then: - (2) adds it straight to the confirm queue because it's already been submitted ([here](`6d132b02a3/rust/agents/relayer/src/msg/pending_message.rs (L159)`)) - (3) successfully builds metadata ([here](`6d132b02a3/rust/agents/relayer/src/msg/op_submitter.rs (L231)`)) - (4) in some cases building metadata fails because the ism doesn't exist The relayer logs either of the four cases (in most cases (2), because we're running a second relayer for now). To be even more confident in fast startup, I ran a single relayer and restarted it. New messages were successfully processed according to one of the four cases above, and the prep queues didn't increase ### 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 -->	6 months ago
Mohammed Hussan	36e9a2e783	feat(infra): Command to create endpoint secrets; cleaning up endpoints (#3922 ) ### Description - clean up references to the single rpc secrets which are redundant as the multi rpc secret includes the single one - add get-rpc-urls script to get secret rpc urls for a given environment and chain - add set-rpc-urls script to: 1) create the secret if it does not exist and add the first secret version or 2) add new secret version to an existing secret and disable the previous version of the secret. The script with test all rpc urls to ensure that they are valid example usage: get-rpc-urls `yarn tsx scripts/secret-rpc-urls/get-rpc-urls.ts -e testnet2 -c fuji` set-rpc-urls `yarn tsx scripts/secret-rpc-urls/set-rpc-urls.ts -e testnet2 -c fuji -r https://api.avax-test.network/ext/bc/C/rpc,https://rpc.ankr.com/avalanche_fuji` <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> - replace `withNetwork` util with `withChain` as we rarely use network internally to reference a chain ### 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 <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->	6 months ago
Mohammed Hussan	cfa20a46fa	chore(infra): Update docker image tag for kathy and key funder (#3902 ) ### Description Update docker image tag for kathy and key funder <!-- 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 -->	6 months ago
Mohammed Hussan	efa9025f5e	chore(infra): Remove RpcConsensusType usage in infra now that SmartProvider is used instead (#3882 ) ### Description Removed references to RpcConsensusType where TS-based providers are used in infra <!-- 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 -->	6 months ago
Kunal Arora	554f875ebf	feat: core deployment on Holesky (#3776 ) ### Description Core deployment on Holesky ### Drive-by changes None ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3597 ### Backward compatibility Yes ### Testing Manual	6 months ago
Trevor Porter	db9f733e4f	fix: use secret RPC urls in infra, apply environment-specific registry overrides (#3875 ) ### Description A while back, it seems secret RPC URLs stopped being used by monorepo services (see https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3179/files#diff-ba3b7bea2b5c046acd88d25ed382df875b49d77e061f2ef8347ffcc741c0353eR34). This adds them back. Some things to note on the approach: - Sadly, due to the way some of the infra config generation works, we're forced to use synchronous interfaces for getting chain metadata in a bunch of places. This is why `getRegistry` returns a `FileSystemRegistry`, which is a `SynchronousRegistry`. - Applying secrets / overrides requires us to do things async for two reasons -- one is just that fetching from GCP secrets is an async operation, the other is that a `MergedRegistry` is not a `SynchronousRegistry`. The approach I've taken is that there are two ways of getting a registry - using `getRegistry` will give the synchronous version that can continue to be used by our sync config generation, but it won't have any environment-specific overrides (tx overrides or secrets). To get an async registry with environment-specific overrides, the `getRegistry` function on the EnvironmentConfig is used. - Overrides are now more succinct as the merging happens later in the pipeline ### Drive-by changes - Started moving away from using the gcloud CLI under the hood for GCP operations and toward using the GCP secret SDK - Updated the mainnet3 key funder to fix an incident, but will follow up with a fresh deploy once this is mergd ### Related issues - These are the code changes for https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3774, but I'll follow up with fresh deploys for the monorepo services ### 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: Connor McEwen <connor.mcewen@gmail.com> Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz> Co-authored-by: J M Rossy <jm.rossy@gmail.com>	6 months ago
github-actions[bot]	8a6654477e	Version Packages (#3842 ) 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.13.0 ### Minor Changes - babe816f8: Support xERC20 and xERC20 Lockbox in SDK and CLI - b440d98be: Added support for registering/deregistering from the Hyperlane AVS ### Patch Changes - Updated dependencies [`0cf692e73`] - @hyperlane-xyz/utils@3.13.0 ## @hyperlane-xyz/cli@3.13.0 ### Minor Changes - b22a0f453: Add hyperlane validator address command to retrieve validator address from AWS - 39ea7cdef: Implement multi collateral warp routes - babe816f8: Support xERC20 and xERC20 Lockbox in SDK and CLI - b440d98be: Added support for registering/deregistering from the Hyperlane AVS ### Patch Changes - b6b26e2bb: fix: minor change was breaking in registry export - Updated dependencies [`39ea7cdef`] - Updated dependencies [`babe816f8`] - Updated dependencies [`0cf692e73`] - @hyperlane-xyz/sdk@3.13.0 - @hyperlane-xyz/utils@3.13.0 ## @hyperlane-xyz/sdk@3.13.0 ### Minor Changes - 39ea7cdef: Implement multi collateral warp routes - babe816f8: Support xERC20 and xERC20 Lockbox in SDK and CLI - 0cf692e73: Implement metadata builder fetching from message ### Patch Changes - Updated dependencies [`babe816f8`] - Updated dependencies [`b440d98be`] - Updated dependencies [`0cf692e73`] - @hyperlane-xyz/core@3.13.0 - @hyperlane-xyz/utils@3.13.0 ## @hyperlane-xyz/utils@3.13.0 ### Minor Changes - 0cf692e73: Implement metadata builder fetching from message ## @hyperlane-xyz/helloworld@3.13.0 ### Patch Changes - b6b26e2bb: fix: minor change was breaking in registry export - Updated dependencies [`39ea7cdef`] - Updated dependencies [`babe816f8`] - Updated dependencies [`b440d98be`] - Updated dependencies [`0cf692e73`] - @hyperlane-xyz/sdk@3.13.0 - @hyperlane-xyz/core@3.13.0 ## @hyperlane-xyz/infra@3.13.0 ### Minor Changes - 39ea7cdef: Implement multi collateral warp routes - 0cf692e73: Implement metadata builder fetching from message ### Patch Changes - b6b26e2bb: fix: minor change was breaking in registry export - Updated dependencies [`b6b26e2bb`] - Updated dependencies [`39ea7cdef`] - Updated dependencies [`babe816f8`] - Updated dependencies [`0cf692e73`] - @hyperlane-xyz/helloworld@3.13.0 - @hyperlane-xyz/sdk@3.13.0 - @hyperlane-xyz/utils@3.13.0 ## @hyperlane-xyz/ccip-server@3.13.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	6 months ago
Yorke Rhodes	0cf692e731	Implement metadata fetching from message (#3702 ) ### Description - Uses derived hook and ISM config and dispatchTx of message to implement metadata fetching ### Drive-by changes - Change yarn cache key to workaround https://github.com/actions/toolkit/issues/658 - Make `hyperlane message send` use `HyperlaneCore.sendMessage` ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3450 ### Backward compatibility Yes ### Testing E2E testing BaseMetadataBuilder	6 months ago
Connor McEwen	b6b26e2bb8	fix: minor change was breaking in registry export (#3821 ) ### Description Fixes compat with with breaking changes in registry 1.3.0 --------- Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz> Co-authored-by: J M Rossy <jm.rossy@gmail.com>	6 months ago
Trevor Porter	704675c7e1	chore: update infra service images (key funder, kathy) (#3843 ) ### Description - Updates key funder and kathy images on testnet4 and mainnet3 - Sorts desired balances and is more explicit about requirements for kathy chains (https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3732 will expand on this to make sure we keep this up to date) - I found it surprising that if the kathy balance wasn't specified in the config, then key funder would default to funding the full relayer amount. Made this not be the case ### 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: Paul Balaji <paul@hyperlane.xyz>	6 months ago
Yorke Rhodes	39ea7cdef9	feat: multi collateral warp routes (#3820 ) ### Description Adds multicollateral warp route support to the CLI. Dedupes SDK warp route types and zod schemas (via type inference). ### Drive-by changes - Removes scattered ICA logic from deployers in favor of config time resolution ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3639 ### Backward compatibility - No ### Testing - E2E Tests	6 months ago
Trevor Porter	37af3dc6ba	feat: deploy to zetachain and redstone (#3788 ) ### Description - Deploys to zetachain and redstone - Some learnings can be found in https://discord.com/channels/935678348330434570/1240168332813144084 Chains not yet fully connected: - inevm (Mailbox ownership situation makes this hard) - mantapacific (waiting on an update to the multisig ownership set there, then will create the tx) - non-EVM chains ### Drive-by changes - decreased ethereum cost from $2 to $1.5 following some feedback - Added Superform to the blast set - Allowed for concurrent deploys I originally had some ugly caching to avoid checking storage gas oracles so much (we check them for each route in a routing hook configuration), but I've removed this. Calling it out for the future though `232695dd6c` ### 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 -->	6 months ago
Trevor Porter	335a0d7479	feat: add agent config for Osmosis Mainnet (#3825 ) ### Description - Added agent config description for Osmosis Mainnet - Updated infra test to allow agent config chains to be a superset of infra chains Taken from @byeongsu-hong's https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3766, but with a fixed test ### 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: byeongsu-hong <hong@byeongsu.dev>	6 months ago
Trevor Porter	a574b76584	Update clusters to use new prometheus version (#3772 ) ### Description GKE was complaining that the kube-state-metrics version we were running with was hitting deprecated APIs, I expect this to fix it. Some minor changes to the infra setup meant that now the push gateway has a different service name, kinda annoyingly with a double `prometheus` in the name. I updated key funder to push to the new gateway ### Drive-by changes We no longer use GKE autopilot, so started using the node exporter too ### 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 -->	6 months ago
Kunal Arora	3145be2543	fix: change version to 3.12.2 (#3801 ) ### 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 -->	7 months ago
github-actions[bot]	7294ea963f	Version Packages (#3752 ) 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/cli@3.12.0 ### Minor Changes - cc8731985: Default to home directory for local registry - ff221f66a: Allows a developer to pass a private key or address to dry-run, and ensures HYP_KEY is only used for private keys. - eba393680: Add CLI-side submitter to use SDK submitter from CRUD and other command modules. ### Patch Changes - 2b7dfe27e: Improve defaults in chain config command - Updated dependencies [`eba393680`] - Updated dependencies [`69de68a66`] - @hyperlane-xyz/sdk@3.12.0 - @hyperlane-xyz/utils@3.12.0 ## @hyperlane-xyz/sdk@3.12.0 ### Minor Changes - 69de68a66: Implement aggregation and multisig ISM metadata encoding ### Patch Changes - eba393680: Exports submitter and transformer props types. - Updated dependencies [`69de68a66`] - @hyperlane-xyz/utils@3.12.0 - @hyperlane-xyz/core@3.12.0 ## @hyperlane-xyz/utils@3.12.0 ### Minor Changes - 69de68a66: Implement aggregation and multisig ISM metadata encoding ## @hyperlane-xyz/core@3.12.0 ### Patch Changes - Updated dependencies [`69de68a66`] - @hyperlane-xyz/utils@3.12.0 ## @hyperlane-xyz/helloworld@3.12.0 ### Patch Changes - Updated dependencies [`eba393680`] - Updated dependencies [`69de68a66`] - @hyperlane-xyz/sdk@3.12.0 - @hyperlane-xyz/core@3.12.0 ## @hyperlane-xyz/infra@3.12.0 ### Patch Changes - Updated dependencies [`eba393680`] - Updated dependencies [`69de68a66`] - @hyperlane-xyz/sdk@3.12.0 - @hyperlane-xyz/utils@3.12.0 - @hyperlane-xyz/helloworld@3.12.0 ## @hyperlane-xyz/ccip-server@3.12.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	7 months ago
Trevor Porter	03ca2d1df7	Update gas oracles, deploy agents (#3755 ) ### Description - Updates gas oracles to make messages to Scroll slightly cheaper - After running into issues configuring non-EVM remotes in the IGP / gas oracle tooling (see https://discord.com/channels/935678348330434570/1238439687165579264), added a temporary band aid of just try/catching. We'll want to fix this at some point in the future - Deploys agents with a new image - Updates the agent JSON configs with some params we were running the agents with in prod via env vars - Adjusts kathy frequency on testnet to send every 1.5hrs instead of 7hrs - Stops running eclipsetestnet agents - apparently there was a reset ### Drive-by changes Some drive-by logging changes ### Related issues n/a ### 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 -->	7 months ago
Daniel Savu	be43b0fd91	feat: use batching configs on all execution environments (#3723 ) ### Description While we only have a tx batching implementation available for EVM chains, we still parallelize the `prepare` and `confirm` steps in the serial submitter according to the `maxBatchSize` config item. To reap the benefits of this change, we need to make these configs universal, because they were only defined within `h_eth::ChainConnectionConf`. This PR adds slight duplication because it adds the batching config on each individual connection config, but it's far simpler than including it in the `ChainConf` struct. The latter would've required changing all the trait impls of `BuildableWithProvider` to include the batching config. ### Drive-by changes Renames `serial_submitter` to `op_submitter` since it's no longer serial. ### Related issues Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3722 ### Backward compatibility Yes ### Testing Manually - added the configs to cosmos e2e and checked the logs	7 months ago
Trevor Porter	1cf6ccace2	Always get endpoint and endpoints secrets in helm charts (#3686 ) ### Description Noticed that the logic used by the key funder's helm chart to decide whether to fetch endpoint (singular) or endpoints (plural) from secrets was stale. This is because fallback was introduced later, and the logic was looking for quorum - so with the key funder config saying we wanted to use fallback provider, we weren't ever fetching the plural endpoints from secrets Imo the branching is a bit unnecessary and prone to becoming stale, so I removed it so that we just get both secrets from GCP secrets. Also redeployed key funder to get the correct secrets ### 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 -->	7 months ago
github-actions[bot]	cc7e8d90e0	Version Packages (#3718 ) # Releases ## @hyperlane-xyz/core@3.11.1 ### Patch Changes - @hyperlane-xyz/utils@3.11.1 ## @hyperlane-xyz/cli@3.11.1 ### Patch Changes - 78b77eecf: Fixes for CLI dry-runs - Updated dependencies [`c900da187`] - @hyperlane-xyz/sdk@3.11.1 - @hyperlane-xyz/utils@3.11.1 ## @hyperlane-xyz/helloworld@3.11.1 ### Patch Changes - Updated dependencies [`c900da187`] - @hyperlane-xyz/sdk@3.11.1 - @hyperlane-xyz/core@3.11.1 ## @hyperlane-xyz/sdk@3.11.1 ### Patch Changes - c900da187: Workaround TS bug in Safe protocol-lib - @hyperlane-xyz/core@3.11.1 - @hyperlane-xyz/utils@3.11.1 ## @hyperlane-xyz/utils@3.11.1 ## @hyperlane-xyz/infra@3.11.1 ### Patch Changes - Updated dependencies [`c900da187`] - @hyperlane-xyz/sdk@3.11.1 - @hyperlane-xyz/helloworld@3.11.1 - @hyperlane-xyz/utils@3.11.1 ## @hyperlane-xyz/ccip-server@3.11.1 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	7 months ago
J M Rossy	c900da1877	Workaround TS bug in Safe protocol-lib (#3717 ) ### Description Replace SDK's `gnosisSafe.ts` utils file with a pure JS version to avoid TS checks on Safe lib which has an incorrectly placed TS file in it's lib dist folder. ### Drive-by changes Fix assert import ## Related issues https://github.com/safe-global/safe-core-sdk/issues/805	7 months ago
Daniel Savu	8e5ef272a6	fix: agent config check, run relayer on mantapacific (#3714 ) ### 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 -->	7 months ago
github-actions[bot]	6f9c7511c7	Version Packages (#3533 ) 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.11.0 ### Minor Changes - b6fdf2f7f: Implement XERC20 and FiatToken collateral warp routes - b63714ede: Convert all public hyperlane npm packages from CJS to pure ESM ### Patch Changes - Updated dependencies [`b63714ede`] - Updated dependencies [`2b3f75836`] - Updated dependencies [`af2634207`] - @hyperlane-xyz/utils@3.11.0 ## @hyperlane-xyz/cli@3.11.0 ### Minor Changes - f8b6ea467: Update the warp-route-deployment.yaml to a more sensible schema. This schema sets us up to allow multi-chain collateral deployments. Removes intermediary config objects by using zod instead. - b6fdf2f7f: Implement XERC20 and FiatToken collateral warp routes - aea79c686: Adds single-chain dry-run support for deploying warp routes & gas estimation for core and warp route dry-run deployments. - 917266dce: Add --self-relay to CLI commands - b63714ede: Convert all public hyperlane npm packages from CJS to pure ESM - 450e8e0d5: Migrate fork util from CLI to SDK. Anvil IP & Port are now optionally passed into fork util by client. - 3528b281e: Restructure CLI params around registries - af2634207: Introduces `hyperlane hook read` and `hyperlane ism read` commands for deriving onchain Hook/ISM configs from an address on a given chain. ### Patch Changes - 8246f14d6: Adds defaultDescription to yargs --key option. - Updated dependencies [`811ecfbba`] - Updated dependencies [`f8b6ea467`] - Updated dependencies [`d37cbab72`] - Updated dependencies [`b6fdf2f7f`] - Updated dependencies [`a86a8296b`] - Updated dependencies [`2db77f177`] - Updated dependencies [`3a08e31b6`] - Updated dependencies [`917266dce`] - Updated dependencies [`aab63d466`] - Updated dependencies [`2e439423e`] - Updated dependencies [`b63714ede`] - Updated dependencies [`3528b281e`] - Updated dependencies [`450e8e0d5`] - Updated dependencies [`2b3f75836`] - Updated dependencies [`af2634207`] - @hyperlane-xyz/sdk@3.11.0 - @hyperlane-xyz/utils@3.11.0 ## @hyperlane-xyz/helloworld@3.11.0 ### Minor Changes - b63714ede: Convert all public hyperlane npm packages from CJS to pure ESM ### Patch Changes - Updated dependencies [`811ecfbba`] - Updated dependencies [`f8b6ea467`] - Updated dependencies [`d37cbab72`] - Updated dependencies [`b6fdf2f7f`] - Updated dependencies [`a86a8296b`] - Updated dependencies [`2db77f177`] - Updated dependencies [`3a08e31b6`] - Updated dependencies [`917266dce`] - Updated dependencies [`aab63d466`] - Updated dependencies [`2e439423e`] - Updated dependencies [`b63714ede`] - Updated dependencies [`3528b281e`] - Updated dependencies [`450e8e0d5`] - Updated dependencies [`af2634207`] - @hyperlane-xyz/sdk@3.11.0 - @hyperlane-xyz/core@3.11.0 ## @hyperlane-xyz/sdk@3.11.0 ### Minor Changes - 811ecfbba: Add EvmCoreReader, minor updates. - f8b6ea467: Update the warp-route-deployment.yaml to a more sensible schema. This schema sets us up to allow multi-chain collateral deployments. Removes intermediary config objects by using zod instead. - d37cbab72: Adds modular transaction submission support for SDK clients, e.g. CLI. - b6fdf2f7f: Implement XERC20 and FiatToken collateral warp routes - 2db77f177: Added RPC `concurrency` property to `ChainMetadata`. Added `CrudModule` abstraction and related types. Removed `Fuel` ProtocolType. - 3a08e31b6: Add EvmERC20WarpRouterReader to derive WarpConfig from TokenRouter address - 917266dce: Add --self-relay to CLI commands - aab63d466: Adding ICA for governance - b63714ede: Convert all public hyperlane npm packages from CJS to pure ESM - 3528b281e: Remove consts such as chainMetadata from SDK - 450e8e0d5: Migrate fork util from CLI to SDK. Anvil IP & Port are now optionally passed into fork util by client. - af2634207: Moved Hook/ISM config stringify into a general object stringify utility. ### Patch Changes - a86a8296b: Removes Gnosis safe util from infra in favor of SDK - 2e439423e: Allow gasLimit overrides in the SDK/CLI for deploy txs - Updated dependencies [`b6fdf2f7f`] - Updated dependencies [`b63714ede`] - Updated dependencies [`2b3f75836`] - Updated dependencies [`af2634207`] - @hyperlane-xyz/core@3.11.0 - @hyperlane-xyz/utils@3.11.0 ## @hyperlane-xyz/utils@3.11.0 ### Minor Changes - b63714ede: Convert all public hyperlane npm packages from CJS to pure ESM - af2634207: Moved Hook/ISM config stringify into a general object stringify utility. ### Patch Changes - 2b3f75836: Add objLength and isObjEmpty utils ## @hyperlane-xyz/infra@3.11.0 ### Minor Changes - af2634207: Moved Hook/ISM reading into CLI. ### Patch Changes - a86a8296b: Removes Gnosis safe util from infra in favor of SDK - Updated dependencies [`811ecfbba`] - Updated dependencies [`f8b6ea467`] - Updated dependencies [`d37cbab72`] - Updated dependencies [`b6fdf2f7f`] - Updated dependencies [`a86a8296b`] - Updated dependencies [`2db77f177`] - Updated dependencies [`3a08e31b6`] - Updated dependencies [`917266dce`] - Updated dependencies [`aab63d466`] - Updated dependencies [`2e439423e`] - Updated dependencies [`b63714ede`] - Updated dependencies [`3528b281e`] - Updated dependencies [`450e8e0d5`] - Updated dependencies [`2b3f75836`] - Updated dependencies [`af2634207`] - @hyperlane-xyz/sdk@3.11.0 - @hyperlane-xyz/helloworld@3.11.0 - @hyperlane-xyz/utils@3.11.0 ## @hyperlane-xyz/ccip-server@3.11.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	7 months ago
Daniel Savu	5aeb83a2e5	Relayer Message Batching to EVM (#3656 ) ### Description Status: - [x] op-queue scaffolding - [x] hyperlane-ethereum integration with multicall - [x] new config items - [x] actually build batch in the op-queue submit step - [x] e2e tests with batching configured - [x] dynamic batch sizes (batch as many messages as the prepare step has ready) - [x] parallelize metadata building - [ ] proportional IGP deduction ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Fixes #3628 - Fixes #3630 ### 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 <tkporter4@gmail.com>	7 months ago
Noah Bayindirli 🥂	a86a8296b2	export tx provider from sdk & remove safe util from infra (#3694 ) ### Description * Exports new tx provider + Gnosis safe util from SDK * Removes the Gnosis safe util from infra ### Drive-by changes * Reminder to add a changeset * Output: ``` ➜ hyperlane-monorepo-official git:(noah/move-safe) ✗ git commit -m "add changeset reminder to husky script" → No staged files match any configured task. 📝 If you haven't yet, please add a changeset for your changes via 'yarn changeset' [noah/move-safe `3e668d0a7`] add changeset reminder to husky script 1 file changed, 2 insertions(+) ``` ### Related issues * Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3684 ### Backward compatibility * Yes ### Testing * n/a	7 months ago
J M Rossy	3528b281e3	Migrate SDK consts to Registry and use new registry utilities (#3615 ) ### Description - Remove most consts from SDK - Refactor tests that relied on chainMetadata - Remove JSON imports/exports in the SDK - Update the HelloWorld package to read metadata from the registry lib - Update the Infra package to read/write to a LocalRegistry - Update the CLI to read and write from registries ### Drive-by changes - Fix typo in `EvmHypCollateralVault` token standard - Use consistent, newest yaml lib version ### Related issues Fixes https://github.com/hyperlane-xyz/issues/issues/917 Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2810 ### Backward compatibility No: - Several SDK exports like `chainMetadata` have been removed - Common args for the CLI like `--chain` have been replaced with `--registry` and `--overrides`	7 months ago
Yorke Rhodes	292879126c	Ensure owners are configured correctly (#3677 ) ### Description Fixes owner config to be safes ### Backward compatibility Yes	7 months ago
Trevor Porter	c4b7ad3196	Update Mode and Blast validator sets & gas oracles (#3669 ) ### 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: nambrot <nambrot@googlemail.com>	7 months ago
Trevor Porter	21cd38c2f3	Update IGP gas oracles with new heuristics, get Cosmos gas prices from registry (#3662 ) ### Description The original and main motivation of this PR was to feel confident when running `deploy.ts -m igp` off of main. Prior to this, running it off main could result in misconfiguring gas oracles, particularly when it came to non-EVM remotes. See https://github.com/hyperlane-xyz/issues/issues/1178 for some context. This PR does a number of things: - Fetches Cosmos gas prices from the Cosmos registry - the `gasPrices.json` now lets you specify the decimals relating to the amount in there. There are 2 reasons for this: it's easier for us to deal with gwei values for EVM chains (as we often end up manually changing these instead of just relying on the script). The second reason is covered in the next bullet - Handles decimals when it comes to gas prices. The existing tooling assumed gas prices would always be denominated in wei. An extra weird situation arises with non-EVM chains: chains like Neutron have gas prices that are quotes in the smallest denomination (ie the equivalent of "wei" for NTRN), but the gas price is not an integer and is very small, e.g. `0.0053`. This poses issues because the IGP contracts require the gas price that's configured onchain to be an integer. Simply rounding up from 0.0053 to 1 results in almost 2 orders of magnitude difference :(. So the solution here is to have some logic that accommodates really tiny gas prices by scaling up the configured gas price and scaling down the configured token exchange rate. - Applies some "non-linear" gas pricing heuristics. See https://github.com/hyperlane-xyz/issues/issues/1204 and https://discord.com/channels/935678348330434570/935678739663192184/1232293417309044818 for some context - Running `update-agent-config.ts` will fetch gas prices for Cosmos chains from the Cosmos registry and ensure they're accurate ### Drive-by changes Some logging messages when applying IGP gas oracle changes to make it more clear what the change actually does ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3386 - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3484 - Fixes https://github.com/hyperlane-xyz/issues/issues/1178 - Fixes https://github.com/hyperlane-xyz/issues/issues/1206 - Fixes https://github.com/hyperlane-xyz/issues/issues/1204 ### Backward compatibility Fully backward compatible ### Testing Ran deploy.ts for the IGP on all chains! --------- Co-authored-by: nambrot <nambrot@googlemail.com>	7 months ago
Paul Balaji	af26342079	feat: add `hyperlane hook read` + `hyperlane ism read` to cli (#3648 )	7 months ago
Trevor Porter	d6f25ed035	Deploy to Mode & Blast (#3653 ) ### 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 -->	7 months ago
Trevor Porter	6f35e4ce58	Ancient8 key funder; add inevm claim threshold (#3619 ) ### 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 -->	7 months ago
Trevor Porter	6c42a6458d	Deploy RC relayer for extra throughput (#3620 ) ### Description See https://discord.com/channels/935678348330434570/1230452070696484956 for context. General idea as a stopgap is to run a relayer concurrent with the Hyperlane one ### 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 -->	7 months ago
Trevor Porter	700240eb8a	Ancient8 new ism, misc infra fixes (#3606 ) ### Description - Deploys ancient8 with a new ISM where we are not quorum - Pulls out warp config to live in a single file / function so that deploy.ts and check-deploy.ts are in sync. Otherwise fork.sh is broken for warp routes - Shuffles around the aw multisig serialization stuff - now they're segmented by environment and context and are written to `config/{env}/aw-validators/{context}.json`. This was in response to some confusing merging logic, see https://discord.com/channels/935678348330434570/1228377321082327141/1229464197297868910 ### Drive-by changes Needed to specify pino to work in pretty mode for warp monitoring :/ this is necessary because pino doesn't work otherwise. After #3582 we should change this ### 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 -->	8 months ago

1 2 3 4 5 ...

702 Commits (b54c14cd31be541c06ca42a50ec2ef32e983653f)