753 Commits (a7ab950246e115d74394ed74ca54c1085e69439a)

Author	SHA1	Message	Date
github-actions[bot]	ec447febc6	Version Packages (#4103) ... 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@5.0.0 ### Major Changes - f1d70a5e8: refactor: select chain now become 2 step, select mainnet/testnet type first, then select chain ### Minor Changes - 388d25517: Added HyperlaneRelayer for relaying messages from the CLI - d0f7f21fd: Fix logging for hyperlane core apply - d00f2ffc0: Displays formatted deployment plan to confirm warp deploy. - 40255575c: Adds blockExplorers option on registry init. - 708999433: Adds hyperlane warp apply - 0e1a80e6e: Improve chain metadata and address fetching from github registries - 5529d98d0: Add hyperlane core apply with update ownership - 62d71fad3: Add hyperlane warp update to extend a warp config - 49986aa92: Add collateralAddressOrDenom for collateralVault - ded5718a0: Update hyperlane core read to log the config terminal "preview", only if the number of lines is &lt; 250 - 5125b798d: Prompt for chain testnet/mainnet during chain definition flow - bb470aec2: Add 'submit' command to CLI. ### Patch Changes - 80ac5d28e: Display token symbol when balance is insufficient for command - 6341edf2a: fix: use merkle tree hook address from registry for self relay hook derivations - c539775d7: Default to mailbox address in registry - c2a2897d7: Update CLI verbiage to ask for vault and not token when initiating collateralVault warp route. - Updated dependencies [2c0ae3cf3] - Updated dependencies [0dedbf5a0] - Updated dependencies [388d25517] - Updated dependencies [69a39da1c] - Updated dependencies [4907b510c] - Updated dependencies [488f949ef] - Updated dependencies [c7f5a35e8] - Updated dependencies [7265a4087] - Updated dependencies [0a40dcb8b] - Updated dependencies [f83b492de] - Updated dependencies [79740755b] - Updated dependencies [8533f9e66] - Updated dependencies [ed65556aa] - Updated dependencies [ab827a3fa] - Updated dependencies [dfa908796] - Updated dependencies [ed63e04c4] - Updated dependencies [dfa908796] - Updated dependencies [5aa24611b] - Updated dependencies [cfb890dc6] - Updated dependencies [708999433] - Updated dependencies [5529d98d0] - Updated dependencies [62d71fad3] - Updated dependencies [49986aa92] - Updated dependencies [7fdd3958d] - Updated dependencies [8e942d3c6] - Updated dependencies [fef629673] - Updated dependencies [be4617b18] - Updated dependencies [1474865ae] - @hyperlane-xyz/sdk@5.0.0 - @hyperlane-xyz/utils@5.0.0 ## @hyperlane-xyz/sdk@5.0.0 ### Major Changes - 488f949ef: Upgrade CosmJS libs to 0.32.4 ### Minor Changes - 2c0ae3cf3: Deploy to connextsepolia + superpositiontestnet - 0dedbf5a0: Deploy to endurance, fusemainnet, zoramainnet - 388d25517: Added HyperlaneRelayer for relaying messages from the CLI - 4907b510c: Add logic to parse SmartProvider errors to handle ethers and smart provider errors - c7f5a35e8: Add hyperlane core apply with update default Ism - f83b492de: - Enable updating of hooks through the `EvmHookModule`, including IGP and gas oracles. - Drive-by fixes to ISM module and tests. - 79740755b: Add enroll remote router to WarpModule - 8533f9e66: Adds transferOwnership to warp update to allow ownership to be transferred if the onchain owner differ - ed65556aa: Improve WarpCore validation error message for IGP fee checks - cfb890dc6: Remove outdated logos in SDK (now in registry) - 708999433: Adds hyperlane warp apply - 5529d98d0: Add hyperlane core apply with update ownership - 62d71fad3: Add hyperlane warp update to extend a warp config - 49986aa92: Add collateralAddressOrDenom for collateralVault - 8e942d3c6: Deploy to cheesechain, worldchain, xlayer ### Patch Changes - 69a39da1c: Fix issue with cosmos tx estimation - 7265a4087: Add rpcUrl, chainId, and method(params) to smart provider logging. - 0a40dcb8b: Update cosmos chain schema - ab827a3fa: Removes innacurate contract verification check, resulting in proxy contracts not being marked as proxies during contract verification. - dfa908796: add error message for all calls to assert util - ed63e04c4: Creates HyperlaneReader to re-use dyn provider log level & silences provider logs in deriveIsmConfig like deriveHookConfig. - 5aa24611b: Add 'isInitialized' check before initializing implementation contract (for contracts that disableInitializers in constructors). - 7fdd3958d: Adds logic to prune and minify build artifacts to address 'entity size too large' error thrown from explorers. Note that the only identified instance of this issue is on BSC mainnet. - fef629673: ContractVerifier now adjusts timeouts based on explorer family, which helps with many rate-limiting related contract verification issues. In addition, the ContractVerifier verify logic has been greatly simplified to allowing for a predictable callstack + easy debugging. - be4617b18: Handle subdirectories for the folder in S3Validator class - Updated dependencies [388d25517] - Updated dependencies [488f949ef] - Updated dependencies [dfa908796] - Updated dependencies [90598ad44] - Updated dependencies [1474865ae] - @hyperlane-xyz/utils@5.0.0 - @hyperlane-xyz/core@5.0.0 ## @hyperlane-xyz/utils@5.0.0 ### Major Changes - 488f949ef: Upgrade CosmJS libs to 0.32.4 ### Minor Changes - 388d25517: Added HyperlaneRelayer for relaying messages from the CLI - dfa908796: set the errorMessage argument as required for assert util function ### Patch Changes - 1474865ae: Replace `configDeepEquals` with improve `deepEquals` ## @hyperlane-xyz/widgets@5.0.0 ### Minor Changes - 98eb680ad: Migrate hyperlane widgets lib to monorepo ### Patch Changes - Updated dependencies [2c0ae3cf3] - Updated dependencies [0dedbf5a0] - Updated dependencies [388d25517] - Updated dependencies [69a39da1c] - Updated dependencies [4907b510c] - Updated dependencies [488f949ef] - Updated dependencies [c7f5a35e8] - Updated dependencies [7265a4087] - Updated dependencies [0a40dcb8b] - Updated dependencies [f83b492de] - Updated dependencies [79740755b] - Updated dependencies [8533f9e66] - Updated dependencies [ed65556aa] - Updated dependencies [ab827a3fa] - Updated dependencies [dfa908796] - Updated dependencies [ed63e04c4] - Updated dependencies [5aa24611b] - Updated dependencies [cfb890dc6] - Updated dependencies [708999433] - Updated dependencies [5529d98d0] - Updated dependencies [62d71fad3] - Updated dependencies [49986aa92] - Updated dependencies [7fdd3958d] - Updated dependencies [8e942d3c6] - Updated dependencies [fef629673] - Updated dependencies [be4617b18] - @hyperlane-xyz/sdk@5.0.0 ## @hyperlane-xyz/core@5.0.0 ### Patch Changes - 90598ad44: Removed outbox as param for ArbL2ToL1Ism - Updated dependencies [388d25517] - Updated dependencies [488f949ef] - Updated dependencies [dfa908796] - Updated dependencies [1474865ae] - @hyperlane-xyz/utils@5.0.0 ## @hyperlane-xyz/helloworld@5.0.0 ### Patch Changes - Updated dependencies [2c0ae3cf3] - Updated dependencies [0dedbf5a0] - Updated dependencies [388d25517] - Updated dependencies [69a39da1c] - Updated dependencies [4907b510c] - Updated dependencies [488f949ef] - Updated dependencies [c7f5a35e8] - Updated dependencies [7265a4087] - Updated dependencies [0a40dcb8b] - Updated dependencies [f83b492de] - Updated dependencies [79740755b] - Updated dependencies [8533f9e66] - Updated dependencies [ed65556aa] - Updated dependencies [ab827a3fa] - Updated dependencies [dfa908796] - Updated dependencies [ed63e04c4] - Updated dependencies [5aa24611b] - Updated dependencies [cfb890dc6] - Updated dependencies [708999433] - Updated dependencies [5529d98d0] - Updated dependencies [62d71fad3] - Updated dependencies [49986aa92] - Updated dependencies [7fdd3958d] - Updated dependencies [8e942d3c6] - Updated dependencies [fef629673] - Updated dependencies [90598ad44] - Updated dependencies [be4617b18] - @hyperlane-xyz/sdk@5.0.0 - @hyperlane-xyz/core@5.0.0 ## @hyperlane-xyz/infra@5.0.0 ### Minor Changes - 388d25517: Added HyperlaneRelayer for relaying messages from the CLI ### Patch Changes - Updated dependencies [2c0ae3cf3] - Updated dependencies [0dedbf5a0] - Updated dependencies [388d25517] - Updated dependencies [69a39da1c] - Updated dependencies [4907b510c] - Updated dependencies [488f949ef] - Updated dependencies [c7f5a35e8] - Updated dependencies [7265a4087] - Updated dependencies [0a40dcb8b] - Updated dependencies [f83b492de] - Updated dependencies [79740755b] - Updated dependencies [8533f9e66] - Updated dependencies [ed65556aa] - Updated dependencies [ab827a3fa] - Updated dependencies [dfa908796] - Updated dependencies [ed63e04c4] - Updated dependencies [dfa908796] - Updated dependencies [5aa24611b] - Updated dependencies [cfb890dc6] - Updated dependencies [708999433] - Updated dependencies [5529d98d0] - Updated dependencies [62d71fad3] - Updated dependencies [49986aa92] - Updated dependencies [7fdd3958d] - Updated dependencies [8e942d3c6] - Updated dependencies [fef629673] - Updated dependencies [be4617b18] - Updated dependencies [1474865ae] - @hyperlane-xyz/sdk@5.0.0 - @hyperlane-xyz/utils@5.0.0 - @hyperlane-xyz/helloworld@5.0.0 ## @hyperlane-xyz/ccip-server@5.0.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	4 months ago
Trevor Porter	cffbfcac13	feat: fully testing ICA ownership with tooling (#4245) ... ### Description Some tweaks to get checker tooling working with ICA ownership: - changed the `inferCallSubmissionTypes` logic to no longer mutate `this.calls`. Some weird side effects were occurring, especially where the ICA logic would try to pop and push from `this.calls` while also looping over it. This is also why I made it serial again. I ended up moving away from mutating this.calls entirely during the iteration, so I guess moving back to doing it concurrently can be done again. Happy to do this if it feels good to - the only reason I haven't is this wasn't a place where we had huge inefficiencies and it'd complicate the code a little - Got it working where a Safe on chain A owns an ICA on chain B These are the flows I tested: - sepolia is the "owner chain" - deployed a warp route between sepolia and alfajores. Changed the alfajores owner to an ICA owned by the sepolia deployer key. Tested transferring ownership back from this to the deployer. - Did the exact same as above, but now with the ICA being owned by a Safe on sepolia - Transferred ownership of Alfajores core contracts to and from the sepolia-deployer-owned ICA These are some raw notes that may be of interest of what I did https://www.notion.so/hyperlanexyz/ICA-playground-996cf28aea1649a18051afb8bb82acb2 This doesn't auto-deploy ICAs. An ICA is expected to have been deployed already, and then just configured in `owners.ts`. Check-deploy figures out that it's an ICA and does all the rest. This is fine imo in the short term as I only imagine us using ICAs on two chains (inevm and viction) for the time being. ### 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 -->	4 months ago
Paul Balaji	c6bf71d1b3	chore: update registry to v2.4.0 (#4247) ... chore: update registry to v2.4.0 - pinned CI version updated to `d9fea91f16949a51b2c8e776bac26712ba1fef3d`, which includes some testnet updates after 2.4.0 (https://github.com/hyperlane-xyz/hyperlane-registry/pull/126) --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	4 months ago
Mohammed Hussan	c21a99abf8	feat(infra): ensure check-deploy covers ownable ISMs (#4236) ... ### Description - check-deploy will surface violations when the on-chain ISM state differs from the config for core and warp modules Example of running check-deploy when the warp config includes a new validator Vs on-chain ISM state ``` ┌─────────┬────────────┬────────┬──────────────┬─────────────┬─────────┬──────────────────────────────────────────────┬──────────────────────────────────────────────┐ │ (index) │ chain │ remote │ name │ type │ subType │ actual │ expected │ ├─────────┼────────────┼────────┼──────────────┼─────────────┼─────────┼──────────────────────────────────────────────┼──────────────────────────────────────────────┤ │ 0 │ 'ethereum' │ │ │ 'ClientIsm' │ │ [Object] │ [Object] │ │ 1 │ 'ethereum' │ │ 'collateral' │ 'Owner' │ │ '0x3965AC3D295641E452E0ea896a086A9cD7C6C5b6' │ '0xa7ECcdb9Be08178f896c26b7BbD8C3D4E844d9Ba' │ └─────────┴────────────┴────────┴──────────────┴─────────────┴─────────┴──────────────────────────────────────────────┴──────────────────────────────────────────────┘ Connection client violation ClientIsm details: + Added to config staticAggregationIsm.modules.0.merkleRootMultisigIsm.validators.3: "0xbb5842ae0e05215b53df4787a29144efb7e67551" + Added to config staticAggregationIsm.modules.1.messageIdMultisigIsm.validators.3: "0xbb5842ae0e05215b53df4787a29144efb7e67551" ~ Updated config staticAggregationIsm.modules.0.merkleRootMultisigIsm.validators.0: "0x95c7bf235837cb5a609fe6c95870410b9f68bcff" -> "0x4d966438fe9e2b1e7124c87bbb90cb4f0f6c59a1" ~ Updated config staticAggregationIsm.modules.0.merkleRootMultisigIsm.validators.1: "0xa5a56e97fb46f0ac3a3d261e404acb998d9a6969" -> "0x95c7bf235837cb5a609fe6c95870410b9f68bcff" ~ Updated config staticAggregationIsm.modules.0.merkleRootMultisigIsm.validators.2: "0xbb5842ae0e05215b53df4787a29144efb7e67551" -> "0xa5a56e97fb46f0ac3a3d261e404acb998d9a6969" ~ Updated config staticAggregationIsm.modules.1.messageIdMultisigIsm.validators.0: "0x95c7bf235837cb5a609fe6c95870410b9f68bcff" -> "0x4d966438fe9e2b1e7124c87bbb90cb4f0f6c59a1" ~ Updated config staticAggregationIsm.modules.1.messageIdMultisigIsm.validators.1: "0xa5a56e97fb46f0ac3a3d261e404acb998d9a6969" -> "0x95c7bf235837cb5a609fe6c95870410b9f68bcff" ~ Updated config staticAggregationIsm.modules.1.messageIdMultisigIsm.validators.2: "0xbb5842ae0e05215b53df4787a29144efb7e67551" -> "0xa5a56e97fb46f0ac3a3d261e404acb998d9a6969" ``` ### Backward compatibility Yes ### Testing Manual	4 months ago
Mohammed Hussan	8e942d3c6b	feat: deploy cheesechain, worldchain, xlayer (#4207) ... ### Description - Support deployment to cheesechain, worldchain and zlayer ### Drive-by changes - update `CosmosChainSchema` to add `chain_type` to fix breaking change introduced by 6854133f98	4 months ago
J M Rossy	488f949efa	chore: Upgrade CosmJS libs to 0.32.4 (#4209) ... ### Description - Upgrade CosmJS libs to 0.32.4 - Remove explorer dep from ccip-server ### Related issues https://github.com/hyperlane-xyz/hyperlane-warp-ui-template/issues/202 ### Backward compatibility No, major version bump required because CosmJS 0.32 is not backwards compatible with 0.31 ### Testing Tested in Warp UI	4 months ago
Mohammed Hussan	5c93f69238	feat(infra): support retrying safe proposal transactions (#4197) ... ### Description - This is required as some (Zetachain) safe transaction services are flaky <!-- 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 -->	4 months ago
Mohammed Hussan	957a262d54	feat: new validators (#4179) ... ### Description <!-- What's included in this PR? --> - Add new validators - Add new safes - make mapViolationsToCalls run in parallel ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> - improve `create-safe.ts` script to fetch and print the transaction service url with instruction to add it to registry ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: Trevor Porter <tkporter4@gmail.com>	4 months ago
Mohammed Hussan	944b2f65e1	feat(infra): Add script to create safes and add safe addresses for new chains (#4127) ... ### Description <!-- What's included in this PR? --> - Add an infra script to create a safe on specific chain using the `safeSigners.json` config where the safe signers are defined ### 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 --> Manual	4 months ago
Trevor Porter	7489a5e143	feat: start sending resource request metrics to grafana; bump scraper CPU requests (#4158) ... ### Description - Starts sending `kube_pod_container_resource_requests` to grafana - Useful for alerts that depend on the requests for a pod - Deployed prom servers on testnet4 and mainnet3 with this config change - Found that the scraper CPU requests are too low - bumped to 2 CPU - seemingly upon startup there's a pretty big CPU spike, so adjusted the requests to be within this spike. -  ### 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 -->	4 months ago
Trevor Porter	37b460193f	chore: deploy kathy (#4156) ... ### Description I didn't deploy kathy following https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3875 and we've hit some RPC issues ### 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 -->	4 months ago
Paul Balaji	0dedbf5a02	feat: deploy to new chains (endurance, fuse, zora) (#4148) ... - feat: deploy to new chains (endurance, fuse, zora) - https://github.com/hyperlane-xyz/issues/issues/1308 - also includes https://github.com/hyperlane-xyz/issues/issues/1305 - registry PR https://github.com/hyperlane-xyz/hyperlane-registry/pull/104	4 months ago
Yorke Rhodes	388d255171	feat: typescript relayer MVP (#3693) ... ### Description - implement `HyperlaneRelayer` as a wrapper around `HyperlaneCore` - add relaying to CLI status command - add infra script relay for an environment ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Touches https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3448 ### 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 --------- Co-authored-by: -f <kunalarora1729@gmail.com> Co-authored-by: Noah Bayindirli 🥂 <noah@primeprotocol.xyz>	4 months ago
Trevor Porter	74cd350db1	chore: update neutron relayer (#4154) ... ### Description updates relayer version, sets gas payment enforcement policy back to normal ### 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 -->	4 months ago
Trevor Porter	857338e2af	chore: update app contexts (#4136) ... ### Description - updating the ezETH metric app context on the relayer - adding merkly addresses to the app contexts - temporarily changing the gas payment enforcement for merkly ETH contracts to just require that some payment was made, this way we won't run into issues with https://github.com/hyperlane-xyz/issues/issues/1294 over the weekend. In practice it's just been the merkly eth contracts that cause this problem when they run out of liquidity - removed some warp route gas payment non-enforcement after we have hook indexing ### 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 -->	4 months ago
Paul Balaji	2c0ae3cf37	feat: deploy to new testnets (connextsepolia, superpositiontestnet) (#4150) ... - feat: deploy to new testnets (connextsepolia, superpositiontestnet) - https://github.com/hyperlane-xyz/issues/issues/1308 - also includes https://github.com/hyperlane-xyz/issues/issues/1305 - registry pr https://github.com/hyperlane-xyz/hyperlane-registry/pull/105	4 months ago
Paul Balaji	b9e8e049bb	chore(infra): strongly type `AgentChainConfig` (#4102) ... - follow on from https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4093 - ts errors in editor if a chain is missing from the config - makes it easier to update `ValidatorBaseChainConfigMap` in future one chain missing: <img width="298" alt="image" src="https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/10051819/0e3c6247-3967-4caa-afad-f7a16234a029"> multiple chains missing: <img width="310" alt="image" src="https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/10051819/241782ca-16a4-4b17-9873-706485e26649">	4 months ago
Mohammed Hussan	dc15860894	feat(infra): Add new warp monitor image tag (#4147) ... ### Description <!-- What's included in this PR? --> - Add new warp monitor image tag ### 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 -->	4 months ago
Mohammed Hussan	ef89a59b00	feat(infra): update ezeth warp monitor config (#4126) ... ### Description <!-- What's included in this PR? --> - update ezeth warp monitor config ### 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 -->	4 months ago
Nam Chu Hoai	5aa24611b3	fix(sdk): Renzo Fraxtal Deploy Fixes (#4115) ... ### Description - Initialized check before initializing implementation contract (for contracts that disableInitializers in constructors) - set gas overrides for renzo warp route deploys - check that validators are set - add TODOs for verifying routing ISMs (probably should be removed @ltyu ) --------- Co-authored-by: Noah Bayindirli 🥂 <15343884+nbayindirli@users.noreply.github.com> Co-authored-by: Noah Bayindirli 🥂 <noah@primeprotocol.xyz>	5 months ago
J M Rossy	0e1a80e6e0	chore: Bump registry version to 2.3.0 (#4114) ... ### Description Update to latest registry for faster and more efficient chain metadata/address fetching ### Related issues https://github.com/hyperlane-xyz/hyperlane-registry/issues/29 ### Backward compatibility Yes ### Testing Ran CLI registry commands locally	5 months ago
Mohammed Hussan	c5ab4425a7	chore(infra): Update warp monitor docker image (#4119) ... ### Description <!-- What's included in this PR? --> Update script to use the latest docker image ### 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
Mohammed Hussan	6cf3982589	feat(infra): Add xERC20 limits monitoring capabilities (#4071) ... ### Description <!-- What's included in this PR? --> - Add support for pushing limits metrics for xERC20 wrap routes - For now only push limits metrics for xERC20 wrap routes, not yet supporting warp route balances ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> - Fixes #4047 ### 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 --> Manual	5 months ago
github-actions[bot]	29050d262a	Version Packages (#4077) ... 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@4.1.0 ### Minor Changes - 4cc9327e5: Update warp deploy to handle xerc20, initializerArgs to be the signer, update deploy gas constants ### Patch Changes - 46652c62a: Fix the missing sorting in the YAML file generated - 56be527d6: Fix typo in core read command - 378a5b79f: Remove extra fields from warp core config - Updated dependencies [36e75af4e] - Updated dependencies [d31677224] - Updated dependencies [4cc9327e5] - Updated dependencies [1687fca93] - @hyperlane-xyz/sdk@4.1.0 - @hyperlane-xyz/utils@4.1.0 ## @hyperlane-xyz/sdk@4.1.0 ### Minor Changes - 36e75af4e: Add optional deployer field to ChainMetadata schema - d31677224: Deploy to bob, mantle, taiko - 4cc9327e5: Update warp deploy to handle xerc20, initializerArgs to be the signer, update deploy gas constants - 1687fca93: Add EvmWarpModule with update() for ISM ### Patch Changes - @hyperlane-xyz/core@4.1.0 - @hyperlane-xyz/utils@4.1.0 ## @hyperlane-xyz/core@4.1.0 ### Patch Changes - @hyperlane-xyz/utils@4.1.0 ## @hyperlane-xyz/helloworld@4.1.0 ### Patch Changes - Updated dependencies [36e75af4e] - Updated dependencies [d31677224] - Updated dependencies [4cc9327e5] - Updated dependencies [1687fca93] - @hyperlane-xyz/sdk@4.1.0 - @hyperlane-xyz/core@4.1.0 ## @hyperlane-xyz/utils@4.1.0 ## @hyperlane-xyz/infra@4.1.0 ### Minor Changes - d31677224: Deploy to bob, mantle, taiko ### Patch Changes - Updated dependencies [36e75af4e] - Updated dependencies [d31677224] - Updated dependencies [4cc9327e5] - Updated dependencies [1687fca93] - @hyperlane-xyz/sdk@4.1.0 - @hyperlane-xyz/helloworld@4.1.0 - @hyperlane-xyz/utils@4.1.0 ## @hyperlane-xyz/ccip-server@4.1.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	5 months ago
Paul Balaji	94e6ca21ee	feat(infra): strongly type keyfunder config (#4093) ... resolves https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3732 - strongly type the keyfunder config - new chains added to an environment's supported chains list must be configured - opens up the path to strongly type more of the env config down the line missing 1 chain: <img width="336" alt="image" src="https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/10051819/698ef9db-c50a-4a49-bc11-d33a44f186bf"> missing multiple chains: <img width="350" alt="image" src="https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/10051819/2f9e4e6c-5c36-4239-9c00-5951eca91589">	5 months ago
Paul Balaji	d316772243	feat: deploy to BOB, Mantle, Taiko (#4051) ... resolves https://github.com/hyperlane-xyz/issues/issues/1289 - feat: deploy to BOB, Mantle, Taiko - drive-by: fix deploying to specific chain - drive-by: adding AVS operators for eth - drive-by: support non-evm remotes in mainnet3 core config --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Daniel Savu	f8b33d1270	chore: update deployed relayer image (#4088) ... ### 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	d35b54670d	feat(keyfunder): make IGP claim thresholds configurable via command line args (#4074) ... hit successor to https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3284 resolves https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4049 - igp claim thresholds are moved to command line args instead, like desired balances - making it easier to tweak IGP claim thresholds - default claim threshold is 20% of desired balance for that chain - roughly follows what I've seen with the other balance vs igp claim thresholds - adding thresholds for all chains we've configured a desired relayer balance for - drive-by fixing keyfunder logging to include the relevant metadata testing: - ran locally and successfully performed igp claims on [blast](https://blastscan.io/tx/0x314d83d16e0406f77731befc7e8387dc946af01f7dc2200a426ff9748ad76d27), [linea](https://lineascan.build/tx/0xa5f4731ebcff073dacc6c15326196002bafd9578059688fd2f29db1a2742cb14), [viction](https://www.vicscan.xyz/tx/0x39921d3018a7b019518aa7a55a45ff29cce379bb9aabf0910c14423bd88689d5) & more --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Trevor Porter	6f4ef05d41	feat: faster way of figuring out how many new scraper rows were inserted (#4073) ... ### Description ### Context Full context / thread: https://discord.com/channels/935678348330434570/1254871503825141923 Copied here: so this is kinda interesting basically the gas payment indexing in the scraper task is consistently prioritizing hook-based indexing work over block range indexing work this only manifests in the scraper and for arbitrum because: there are a lot of arbitrum origin messages on the scraper, each gas payment indexing tick takes a very long time because of some very suboptimal queries. store_payments can take like 10-15 seconds! You can see batches of logs Found log(s) in index range https://cloudlogging.app.goo.gl/Bo9Q7YwyziSqjsEu7 that correspond with the gas payment contract sync block height (green line) advancing https://abacusworks.grafana.net/goto/poW4KOQIg?orgId=1  but we're still indexing gas payments bc of hook indexing - there are tons of Found log(s) for tx id https://cloudlogging.app.goo.gl/QvDaBuf67SjjKviw6 In the scraper's store_payments we bizarrely end up performing 2 very expensive queries with the calls to payments_count - it gets the count of gas payments for the provided domain so it can figure out how many new gas payments were actually inserted https://github.com/hyperlane-xyz/hyperlane-monorepo/blob/main/rust/agents/scraper/src/db/payment.rs#L27-L64 These queries vary a bunch in how expensive they can be - sometimes each one is like 1-2 seconds, sometimes it gets up to 10 seconds each though https://cloudlogging.app.goo.gl/cDFNH3oxh6WWV3Go8  easiest fix is probably to figure out how to make store_payments less expensive - we probably don't need to be making these calls to payments_count to figure out which ones are new which ill do atm there's maybe a decent argument to having hook indexing and range indexing not contend with one another but we should be able to kick that can also an annoying thing is https://github.com/hyperlane-xyz/hyperlane-monorepo/blob/main/rust/hyperlane-base/src/contract_sync/mod.rs#L155 this log not showing up, probably some weird instrumentation setup or something makes debugging harder ### The fix We want to keep supporting the possibility that we've double-indexed a data type, and to only return the number of new rows inserted. We want to keep each indexing task as non-conflicting as possible - we know that only one scraper is running at a time, but that a task for each chain and data type is executing concurrently. It's possible for e.g. two gas payment indexing tasks to try to insert into the same table concurrently, but it'll be for different domains. Insert statement concurrency issues aren't an issue because the only chance for conflict is the auto-incrementing primary key id, but this is all handled properly by database internals. Insert results only give the latest ID resulting from the insertion. E.g. if no matter how many rows were inserted, it gives the latest ID from that batch, but no info about how many were in the batch. We could do something like get the latest id in the table for all domains (this is cheap) before, then do the insert, and then get the latest id again, but this is susceptible to race conditions if concurrent tasks get an insertion in during that time as well. Shoving all these into a transaction doesn't seem to solve the problem either unless there's a lock on the table. However, sea-orm doesn't support table level locks, just select locks. We could also use a CTE to perform as a way to perform the select & insertion atomically and return the value of the select - but again sea-orm doesn't seem to provide a nice way of doing this from what I could tell. Instead, my suggested fix is: 1. Get the latest id in the table relating to the specific domain (this is cheap, < 100ms) 2. Perform the insertion 3. Count how many new rows for the specific domain now exist whose id is > the id from (1). This is also cheap, < 100ms. If there is a very long time since the last insertion for the domain, this could take longer, but in practice this doesn't seem to be the case. If this couple order of magnitude improvement still poses issues in the future, we can consider other alternatives, probably involving locking or fancier CTE queries. Some example queries and how long they take: Before (2x of these would occur!): <img width="477" alt="Screen Shot 2024-06-28 at 12 36 41 PM" src="https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/20362969/5cc8ac35-74fb-4847-9c6f-448deb253a0c"> Now: 1. Max id for a given domain <img width="494" alt="Screen Shot 2024-06-28 at 12 37 00 PM" src="https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/20362969/56dbb3ff-b540-458c-809c-56ebfbfd3b0f"> 2. Subsequent count but with an ID filter - note I actually changed this query to look for IDs > 3600000, which includes 55300 rows and it's still just 102ms! <img width="632" alt="Screen Shot 2024-06-28 at 12 37 49 PM" src="https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/20362969/11593180-682f-4867-9867-97fd93512802"> ### Drive-by changes - Updated the neutron image along with a deploy there ### Related issues ### Backward compatibility ### Testing Ran some sorta ad-hoc unit tests to test my new query by running against the prod db with a tokio::task. Tested for a new domain and an existing one	5 months ago
github-actions[bot]	526984cc3c	Version Packages (#4034) ... 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@4.0.0 ### Major Changes - df6a18053: Release CLI v4.0.0. ### Minor Changes - 44cc9bf6b: Add CLI command to support AVS validator status check - b05ae38ac: Gracefully handle RPC failures during warp send & fix deriving hook error that prevents warp and core test messages on the cli. - 9304fe241: Use metadata builders in message relaying - 6398aab72: Upgrade registry to 2.1.1 - 5c8ba0b85: Rename hyperlane config create chain -> hyperlane registry init. Rename all `configure` to `init` - cd419c98a: Add a validator preFlightCheck command verifying that the validator has been announced for a given chain - 35f869950: Add command to support creating agent configs - bf7ad09da: feat(cli): add `warp --symbol` flag - b0828b3d0: Reintroduce `ism read` and `hook read` commands - 129bd871d: Add chain displayName prompt with default - 4040db723: Fix createDefaultWarpIsmConfig to default to trusted relayer and fallback routing without prompts - 6db9fa9ad: Implement hyperlane warp deploy - bd3ca9195: Updates ci-test.sh to ci-advanced-test.sh. - b7003cf35: Add stdout.rows to pagesize calculation with DEFAULT_PAGE_SIZE ### Patch Changes - 3283eefd6: Removes default pattern for chain name when creating a new chain. - 4dd2651ee: Add xerc20 limit lookups to warp read - 6b63c5d82: Adds deployment support for IsmConfig within a WarpRouteConfig - Updated dependencies [b05ae38ac] - Updated dependencies [9304fe241] - Updated dependencies [bdcbe1d16] - Updated dependencies [6b63c5d82] - Updated dependencies [e38d31685] - Updated dependencies [e0f226806] - Updated dependencies [6db9fa9ad] - @hyperlane-xyz/sdk@4.0.0 - @hyperlane-xyz/utils@4.0.0 ## @hyperlane-xyz/core@4.0.0 ### Minor Changes - 44cc9bf6b: Add CLI command to support AVS validator status check ### Patch Changes - @hyperlane-xyz/utils@4.0.0 ## @hyperlane-xyz/helloworld@4.0.0 ### Minor Changes - 6398aab72: Upgrade registry to 2.1.1 - bf7ad09da: feat(cli): add `warp --symbol` flag ### Patch Changes - Updated dependencies [44cc9bf6b] - Updated dependencies [b05ae38ac] - Updated dependencies [9304fe241] - Updated dependencies [bdcbe1d16] - Updated dependencies [6b63c5d82] - Updated dependencies [e38d31685] - Updated dependencies [e0f226806] - Updated dependencies [6db9fa9ad] - @hyperlane-xyz/core@4.0.0 - @hyperlane-xyz/sdk@4.0.0 ## @hyperlane-xyz/sdk@4.0.0 ### Minor Changes - b05ae38ac: Gracefully handle RPC failures during warp send & fix deriving hook error that prevents warp and core test messages on the cli. - 9304fe241: Use metadata builders in message relaying - bdcbe1d16: Add EvmWarpModule with create() - e38d31685: Add logic to set smart provider log level to disable provider logs during Warp TokenType derive - e0f226806: - Enables creation of new Hooks through the `EvmHookModule`. - Introduces an `EvmModuleDeployer` to perform the barebones tasks of deploying contracts/proxies. - 6db9fa9ad: Implement hyperlane warp deploy ### Patch Changes - 6b63c5d82: Adds deployment support for IsmConfig within a WarpRouteConfig - Updated dependencies [44cc9bf6b] - @hyperlane-xyz/core@4.0.0 - @hyperlane-xyz/utils@4.0.0 ## @hyperlane-xyz/utils@4.0.0 ## @hyperlane-xyz/infra@4.0.0 ### Minor Changes - 6398aab72: Upgrade registry to 2.1.1 - bf7ad09da: feat(cli): add `warp --symbol` flag ### Patch Changes - Updated dependencies [b05ae38ac] - Updated dependencies [9304fe241] - Updated dependencies [6398aab72] - Updated dependencies [bdcbe1d16] - Updated dependencies [6b63c5d82] - Updated dependencies [bf7ad09da] - Updated dependencies [e38d31685] - Updated dependencies [e0f226806] - Updated dependencies [6db9fa9ad] - @hyperlane-xyz/sdk@4.0.0 - @hyperlane-xyz/helloworld@4.0.0 - @hyperlane-xyz/utils@4.0.0 ## @hyperlane-xyz/ccip-server@4.0.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	5 months ago
Paul Balaji	653bbcff52	fix(e2e): hardcode kathy chains for e2e in send-test-messages.ts (#4067) ... resolves https://github.com/hyperlane-xyz/issues/issues/1291 - remove test4 from kathy test - drive-by tidy-up of `test4` metadata - resets e2e test timeout back to original figure - reuse original e2e rust cache gonna keep the original commits on here as a trail of thought --------- Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Trevor Porter	e6b9d0e1bf	chore: bump arb costs (#4018) ... ### Description Big gas spike on arb rn, see https://discord.com/channels/935678348330434570/1253313812652888154 for context ### 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
J M Rossy	47cba13522	chore: Upgrade registry to 2.1.1 (#4035)	5 months ago
Trevor Porter	a109937f96	chore: some throughput tweaks (#4036) ... ### Description Context: https://discord.com/channels/935678348330434570/1254036693217054794 ### 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	7adbd27634	feat(infra): deploy to a set of specific chains (#4040) ... - feat(infra): deploy to a set of specific chains - allows users to specify more than 1 target chain to deploy to - provides suggestions of available chains to deploy (given local registry)  --------- Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	5 months ago
J M Rossy	6398aab727	chore: Upgrade registry to 2.1.1 (#4033) ... ### Description To pickup fix in https://github.com/hyperlane-xyz/hyperlane-registry/pull/71 ### Backward compatibility Yes	5 months ago
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:  deploying relayer:  --------- 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
Nam Chu Hoai	290c8cb6f6	feat: Script to generate Renzo Warp Route Configuration (#3983) ... ### 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
Yorke Rhodes	bf7ad09da3	feat(cli): add `warp --symbol` flag (#3992) ... ### Description - This allows users to interact read warp routes from the registry with symbol identifier rather than chain/address ### Drive-by Rename `wei` to `amount` ### Backward compatibility No, outputs chain map ### Testing - Manual (single) ```sh $ yarn hyperlane warp read --symbol EZETH $ yarn hyperlane warp send --symbol EZETH ``` (multiple) ```sh $ yarn hyperlane warp read --symbol USDC $ yarn hyperlane warp send --symbol USDC ``` --------- Co-authored-by: Noah Bayindirli 🥂 <noah@hyperlane.xyz>	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