hyperlane-monorepo

Commit Graph

Author	SHA1	Message	Date
Nam Chu Hoai	2e439423e7	Allow gasLimit overrides in the SDK/CLI for deploy txs (#3622 ) ### Description Small PR to actually allow overrides of gasLimit --------- Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>	7 months ago
Noah Bayindirli 🥂	450e8e0d55	migrate fork util to SDK (#3625 ) ### Description * Migrates fork util to SDK ### Drive-by changes * None ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3624 ### Backward compatibility * Yes ### Testing * Manual on core & warp	7 months ago
Yorke Rhodes	e10735a718	Fix solidity coverage (#3640 )	7 months ago
Lee	a91677a3da	Return entire deployedContracts object (#3617 ) ### Description Returns the deployedContracts object in token deployer ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Fixes #3585 ### 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 --> ### Testing None --------- Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>	8 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 -->	8 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
Daniel Savu	f4626eb4fe	Allow protocol-specific indexing (#3544 ) ### Description - Generalizes contract syncer hashmaps to store trait objects instead of concrete structs, since both `SequencedDataContractSync` and `WatermarkContractSync` implement `ContractSyncer` - The nice thing this enables is being able to instantiate a different type of syncer for the same contract, for different chain protocols (e.g. for IGP, we can use a sequenced syncer on sealevel and cosmwasm, and a watermark syncer on EVM). - The problem is that `ContractSyncer` is implemented on different trait bounds on `SequencedDataContractSync` and `WatermarkContractSync`. Most notably, the `SequencedDataContractSync` impl bounds the indexed type by the `Sequenced` trait. This means that if a type is to be indexed by more than one syncer strategy, it needs to implement the union of bounds of those strategies - Blocker: In the IGP, this means that `InterchainGasPayment` needs to implement `Sequenced` and we have no obvious way of getting that just from the type. Even if the sequence is derived from the type, it has to be a sensible value, since indexing reliability depends on it. - Similar to the point above, we now have `contract_syncs`, a single function that instantiates contract syncs for all chains. Since `contract_syncs` must be able to build a `ContractSyncer` trait obj for all syncer types, it bounds both `T` (the indexed type) and `D` (the log store type) with a union of bounds, so it may be too strict for some types in the future. - The scraper now uses forward-backward indexing instead of just forward indexing, because that simplified the refactor - there's now a convenience trait called `TryFromWithMetrics` that allows adding this bound: `SequenceIndexer<T>: TryFromWithMetrics<ChainConf>,`. This isn't really extendable if we use non-sequence indexers, but it's fine for now since this is used everywhere - replaces the macro-based contract syncer builder with generic fns Still todo: - add new `IndexingDecorator<T>` struct that can wrap `InterchainGasPayment`, so we can use sequence-aware indexing for the IGP - remove sequence logic from the watermark cursor ### 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 -->	8 months ago
Noah Bayindirli 🥂	aea79c686e	feat: add dry-run support for warp deploy + gas stats (#3586 ) ### Description * New feature to allow users to dry-run the warp deploy script against a forked (base/origin) network of their choice * To run: `yarn build && yarn hyperlane deploy warp --dry-run` \|\| `yarn build && yarn hyperlane deploy warp -d` * Externally enables: `hyperlane deploy warp --dry-run` \|\| `hyperlane deploy warp -d` * Also adds gas usage util for both warp & core deployments in all contexts, e.g. * When running a vanilla core deploy, for example, between alfajores and fuji, you will now see: ``` ⛽️ Gas Usage Statistics - Gas required for core deploy on alfajores: 0.0058686745 CELO - Gas required for core deploy on fuji: 0.0239308515 AVAX ``` ### Drive-by changes * None ### Related issues * Fixes https://github.com/hyperlane-xyz/issues/issues/819 ### Backward compatibility * Yes ### Testing * Note: `hl` == `yarn build && yarn hyperlane`. The below tests are only a sample and are not inclusive. #### Manual Testing * With `anvil` NOT running in separate instance: * `hl deploy warp -d` * Throws: ``` Error: No active anvil node detected. Please run `anvil` in a separate instance. ``` * With `anvil` running in separate instance: * `hl deploy warp -d -k c0052e22df5d1f4ae7c51e254Xx00Xx0eb833453eaed6301xXxxx8a30d92d10a` (any private key) * Throws `Error: Invalid address length. Please ensure you are passing an address and not a private key.` * `hl deploy warp -d -k 0x16F4898F47c085C41d7Cc6b1dc0xX0xXX017dcBb` (any public address) * Output: ``` 🔎 Verifying anvil node is running... ✅ Successfully verified anvil node is running Using warp route deployment config at ./configs/warp-route-deployment.yaml No chain config file provided ? Do you want to use some core deployment address artifacts? This is required for PI chains (non-core chains). no Forking alfajores for dry-run... ✅ Successfully forked alfajores for dry-run Impersonating account (0x16F4898F47c085C41d7Cc6b1dc72B91EA617dcBb)... ✅ Successfully impersonated account (0x16F4898F47c085C41d7Cc6b1dc72B91EA617dcBb) ... ✅ Hyp token deployments complete Writing deployment artifacts Deployment is complete! Contract address artifacts are in artifacts/dry-run_warp-route-deployment-2024-04-16-12-27-02.json Warp config is in artifacts/dry-run_warp-config-2024-04-16-12-27-02.json ⛽️ Gas Usage Statistics - Gas required for warp dry-run on alfajores: 0.013310162514578124 CELO Resetting forked network... ✅ Successfully reset forked network ✅ Warp dry-run completed successfully ``` #### CI Testing * Successful CI-backed integration/regression testing via `ci-test.sh`	8 months ago
J M Rossy	2b3f75836a	Add objLength and isObjEmpty util fns (#3605 ) ### Description Add `objLength` and `isObjEmpty` utils ### Related issues Fixes https://github.com/hyperlane-xyz/issues/issues/1199 ### Backward compatibility Yes	8 months ago
Yorke Rhodes	9a32971050	Remove accidental .only and update lint rules (#3614 ) ### Description Removal accidental .only ### Drive-by Update lint rules	8 months ago
Yorke Rhodes	917266dce1	Implement NULL metadata relaying in the SDK/CLI (#3604 ) ### Description - Add NULL self relay to core app - Add self relay to send message command ### Drive-by changes - Migrate to assert util in ISM Factory - Default to `HYP_KEY` in shared key option ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3608 - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3609 - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3452 ### Backward compatibility Yes ### Testing Manual https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/3020995/e44683c3-bca4-41d5-a4c7-45718f05edf4 https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/3020995/50565be1-d266-4d2d-ae27-5fbb5539b93f	8 months ago
Yorke Rhodes	c7007b0561	Implement trusted relayer ISM (#3363 ) ### Description - Adds an ISM that verifies whether the configured trusted relayer is the relayer of the message ### Related issues - Touches https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3371 ### Testing Unit Tests	8 months ago
Paul Balaji	2c3faf778c	feat: derive `IsmConfig` given an ism address (#3580 )	8 months ago
Trevor Porter	d3aa3f5cc9	Set prio fee override for moonbeam (#3587 ) ### 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 -->	8 months ago
Trevor Porter	64c8c8ad6d	Update key funder deployments w/ RpcConsensusType.Fallback, fix with ESM (#3583 ) ### Description Making testnet4 and mainnet3 key funder use fallback for consistency & robustness ### Drive-by changes Updated the deployed key funder images	8 months ago
Trevor Porter	26a26f4073	Agent transaction overrides, ensure agent configs are updated in CI (#3563 ) ### Description - Adds some basic transaction overrides for Ethereum chains to be used by the agents. This follows the existing config schema in chain metadata that we have been using on the TS side for a while. The overrides are as follows: - `transactionOverrides.gasPrice` - if specified, non EIP-1559 txs are used, and they use this gasPrice - `transactionOverrides.gasLimit` - if specified, this takes precedence over any gas estimation that's done and is the gas limit that's used for txs. (This is pretty niche and I don't imagine we'll ever wanna use this internally, but happens to cover the use case described [here](https://discord.com/channels/935678348330434570/984123861144600587/1224617234580766741), which is nice to cover) - `transactionOverrides.maxFeePerGas` - if specified and if the chain supports EIP 1559 txs, is used for the `maxFeePerGas` - `transactionOverrides.maxPriorityFeePerGas` - if specified and if the chain supports EIP 1559 txs, is used for the `maxPriorityFeePerGas` - Updates some of the transaction overrides in mainnet3 / testnet4 to be more reasonable now that we'll be using them to submit transactions pretty frequently - Note that atm the transaction overrides are most easily applied to the agents via the config JSONs, and not via our K8s configuration. The upshot of this is if we wanna change a transaction override right now, the easiest way to do it will be to run `update-agent-config.ts` and then build a new image. Created https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3565 to track making this experience better - Part of this change means that it's more important to keep the `transactionOverrides` specified in the SDK / infra up to date with the agent config. So I ended up doing https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3325 along the way, which also required doing https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3311. - To fix the issue with arbitrum blocks, we now require the index.from to be specified in the chain metadata if the chain's technical stack is arbitrum nitro - A new script, `update-agent-config.ts` is added, and it's ran for mainnet3 and testnet4 in CI to make sure there's no diff (similar idea to what we do with prettier) - Along the way I renamed mainnet3_config.json and testnet4_config.json to mainnet_config.json and testnet_config.json. This has been a source of confusion with ppl in the past - in v2 we named them without any numeric suffixes, so we now just do that again ### Drive-by changes - There's a drive-by to poll more frequently for pending transactions (2 seconds). The default is 7 seconds in Ethers, and for many chains that have really quick block times, this may be a way for us to speed up us learning that a transaction is included - Don't enforce gas on the inevm routes, looks like there's some weirdness there that was reported by Nam ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3562 - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3325 - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3311 ### 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
Paul Balaji	e3bf744f4b	feat: derive `HookConfig` given a hook address (#3543 )	8 months ago
Noah Bayindirli 🥂	17e48945a1	feat: add dry-run support for core deploy (#3558 ) Original PR: https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3305 ### Description * New feature to allow users to dry-run the core deploy script against a forked network of their choice * To run: `yarn build && yarn hyperlane deploy core --dry-run` \|\| `yarn build && yarn hyperlane deploy core -d` * Externally enables: `hyperlane deploy core --dry-run` \|\| `hyperlane deploy core -d` ### Drive-by changes * For all touched paths: * Code cleanliness + reuse * Method docs * Minor changes for increased symmetry ### Related issues * Fixes https://github.com/hyperlane-xyz/issues/issues/819 ### Backward compatibility * Yes ### Testing * Note: `hl` == `yarn build && yarn hyperlane`. The below tests are only a sample and are not inclusive. #### Manual Testing * With `anvil` NOT running in separate instance: * `hl deploy core -d` * Throws: ``` Error: No active anvil node detected. Please run `anvil` in a separate instance. ``` * With `anvil` running in separate instance: * `hl deploy core -d --targets alfajores -k c0052e22df5d1f4ae7c51e254Xx00Xx0eb833453eaed6301xXxxx8a30d92d10a` (any private key) * Throws `Error: Invalid address length. Please ensure you are passing an address and not a private key.` * `hl deploy core -d --targets bsctestnet -k 0x16F4898F47c085C41d7Cc6b1dc0xX0xXX017dcBb` (any public address; BSC public RPC endpoint does not support forking) * Output: `⛔️ [dry-run] The current RPC may not support forking. Please consider using a different RPC provider.` * `hl deploy core -d --targets alfajores -k 0x16F4898F47c085C41d7Cc6b1dc0xX0xXX017dcBb` (any public address) * Output: ``` Verifying anvil node is running... Successfully verified anvil node is running ✅ No chain config file provided Forking alfajores for dry-run... Successfully forked alfajores for dry-run ✅ Impersonating account (0x16F4898F47c085C41d7Cc6b1dc72B91EA617dcBb)... Successfully impersonated account (0x16F4898F47c085C41d7Cc6b1dc72B91EA617dcBb) ✅ ... Core contracts deployed Writing agent configs Agent configs written Deployment is complete! Contract address artifacts are in artifacts/dry-run_core-deployment-2024-02-23-15-51-45.json Agent configs are in artifacts/dry-run_agent-config-2024-02-23-15-51-45.json Resetting forked network... Successfully reset forked network ✅ ``` #### CI Testing * Successful CI-backed integration/regression testing via `ci-test.sh` (includes script refactor)	8 months ago
Lee	0090f19e78	Support self-relay with IGP enforced on warp routes (#3566 ) ### Description Adds transferRemote overload ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Fixes #3525 ### Backward compatibility Yes ### Testing Unit Tests	8 months ago
J M Rossy	b63714ede8	Convert packages from CJS to ESM (#3531 ) ### Description - Reconfigure tsconfig and package.json for the utils, core, sdk, and helloworld packages - Update imports to use ESM syntax - Add patch for typechain to address [issue 898](https://github.com/dethcrypto/TypeChain/pull/898) ### Drive-by changes Improve package Readme content ### Related issues Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/1354 ### Backward compatibility No: package consumers using CJS will need to modify their imports or update to ESM. See [this popular gist](https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c#pure-esm-package) for details. ### Testing - [x] CI test coverage which invokes a lot of code via the CLI e2e - [x] Manually test in Warp UI by copying packages - [x] Publish beta packages and test in a few popular bundlers	8 months ago
Daniel Savu	040641bf42	chore: rust ci tests with full backtraces enabled (#3564 ) ### Description Currently there's no way to know exactly where a panic occurred in rust e2e. This adds full backtraces to show where the task `.join` that caused the panic was. For example, this line isn't visible in the regular backtrace and it shows that the panic happened when spawning the anvil task (if you check out commit `0cc48e164379d08a8f4c3703eaab79bb86e271d6`): ``` at [...]/hyperlane-monorepo/rust/utils/run-locally/src/main.rs:321:22 ``` ### 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 -->	8 months ago
Paul Balaji	0cc48e1643	fix: typo in RateLimited.sol (#3561 ) make codespell happy again	8 months ago
Trevor Porter	526d27db04	Ancient8 deploy (#3472 ) ### Description - Deploys ancient8 core - Deploys a USDC warp route from Ethereum to ancient8 - Some changes to the key generation step - specifically: - `scripts/create-keys.ts` now expects `--newChainValidators chainname=1` instead of the flag `--newChains` - fixed the logic around adding new validators, which previously was broken - Adds a hook module to deploy.ts - this is meant to be used in a similar fashion to the warp module, where configs are built ad-hoc - changes `aw-multisig.json` to be `aw-multisig-${context}.json`, as previously the entire aw-multisig.json would be overridden no matter what the current context was	8 months ago
Lee	24e1f86d25	Warp Route rate limiter hook & ISM (#3527 ) ### Description Adds rate limiting hook and ism to limit warp route transfers ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Fixes #2697 ### Backward compatibility Yes ### Testing Unit Tests --------- Signed-off-by: Paul Balaji <paul@hyperlane.xyz> Co-authored-by: Noah Bayindirli 🥂 <noah@primeprotocol.xyz> Co-authored-by: Kunal Arora <55632507+aroralanuk@users.noreply.github.com> Co-authored-by: Paul Balaji <paul@hyperlane.xyz> Co-authored-by: J M Rossy <jm.rossy@gmail.com> Co-authored-by: Trevor Porter <trkporter@ucdavis.edu> Co-authored-by: Daniel Savu <23065004+daniel-savu@users.noreply.github.com>	8 months ago
Kunal Arora	37d49ec581	feat: add HypERC20 checker (#3517 ) ### Description - Added HypERC20App (extends GasRouterApp) and HypERC20Checker (extends RouterChecker bc there's no GasRouterChecker - link to issue) - remoteChains fetches the remote chains from the local router address is it given. This means, the abstract routerAddress in multiGeneric had to be made and this call had to awaited in a few places where it's used. Why? previously we assumed that the routers will be fully-connected and will match 1:1 with the config. This is too strong of an assumption for ICAs given we inherit the config through `getRouterConfig` and the ICA accounts will only need to exist on chains which don't have safes. Plus, in some cases, the chains implied by the app factories vs checker config don't match and this leads to further issues down the line while checking for mailbox client properties or in the govern. Checking the onchain enrollments is the most safe and resilient approach we can take especially given that having a checker for every RouterApp isn't feasible. ### Drive-by changes - adding native keys to warp artifacts for the appHelper to work in App.fromAddressMap. Note: if there's something using the router key, this isn't breaking unless you expect only one key. ### Related issues - fixes https://github.com/hyperlane-xyz/issues/issues/1191 ### Backward compatibility Yes ### Testing Manual --------- Signed-off-by: Paul Balaji <paul@hyperlane.xyz> Co-authored-by: Paul Balaji <paul@hyperlane.xyz> Co-authored-by: J M Rossy <jm.rossy@gmail.com> Co-authored-by: Trevor Porter <trkporter@ucdavis.edu> Co-authored-by: Daniel Savu <23065004+daniel-savu@users.noreply.github.com>	8 months ago
Kunal Arora	b110a73f80	fix:deploy-core ci writing unnecessary cache fix (#3542 ) ### Description - For https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3483, I was passing in ica artifacts through the cachedAddressesMap function which in turn writes these addresses to the deploy addresses.json file and this causes chain not found error in the subsequent module deployments. Fix - Read from options.icaApp for the router address (extra step added to the deployer) ### Drive-by changes None ### Related issues - https://discord.com/channels/935678348330434570/1225043256782622730 ### Backward compatibility Yes ### Testing local manual	8 months ago
Kunal Arora	aab63d466e	fix: contract verification for ICAs (#3532 ) ### Description - verified ICA router and ISM contracts for mainnet and testnet chains excluding avalanche and alfajores. ### Drive-by changes - update contractName for ICA ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3526 ### Backward compatibility Yes ### Testing None	8 months ago
github-actions[bot]	b88b56a589	Version Packages (#3495 ) 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.10.0 ### Minor Changes - 96485144a: SDK support for ICA deployment and operation. - 38358ecec: Deprecate Polygon Mumbai testnet (soon to be replaced by Polygon Amoy testnet) ### Patch Changes - Updated dependencies [`96485144a`] - Updated dependencies [`4e7a43be6`] - @hyperlane-xyz/utils@3.10.0 ## @hyperlane-xyz/cli@3.10.0 ### Minor Changes - 3ec81081c: Breaking: Update the `hyperlane chains list` command to accept an `env` (either 'mainnet' or 'testnet') to list chains for. Update `hyperlane chains list` command to pull the set of core chains from the contract addresses constant in the SDK. - 96485144a: SDK support for ICA deployment and operation. - 4e7a43be6: Replace Debug logger with Pino ### Patch Changes - 5373d54ca: Add --log and --verbosity settings to CLI - Updated dependencies [`96485144a`] - Updated dependencies [`38358ecec`] - Updated dependencies [`ed0d4188c`] - Updated dependencies [`4e7a43be6`] - @hyperlane-xyz/utils@3.10.0 - @hyperlane-xyz/sdk@3.10.0 ## @hyperlane-xyz/helloworld@3.10.0 ### Minor Changes - 96485144a: SDK support for ICA deployment and operation. - 4e7a43be6: Replace Debug logger with Pino ### Patch Changes - Updated dependencies [`96485144a`] - Updated dependencies [`38358ecec`] - Updated dependencies [`ed0d4188c`] - Updated dependencies [`4e7a43be6`] - @hyperlane-xyz/sdk@3.10.0 - @hyperlane-xyz/core@3.10.0 ## @hyperlane-xyz/sdk@3.10.0 ### Minor Changes - 96485144a: SDK support for ICA deployment and operation. - 38358ecec: Deprecate Polygon Mumbai testnet (soon to be replaced by Polygon Amoy testnet) - ed0d4188c: Fixed an issue where warp route verification would fail at deploy time due to a mismatch between the SDK's intermediary contract representation and actual contract name. Enabled the ContractVerifier to pick up explorer API keys from the configured chain metadata. This allows users to provide their own explorer API keys in custom `chains.yaml` files. - 4e7a43be6: Replace Debug logger with Pino ### Patch Changes - Updated dependencies [`96485144a`] - Updated dependencies [`38358ecec`] - Updated dependencies [`4e7a43be6`] - @hyperlane-xyz/utils@3.10.0 - @hyperlane-xyz/core@3.10.0 ## @hyperlane-xyz/utils@3.10.0 ### Minor Changes - 96485144a: SDK support for ICA deployment and operation. - 4e7a43be6: Replace Debug logger with Pino ## @hyperlane-xyz/ccip-server@3.10.0 ### Minor Changes - 96485144a: SDK support for ICA deployment and operation. ## @hyperlane-xyz/infra@3.10.0 ### Minor Changes - 96485144a: SDK support for ICA deployment and operation. - 38358ecec: Deprecate Polygon Mumbai testnet (soon to be replaced by Polygon Amoy testnet) - 4e7a43be6: Replace Debug logger with Pino ### Patch Changes - Updated dependencies [`96485144a`] - Updated dependencies [`38358ecec`] - Updated dependencies [`ed0d4188c`] - Updated dependencies [`4e7a43be6`] - @hyperlane-xyz/helloworld@3.10.0 - @hyperlane-xyz/utils@3.10.0 - @hyperlane-xyz/sdk@3.10.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	8 months ago
Kunal Arora	d792309b8d	feat: govern using ICAs (#3381 ) ### Description - Add inferICAEncodedSubmissionType for submitting transactions through ICA routers ### Drive-by changes - SafeUrl doesn't throw for chains we don't have safe service for. (bc while checking for native SubmissionType.SAFE we'll still check) ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3199 ### Backward compatibility Yes ### Testing Unit tests --------- Signed-off-by: Paul Balaji <paul@hyperlane.xyz> Co-authored-by: Paul Balaji <paul@hyperlane.xyz> Co-authored-by: J M Rossy <jm.rossy@gmail.com> Co-authored-by: Trevor Porter <trkporter@ucdavis.edu> Co-authored-by: Daniel Savu <23065004+daniel-savu@users.noreply.github.com>	8 months ago
Noah Bayindirli 🥂	38358ececd	feat: deprecate Mumbai testnet (#3521 ) ### Description - Removes all reference to Mumbai testnet, since it is soon being [deprecated](https://polygon.technology/blog/polygon-pos-is-cooking-the-napoli-upgrade-means-better-ux-the-mumbai-testnet-takes-a-bow) by the Polygon team - Monorepo docker tag: https://console.cloud.google.com/gcr/images/abacus-labs-dev/global/hyperlane-monorepo@sha256:d4b44359cae9c4e3bdeb6f965c59d056f7fce72c42069adc0dea038ac600785a/details?authuser=5&project=abacus-labs-dev&tab=info - Agent docker tag: https://console.cloud.google.com/gcr/images/abacus-labs-dev/global/hyperlane-agent@sha256:a578d96f7f06721d0b6cd8095d6a1fa5d22f01b59eba3320ee3b1fe34ca3c5df/details?authuser=5&project=abacus-labs-dev&tab=info ### Drive-by changes - Adds missing Testnet domains, Fuji & BSC Testnet - Fix for failing `test-rs` CI check with ``` error[E0004]: non-exhaustive patterns: `chain::KnownHyperlaneDomain::Fuji` and `chain::KnownHyperlaneDomain::BinanceSmartChainTestnet` not covered --> hyperlane-core/src/utils.rs:226:15 \| 226 \| match $v { \| ^^ patterns `chain::KnownHyperlaneDomain::Fuji` and `chain::KnownHyperlaneDomain::BinanceSmartChainTestnet` not covered ``` ### Related issues - Dependency on #3523 - Fixes #1181 ### Backward compatibility - [x] Backwards compatible - [x] Requires docker image tags to be added post-build - [x] Requires agent artifact cleanup in cloud account: https://www.notion.so/hyperlanexyz/Runbook-83c755f2652943289cf98cd1309487a8?pvs=4#77730653a12f409dacfbd427cab545d3 ### Testing * Build success * `yarn hyperlane chains list -e testnet` does not return `mumbai` * fork.sh script success locally	8 months ago
Daniel Savu	9b11f327c5	Range retries in watermark cursor (#3500 ) ### Description Changes the logic in the watermark cursor, to update the range in the `update` method rather than in `get_next_range`. This means that RPC errors won't result in ranges being skipped, so IGP indexing should be more reliable. ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - First in a sequence of many, for https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3264 ### 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
Kunal Arora	96485144a4	feat: ICA Router deployment on all core mainnet and testnet chains (#3493 ) ### Description - deployed InterchainAccountIsm and InterchainAccountRouter on all chains ### Drive-by changes - strongly ordered artifacts ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3475 ### Backward compatibility Yes ### Testing None --------- Signed-off-by: Paul Balaji <paul@hyperlane.xyz> Co-authored-by: Paul Balaji <paul@hyperlane.xyz> Co-authored-by: J M Rossy <jm.rossy@gmail.com> Co-authored-by: Trevor Porter <trkporter@ucdavis.edu> Co-authored-by: Daniel Savu <23065004+daniel-savu@users.noreply.github.com>	8 months ago
Kunal Arora	769f57d283	feat:ICA support in SDK (#3483 ) ### Description - Adding 'deployAccount` and `getCallRemote` helpers in InterchainAccount.ts for ease of use for the governor - Adding resolveAccountOwner/resolveInterchainAccountAsOwner wherever it's ambiguous if the owner is address (status quo) or AccountConfig (from this PR) - Added icaApp to HyperlaneDeployer for easier access to ICA ownership for any deployer - resolveAccountOwner vs resolveInterchainAccountAsOwner: the former is usable outside the deployers like the checker, etc whereas the latter is where we're already using the deployer and have the required localRouter already cached - includes the formatting change for the account verification file - owner needs casting in infra/config because of the type Address \| AccountConfig type (cannot use resolveAccountOwner here which requires multiprovider) - Add quoteGasPayment with gas limit override to the ICA router contract ### Drive-by changes - HyperlaneDeployer.cacheAddressesMap appends addresses two keys deep instead of overridding the whole cache - callData in utils now supports value to be compatible with CallData[] in the ICA Router contract and generally for V3 which allows msg.value on dispatch - `appFromAddressesMapHelper` doesn't intersect multiprovider with contractMap chains (this causes issues if the contracts map doesn't include chains we may want to read something like domainId from like ismfactory or ICADeployer) - HyperlaneHookDeployer is now using the owner as owner vs it was earlier using the deployer earlier for unknown reason - ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3505 ### Backward compatibility No (call value) ### Testing Unit testing/e2e testing through governor --------- Signed-off-by: Paul Balaji <paul@hyperlane.xyz> Co-authored-by: Paul Balaji <paul@hyperlane.xyz> Co-authored-by: J M Rossy <jm.rossy@gmail.com> Co-authored-by: Trevor Porter <trkporter@ucdavis.edu> Co-authored-by: Daniel Savu <23065004+daniel-savu@users.noreply.github.com>	8 months ago
Daniel Savu	00fcaf74db	fix: warn on tx reverts; log cosmos tx results (#3497 ) ### 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 -->	8 months ago
Daniel Savu	57e4a8acd9	relayer image with half the timeout for eth txs (#3511 ) ### 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 -->	8 months ago
Trevor Porter	9b06f3bfe1	Different key funder job name (#3506 ) ### Description - My changes in #3491 / #3492 were kind of accurate - according to https://github.com/prometheus/pushgateway/issues/65 even using pushAdd will displace existing metrics. It's all very confusing! - I tested this with a script that pushed some test metrics to the push gateway - basically by having the key funder use a different job name than the mainnet2 one, the metrics each of them push won't conflict with one another ### 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 -->	8 months ago
Noah Bayindirli 🥂	2093fe48fd	add 'mumbai' to chainsToSkip (#3523 ) ### Description - Adds `mumbai` to `chainsToSkip` as a preliminary step for deprecating Polygon Mumbai testnet ### Related Issues - Unblocks #3521 - Fixes #1181	8 months ago
Noah Bayindirli 🥂	d00500f505	update codeowners for @nbayindirli (#3522 ) ### Description * Updated codeowners for @nbayindirli	8 months ago
Lee	db85f8aaf4	Upgradable warp routes (#3474 ) ### Description Makes the following Warp Routes upgradable through CLI deployment ``` - FastHypERC20Collateral - FastHypERC20 - HypERC20 - HypERC20Collateral - HypERC20CollateralVaultDeposit - HypNative - HypNativeScaled - HypERC721Collateral - HypERC721 - HypERC721URICollateral - HypERC721URIStorage ``` - Adds `initialize()` to each contract - It mostly contains `_MailboxClient_initialize`, and any additional proxy specific constructor logic - Refactors - Update `GasRouterDeployer` to inherit from `ProxiedRouterDeployer` - Update `ProxiedRouterDeployer.routerContractName` to `abstract ProxiedRouterDeployer.routerContractName(): RouterKey` . - This allows child classes to specify their own contract name instead of being locked-in to a single name upon construction. Similar concept to the existing `ProxiedRouterDeployer.constructorArgs()` and `ProxiedRouterDeployer.initializeArgs()` - Update `router()` - Add function into `InterchainQueryDeployer` - Add function into `InterchainAccountDeployer` - Update to abstract function in `ProxiedRouterDeployer` - ### Drive-by changes ### Related issues Fixes #999 ### Backward compatibility - Should be backward compatible ### Testing - Updates contract unit tests - Manual testing through CLI and verified contracts	8 months ago
J M Rossy	5373d54ca5	Add global log options to CLI (#3519 ) ### Description - Add global log options to CLI - Improve consistency with agent log options - Other minor log-related cleanup ### Related issues Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3499 ### Backward compatibility Yes because the new log options haven't yet published	8 months ago
Kunal Arora	41cc7f5c4b	fix: config fallback as default on fuji (#3501 ) ### Description - default hook was misconfigured to a routing whereas it should have been a fallback routing hook ### Drive-by changes LOG_PRETTY=true in CI ### Related issues - https://discord.com/channels/935678348330434570/935678739663192184/1222618018098581575 ### Backward compatibility Yes ### Testing Manual through cast	8 months ago
Paul Balaji	ed0d4188c1	fix: add changeset for warp verify fix (#3513 )	8 months ago
Paul Balaji	3ec81081c6	feat: CLI chain list derived from SDK contract addresses artifact (#3514 )	8 months ago
Daniel Savu	ff6b06079e	Half the relayer timeout on v3 (#3508 ) ### Description V3 counterpart of https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3431 Co-authored-by: nambrot <nambrot@googlemail.com>	8 months ago
Paul Balaji	a9881dc128	fix: warp route deployment verification (#3494 )	8 months ago
J M Rossy	4e7a43be6a	Logging overhaul (#3481 ) ### Description - Replace use of debug lib with Pino - Replace `loggerName` params with Logger types - Update SDK Readme ### Related issues Fixes https://github.com/hyperlane-xyz/issues/issues/918 ### Backward compatibility No, breaks anyone passing in custom logger to SDK classes, which is likely no one ### Testing - Tested in CLI - Tested in Warp UI	8 months ago
Kunal Arora	4f0ea4361e	feat: add quoteGasPayment to ICA router (#3460 ) ### Description - for easier offchain use, we can directly call the ICA router to fetch the quote needed for the dispatch. ### Drive-by changes None ### Related issues None ### Backward compatibility Yes ### Testing Unit	8 months ago
github-actions[bot]	1af0babdec	Version Packages (#3489 ) # Releases ## @hyperlane-xyz/cli@3.9.0 ### Minor Changes - 11f257ebc: Add Yield Routes to CLI ### Patch Changes - Updated dependencies [`11f257ebc`] - @hyperlane-xyz/sdk@3.9.0 - @hyperlane-xyz/utils@3.9.0 ## @hyperlane-xyz/sdk@3.9.0 ### Minor Changes - 11f257ebc: Add Yield Routes to CLI ### Patch Changes - @hyperlane-xyz/core@3.9.0 - @hyperlane-xyz/utils@3.9.0 ## @hyperlane-xyz/core@3.9.0 ### Patch Changes - @hyperlane-xyz/utils@3.9.0 ## @hyperlane-xyz/helloworld@3.9.0 ### Patch Changes - Updated dependencies [`11f257ebc`] - @hyperlane-xyz/sdk@3.9.0 - @hyperlane-xyz/core@3.9.0 ## @hyperlane-xyz/utils@3.9.0 ## @hyperlane-xyz/infra@3.9.0 ### Patch Changes - Updated dependencies [`11f257ebc`] - @hyperlane-xyz/sdk@3.9.0 - @hyperlane-xyz/helloworld@3.9.0 - @hyperlane-xyz/utils@3.9.0 ## @hyperlane-xyz/ccip-server@3.9.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	8 months ago
Yorke Rhodes	ba6ab2ce37	Update static-analysis.yml (#3480 ) ### Description - Updates slither static analysis to run on main for use with github code scanning	8 months ago
Trevor Porter	3b520640d7	Don't overwrite pushgateway metrics, shift mainnet3 cron schedule (#3491 ) ### Description Copying from my Discord thread https://discord.com/channels/935678348330434570/1222226637026885652 > Instead of pushing new metrics to the pushgateway and allowing any existing metrics that exist there to stay there, we replace any existing metrics > We use `.push` instead of `.pushAdd` here `258bf85e43/typescript/infra/src/utils/metrics.ts (L29)` > And because we run two key funders on the mainnet cluster, the mainnet3 key funder metrics compete with the mainnet2 key funder metrics > We start them on the same cron job frequency I guess, but we have more keys on mainnet3 so it typically takes longer than the mainnet2 one, so the mainnet3 metrics tend to overwrite the mainnet2 ones > Wonder if we should start them at diff times for less nonce contention risk anyways > For posterity, I found this by port-forwarding to the push gateway ``` kubectl port-forward prometheus-pushgateway-587c8dc779-294wv 9091 -n monitoring ``` > Where I found only mainnet3 metrics at localhost:9091/metrics ``` # HELP hyperlane_wallet_balance Current balance of eth and other tokens in the `tokens` map for the wallet addresses in the `wallets` set # TYPE hyperlane_wallet_balance gauge hyperlane_wallet_balance{chain="arbitrum",hyperlane_context="hyperlane",hyperlane_deployment="mainnet3",instance="",job="key-funder",token_name="Native",token_symbol="Native",wallet_address="0xa7ECcdb9Be08178f896c26b7BbD8C3D4E844d9Ba",wallet_name="key-funder"} 9.10653822887378 ``` > even though the push gateway had been running for days So this PR: * Shifts the cron schedule for key funder by 30 mins to avoid nonce clobberring with the mainnet2 key funder * moves to by default not overwriting existing metrics I'll do a similar PR for v2 to stop overwriting existing metrics ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues Related: https://github.com/hyperlane-xyz/issues/issues/1141 ### 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 ...

2126 Commits (2e439423e743694226e877fe3c63d664684083d2) All Branches Search

2126 Commits (2e439423e743694226e877fe3c63d664684083d2)

All Branches