hyperlane-monorepo

Commit Graph

Author	SHA1	Message	Date
J M Rossy	6f464eaeda	Add injective and nautilus logos (#3241 )	10 months ago
Daniel Savu	3cbb06a07a	feat: fetch chain-specific metrics in standalone task (#3214 ) ### Description Spawning a tokio task to fetch chain-specific metrics in provider middleware was wasteful because we ended up with 15 tasks doing the same job. Now there is a single task that is spawned inside the relayer, which I added in the struct that used to only fetch relayer balance. Some questions: - I'm realising in the current state I'm probably removing these metrics from validators. Lmk if yes and I'll add back - the chain-specific metrics were moved out of `MiddlewareMetrics` because they're no longer part of middleware, but I wasn't sure where to place them. Maybe `CoreMetrics` is a better place than the current `custom_metrics.rs` file? `tokio-metrics` turned out not to be useful because we'd need to instrument every call site of `tokio::spawn` with it. We should still do it but as a separate task imo. ### Drive-by changes - This PR also makes it very easy to add the metrics tasks for new chains, by extending the `HyperlaneProvider` trait with a `get_chain_metrics` call which seems reasonably general to me to have implemented by all providers. (Bc we currently only track these for evm chains) - the description, naming and logic of the `gas_price` metric was also changed to support new chains ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3047 ### Backward compatibility Yes ### Testing Still need to manually test	10 months ago
Kunal Arora	ab17af5f7e	feat: configure GasOracle in HyperlaneIgpDeployer (#3218 ) ### Description HyperlaneIGPDeployer supports configuring storageGasOracle if provided. HyperlaneIgpDeployer takes in `IgpConfig & Partial<OracleConfig>` Note: storageGasOracle cannot be configured in CLI yet. Note: this is a more minimal version of https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3101 where more breaking changes were made. ### Drive-by changes None ### Related issues - fixes https://github.com/hyperlane-xyz/issues/issues/820 ### Backward compatibility Yes ### Testing Unit	10 months ago
Paul Balaji	58b4aaa559	feat: deploy new RC (#3190 )	10 months ago
Trevor Porter	473b43f001	Injective & inevm agents (#3155 ) ### Description - Deploys injective & inevm validators, adds them to the hyperlane context relayer, and starts scraping inevm ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz> Co-authored-by: nambrot <nambrot@googlemail.com> Co-authored-by: Daniel Savu <23065004+daniel-savu@users.noreply.github.com>	10 months ago
Kunal Arora	cf82687507	feat:remove create-key circular dependency (#3159 ) ### Description Diagnosis: circular dependency created by igp requiring multisig size and threshold for building coreConfig which is needed while creating new keys. This arises in the scenario where you add the chain to chainMetadata and not to defaultMultisigConfigs (say newChainConfigs) - separated agents and helloworld configs from core and segregated scripts for `core-utils.ts` and `agent-utils.ts` for avoiding loading of envConfig.coreConfig - add argv commands to prompt for new chains or updated chains and validator/threshold combo: `yarn ts-node scripts/create-keys -e testnet4 --context hyperlane --new-chains basesepolia=2/3` (here 2 is desired threshold and 3 is desired multisig set size) - if you provide a newChainConfigs chain and don't supply an argv, the create-keys script will revert - persist addresses in gcp (already present) and under sdk (this PR) with types preserved ### Drive-by changes - imports - might break other scripts like delete-keys, etc in infra (not tested) ### Related issues - fixes https://github.com/hyperlane-xyz/issues/issues/887 ### Backward compatibility Yes ### Testing Manual --------- Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>	10 months ago
Ivan Temchenko	65e2ea50f9	Google Cloud Storage CheckpointSyncer implementation (#3156 ) ### Description GSC builder and implementer classes; Documentation comments; Examples; Anonymous test on public bucket access; ### Drive-by changes `cargo doc` build fixes: * replaced square braces of non-existing items with `'` ; * raw URL surrounded by `<>`; ### Related issues Fixes #2242 Part 1 ### Backward compatibility Yes ### Testing Unit Tests	10 months ago
Yorke Rhodes	54aeb6420b	feat/CLI tool for monitoring warp route balances (#3231 ) ### Description Replay https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3204 on main Co-authored-by: -f <kunalarora1729@gmail.com>	10 months ago
Paul Balaji	fa058a0e57	fix: add fallback to kurtosis terminal link (#3227 )	10 months ago
Yorke Rhodes	0ff3e2b171	Deploy injective and inEVM (#3140 ) ### Description - Deploy core to injective and inEVM networks ### Drive-by changes - Update cw-hyperlane dependency ### Backward compatibility Yes ### Testing - Fork tests - e2e tests --------- 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> Co-authored-by: Nam Chu Hoai <nambrot@googlemail.com>	10 months ago
Yorke Rhodes	634873fe31	Rotate chain metadata RPC urls (#3229 ) ### Description - existing viction and sepolia RPC urls were failing on eth_getCode ### Testing - CI fork tests	10 months ago
Daniel Savu	f2a0e92c7f	Cosmos grpc fallbackprovider (#3139 ) ### Description Implements grpc fallback provider logic for cosmos - initially tried implementing the fallback provider deprioritization logic at middleware level like in the EVM. The difference between ethers and cosmrs is that in the latter, middleware can only live at the transport layer (`tower` crate level). - based on this github [issue](https://github.com/hyperium/tonic/issues/733), that actually doesn't look possible, because the http::Request type isn't `Clone` so it can't be submitted to multiple providers - ended up implementing the fallback provider at the application layer, by keeping an array of grpc channels - There is now a `call` method in `hyperlane_core::FallbackProvider` which I'm actually really happy with. This method handles the fallbackprovider-specific logic by taking in an async closure, running it on each provider, and iterating providers if the closure call fails. In `grpc.rs` you can see how this is slightly verbose but I think it's quite manageable. The only part that bugs me is having to duplicate `Pin::from(Box::from(future))`, but that's need afaict because the regular closure returns an anonymous type - adds `grpcUrls` and `customGrpcUrls` config items - tests the cosmos fallback provider e2e ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Fixes: https://github.com/hyperlane-xyz/issues/issues/998 ### 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 -->	10 months ago
Paul Balaji	8bfa8c13cc	fix: agent config artifact includes only chains user deployed to (#3223 )	10 months ago
Trevor Porter	d1621b49d0	Add Neutron back to mainnet3_config.json (#3220 ) ### Description Looks like https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3179/files#diff-edae1a4e631a67121d92119998e37740c0190bec5060e3c842cc86e4d3d26a4dL417 removed Neutron from mainnet3_config.json :( Seems like the Typescript tooling may have overridden it accidentally? Will need to figure out what to do there ### Drive-by changes ### 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 -->	10 months ago
github-actions[bot]	0865c948c3	Version Packages (#3217 ) 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.6.2 ### Patch Changes - @hyperlane-xyz/utils@3.6.2 ## @hyperlane-xyz/cli@3.6.2 ### Patch Changes - 99fe93a5b: Removed IGP from preset hook config - @hyperlane-xyz/sdk@3.6.2 - @hyperlane-xyz/utils@3.6.2 ## @hyperlane-xyz/helloworld@3.6.2 ### Patch Changes - @hyperlane-xyz/core@3.6.2 - @hyperlane-xyz/sdk@3.6.2 ## @hyperlane-xyz/sdk@3.6.2 ### Patch Changes - @hyperlane-xyz/core@3.6.2 - @hyperlane-xyz/utils@3.6.2 ## @hyperlane-xyz/utils@3.6.2 ## @hyperlane-xyz/infra@3.6.2 ### Patch Changes - @hyperlane-xyz/helloworld@3.6.2 - @hyperlane-xyz/sdk@3.6.2 - @hyperlane-xyz/utils@3.6.2 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	10 months ago
Kunal Arora	99fe93a5ba	feat:removing igp from preset hook config (#3215 ) ### Description - To simplify the PI deployment, I've removed the igp from preset hook config which PI deployers use if they don't provide a hook config via the CLI. - This means we don't need to deploy IGP or storage gas oracles and the PI deployer can spin up relayer with gas enforcement policy set to false. ### Drive-by changes None ### Related issues None ### Backward compatibility Yes ### Testing Manual	10 months ago
Paul Balaji	8907a7151c	feat: build head of PRs instead of merge commit (#3206 )	10 months ago
Paul Balaji	166e9d316a	feat: improve create-key logging (#3207 )	10 months ago
Huulu	3ea5dd7b66	chore(rust): proofreading (#3152 ) Came across few typos while browsing ./rust. One of them is an error message displayed to the user, rest are comments. Hope I could be of any help. Have a nice week-end Co-authored-by: Daniel Savu <23065004+daniel-savu@users.noreply.github.com>	10 months ago
Nam Chu Hoai	1adce84e33	Reduce v3 kathy frequency (#3104 ) ### Description Reduces frequency so that we only send roughly once every hour - [x] Reduce alert thresholds - [x] Deploy	10 months ago
Yorke Rhodes	8fe24830ee	Deploy viction core and warp routes (#3067 ) ### Description Deploys core and warp to viction ### Related issues - Fixes https://github.com/hyperlane-xyz/issues/issues/850 - Fixes https://github.com/hyperlane-xyz/issues/issues/859 ### Backward compatibility Yes ### Testing Fork tests --------- 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> Co-authored-by: Nam Chu Hoai <nambrot@googlemail.com>	10 months ago
Daniel Savu	9e6146518f	fix: potential rate-limiting bugfix (#3191 ) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2586 ### 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 -->	10 months ago
Kunal Arora	d0190ecec6	fix: add warning for advanced ism config usage (#3160 ) ### Description Add bold red warning for advanced ism for both configuring and deploying Note: we don't merge sdk artifacts for advanced ism core deployment ### Drive-by changes none ### Related issues none ### Backward compatibility Yes ### Testing Manual	10 months ago
Kunal Arora	ff771351b8	feat:update deployments to use `FallbackRoutingHook` (#3179 ) ### Description - mainnet3, testnet4 should be using fallback routing hooks because it's more "porous" for first-time deployers of hyperlane to have merkleTreeHook out of the box ### Drive-by changes - added overrides to configureHook in basedeployer and setHook in hookdeployer - added fetching local rpc first logic in infra/chains and then secrets rpc if needed. This would mean the forking and live setup will be closer as the rpc urls will be the same between the two. ### Related issues None ### Backward compatibility Yes ### Testing Fork	10 months ago
Trevor Porter	3bb4d87dda	Injective / inevm agent code & config changes (#3185 ) ### Description Taken from https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3155 but without any of the ancillary things like changes to the SDK or infra. Merging to get an image off `main` that works w/ injective. Branch plan is: - after this is merged, an image off main can be used to run an agent against injective/inevm - https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3140 will have all the SDK changes from the contract deployments - https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3155 will have the infra changes to start deploying injective / inevm validators / relayer ### 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 -->	10 months ago
Trevor Porter	1eaed03694	Blacklist (optimism)goerli griefer, deploy w/ new image on testnet4 (#3184 ) ### Description Blacklists a griefer that sent a bunch of messages before we had IGPs properly configured on testnet4 ### 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 -->	10 months ago
Daniel Savu	c9ef41c109	Fallback Provider Refactor (#3127 ) ### Description - Generalizes the fallback provider. Now any provider type can be used in it, as long as it implements `Into<Box<dyn BlockNumberGetter>> + Clone` (aka it can be wrapped into a struct that reads the current block #, and it can be cloned). - moves the fallback provider implementation to hyperlane-core - had serious issues with getting versions to successfully resolve - next time I run into issues, strongly inclined to create a new crate with dependencies for all chains, but which are only depended on by the agents codebase (rather than the contract as well). Chatted with @tkporter about this. - now fallbackprovider needs to be wrapped in a newtype struct for chain-specific trait implementations - If `Deref` is implemented for the newtype struct, all the function calls will still work (although using Deref for newtypes is [debatable](https://users.rust-lang.org/t/understanding-the-perils-of-deref/47958/18)) - the `request` function required by the `JsonRpcClient` still has some reusable logic but I left it there until it's clearer what can be reused by the cosmos fallback provider - the fallback provider unit tests still live in hyperlane-ethereum because of the logic in `require` ### Drive-by changes - needed to use `async-rwlock` instead of `tokio` for the `RwLock` structure used by the fallback provider for interior mutability. This is because the solana program requirements had rust pinned too far into the past for `tokio` to resolve to a version. ### Related issues - Fixes https://github.com/hyperlane-xyz/issues/issues/892 ### Backward compatibility Yes ### Testing Unit tests that were already there for the fallback provider	10 months ago
Nam Chu Hoai	648c0ac8da	Add Neutron validators (#3182 ) ### Description Adds the validator set to the source of truth in the SDK consts	10 months ago
Yorke Rhodes	778312d996	Improve ergonomics of fork tests (#2911 ) ### Description https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/2888 introduced breaking changes to non-`arbitrum` chains but fork tests would not cover This PR adds a `fork-all` script for running fork tests on all `protocol == ethereum` chains in an environment It also improves the interface of the `fork` script to accept a target chain ### Drive-by changes - Remove noisy `console.log`s - swap `polygon, ethereum, polygonzkevm` RPCs - Fixes `ownerOverrides: proxyAdmin` for chains without gnosis safes ### Backward compatibility Yes	10 months ago
Yorke Rhodes	fa465b7233	Remove dupe FastHypERC20 for verifiable contracts (#3091 ) ### Description Duplicate FastHypERC20 implementations got into main following the v3 merge that prevent flattening used in verification ### Related issues - Unblocks https://github.com/hyperlane-xyz/issues/issues/886 ### Backward compatibility Yes ### Testing Unit Tests	10 months ago
Kunal Arora	0d5a751982	fix:use custom hook for sending test messages in the CLI (#3178 ) ### Description - Saving the deployed top-level hook address if the deployer is not the owner of the mailbox - CLI command for sending messages uses the custom hook if present in the artifacts ### Drive-by changes None ### Related issues ### Backward compatibility Yes ### Testing Manual	10 months ago
Paul Balaji	0e8e169311	feat: aws validator terraform example (#3170 )	10 months ago
github-actions[bot]	72774b3b92	Version Packages (#3153 ) # Releases ## @hyperlane-xyz/core@3.6.1 ### Patch Changes - e4e4f93fc: Support pausable ISM in deployer and checker - Updated dependencies [`78e50e7da`] - @hyperlane-xyz/utils@3.6.1 ## @hyperlane-xyz/cli@3.6.1 ### Patch Changes - Updated dependencies [`e4e4f93fc`] - @hyperlane-xyz/utils@3.6.1 - @hyperlane-xyz/sdk@3.6.1 ## @hyperlane-xyz/helloworld@3.6.1 ### Patch Changes - Updated dependencies [`e4e4f93fc`] - @hyperlane-xyz/sdk@3.6.1 - @hyperlane-xyz/core@3.6.1 ## @hyperlane-xyz/sdk@3.6.1 ### Patch Changes - ae4476ad0: Bumped mantapacific reorgPeriod to 1, a reorg period in chain metadata is now required by infra. - f3b7ddb69: Add optional grpcUrl field to ChainMetadata - e4e4f93fc: Support pausable ISM in deployer and checker - Updated dependencies [`e4e4f93fc`] - @hyperlane-xyz/utils@3.6.1 - @hyperlane-xyz/core@3.6.1 ## @hyperlane-xyz/utils@3.6.1 ### Patch Changes - 3c298d064: Add isAddress function to check if string matches EVM, Cosmos, or Solana address formats - df24eec8b: Fix for address utils falsy fallbacks - 78e50e7da: addressToBytes32 changed to work for all protocol types ## @hyperlane-xyz/infra@3.6.1 ### Patch Changes - ae4476ad0: Bumped mantapacific reorgPeriod to 1, a reorg period in chain metadata is now required by infra. - e4e4f93fc: Support pausable ISM in deployer and checker - Updated dependencies [`e4e4f93fc`] - @hyperlane-xyz/utils@3.6.1 - @hyperlane-xyz/sdk@3.6.1 - @hyperlane-xyz/helloworld@3.6.1 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	10 months ago
J M Rossy	df24eec8be	Fix address util nullish fallback handling (#3181 ) ### Description Small fix for address utils ### Related issues https://github.com/hyperlane-xyz/issues/issues/899 ### Backward compatibility Yes ### Testing In warp UI	10 months ago
Trevor Porter	6845f9f4b8	Fix parsing sequences of H256s in a matchinglist via agent settings (#3180 ) ### Description Upon trying to use a blacklist with an array of H256s as the `recipientAddress`, was getting a panic: ``` running 1 test parse_value: Array [Object {"destinationdomain": Number(11155111), "origindomain": Number(1399811151), "recipientaddress": Array [String("0x6AD4DEBA8A147d000C09de6465267a9047d1c217"), String("0x6AD4DEBA8A147d000C09de6465267a9047d1c218")], "senderaddress": Array [String("0x6AD4DEBA8A147d000C09de6465267a9047d1c217"), String("0x6AD4DEBA8A147d000C09de6465267a9047d1c218")]}] "Expected matching list" thread 'settings::matching_list::test::supports_sequence_h256s' panicked at 'called `Result::unwrap()` on an `Err` value: ConfigParsingError([(ConfigPath([]), Expected matching list Caused by: invalid type: string "0x6AD4DEBA8A147d000C09de6465267a9047d1c217", expected a borrowed string Location: /Users/trevor/abacus-monorepo/rust/hyperlane-base/src/settings/parser/json_value_parser.rs:259:14)])', agents/relayer/src/settings/matching_list.rs:473:60 stack backtrace: 0: rust_begin_unwind at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/std/src/panicking.rs:593:5 1: core::panicking::panic_fmt at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/core/src/panicking.rs:67:14 2: core::result::unwrap_failed at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/core/src/result.rs:1651:5 3: core::result::Result<T,E>::unwrap at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/core/src/result.rs:1076:23 4: relayer::settings::matching_list::test::supports_sequence_h256s at ./src/settings/matching_list.rs:473:9 5: relayer::settings::matching_list::test::supports_sequence_h256s::{{closure}} at ./src/settings/matching_list.rs:459:34 6: core::ops::function::FnOnce::call_once at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/core/src/ops/function.rs:250:5 7: core::ops::function::FnOnce::call_once at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/core/src/ops/function.rs:250:5 note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace. test settings::matching_list::test::supports_sequence_h256s ... FAILED ``` Honestly not too sure about the implications of this being a String vs &str ### 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 -->	10 months ago
Trevor Porter	0cad4f7407	Support cosmos contract byte lengths other than 32 (#3147 ) ### Description fixes #3143 Initially went down a path that would use protocol-specific types for addresses as suggested by #3143. I had made a `HyperlaneConnectionConf` enum with protocol-specific variants whose values were `addresses: CoreContractAddresses<ProtocolSpecificAddressType>` and `connection: ProtocolSpecificConnectionConf`. This worked pretty well until I hit the ISM logic. Because hyperlane-core is where the Mailbox trait is defined, the return type of `recipient_ism` in the trait cannot involve protocol specific types. It can't be moved to hyperlane-base because hyperlane-base imports the chain crates, so we'd have a cyclic dependency. I experimented with moving away from H256 to something like a Vec<u8> or string, but this felt a bit weird. In the end we decided to keep H256s as the global representation for contract addresses for now, with the intent of eventually changing this, and to support the varying length situation in a cosmos config ### Drive-by changes - Added some cosmos specific agent configurations into the sdk - Moved to bech32_prefix in the agents for consistency with what the SDK's chain metadata already does - I guess no one's ran cargo test in a while so vectors/message.json got a new v3 message lol ### Related issues Fixes #3143 ### Backward compatibility Changes prefix to bech32_prefix in the agent config, and now requires `contractAddressBytes` ### Testing Tested merged with #3144 and all worked --------- Co-authored-by: Daniel Savu <23065004+daniel-savu@users.noreply.github.com>	10 months ago
Daniel Savu	528a19022b	Deploy eclipse testnet (#3172 ) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: Trevor Porter <trkporter@ucdavis.edu>	10 months ago
Trevor Porter	5b4af6bf1d	Injective-specific account info protobuf (#3144 ) ### Description Only change needed was to correctly handle the account info. Because we may want to handle injective testnet, added `is_injective` fn to HyperlaneDomain instead of just doing the match directly. Happy to import some of the longer fully qualified names instead ### 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 -->	10 months ago
J M Rossy	f3b7ddb699	Add optional gRpcUrls field to ChainMetadata schema (#3163 ) ### Description - Add optional gRpcUrls field to ChainMetadata schema - Enforce inclusion of restUrls and gRpcUrls for cosmos chains - Fix neutron rest url ### Related Issues Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3161 ### Backward compatibility Yes ### Testing Unit test	10 months ago
Trevor Porter	78e50e7da4	Validator observability infra (#3116 ) ### Description - Configures the relayers to start tracking the latest checkpoints of the manta TIA WR, arbitrum TIA WR, and helloworld sets (and, implicitly, the default ISM sets too) - deployed all agent roles & networks with the new image - created alerts and added to the nexus dashboard One thing that's a bit of a bummer is the metrics are only updated whenever we try to construct metadata for a message. Naturally the validators will poll & sign checkpoints slightly out of sync, so pretty frequently the relayer attempts to deliver a message where say 4/6 signatures are needed, and 2 of the validators happen to just have not polled & signed the checkpoint yet. The message is then successfully delivered, and the 2 remaining validators probably sign the checkpoint in a matter of seconds, but the metrics aren't updated to reflect this unless there's another message whose metadata is being constructed. This just means that the graph is a bit ugly when things are working. But when things aren't working, we'll still be able to clearly see which validators are behind. We may want to consider changing the metrics if this proves confusing. Some ideas: 1. Move to a separate task that occasionally polls the latest checkpoints of the configured app contexts 2. Also track the threshold. This way we can construct alerts & dashboards based off the threshold and not be overly concerned if there are some stragglers ### Drive-by changes added `bytesToBytes32` so that we can construct matching lists, which the agents expect to be 0x-prefixed, using a router address config that may include protocol-specific address formats ### Related issues Fixes #3109 ### Backward compatibility yes ### Testing deployed	10 months ago
Trevor Porter	ae4476ad09	Move to reorg period of 1 for mantapacific (#3126 ) ### Description - Moves to a reorg period of 1 for mantapacific instead of 0 - this should avoid the IGP indexing bugs we're seeing where we first get the latest block, then make an eth_getLogs RPC, but the node servicing the latter RPC doesn't yet know of the new latest block ### Drive-by changes Remove some duplication of the reorg period ### Related issues n/a ### Backward compatibility backward compatible ### Testing none yet, other than deploying	10 months ago
Nam Chu Hoai	3339f78537	Support unoptimized InterchainGasPaymaster bytecode (#3137 ) ### Description Testnet4 has unoptimized Bytecode that did not get added as a constant in the checker ### Drive-by changes CLI test was referencing the wrong folder	10 months ago
Yorke Rhodes	e4e4f93fca	Cleanup merge of #3141 (#3164 ) ### Description - Adds changeset for https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3141 ### Drive-by changes - Runs coverage on all packages after `yarn-test` ### Backward compatibility Yes ### Testing Unit tests	10 months ago
Yorke Rhodes	0727a6178e	Pausable ISM (#3141 ) ### Description - Adds pausable hook and ism config support to deployers - Configure testnet pausable hook and ISM - Add pausable ism checking ### Drive-by changes - Refactors ownable config ### Related issues - https://github.com/hyperlane-xyz/issues/issues/706 ### Backward compatibility - Yes ### Testing - Unit Tests and fork tests	10 months ago
J M Rossy	3c298d0646	Fix Smart Provider e2e test (#3150 ) ### Description Remove hard-coding of min block number and topic1 value. ### Drive-by changes Add convenience `isAddress` util function ### Related issues https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3148 ### Backward compatibility Yes	11 months ago
github-actions[bot]	493c160b2e	Version Packages (#3111 ) 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.6.0 ### Minor Changes - 0488ef31d: Add dsrv, staked and zeeprime as validators - 8d8ba3f7a: HyperlaneIsmFactory is now wary of (try)getDomainId or (try)getChainName calls which may fail and handles them appropriately. ### Patch Changes - 67a6d971e: Added `shouldRecover` flag to deployContractFromFactory so that the `TestRecipientDeployer` can deploy new contracts if it's not the owner of the prior deployments (We were recovering the SDK artifacts which meant the deployer won't be able to set the ISM as they needed) - 612d4163a: Add mailbox version const to SDK - @hyperlane-xyz/core@3.6.0 - @hyperlane-xyz/utils@3.6.0 ## @hyperlane-xyz/core@3.6.0 ### Patch Changes - @hyperlane-xyz/utils@3.6.0 ## @hyperlane-xyz/cli@3.6.0 ### Patch Changes - 67a6d971e: Added `shouldRecover` flag to deployContractFromFactory so that the `TestRecipientDeployer` can deploy new contracts if it's not the owner of the prior deployments (We were recovering the SDK artifacts which meant the deployer won't be able to set the ISM as they needed) - Updated dependencies [`67a6d971e`] - Updated dependencies [`612d4163a`] - Updated dependencies [`0488ef31d`] - Updated dependencies [`8d8ba3f7a`] - @hyperlane-xyz/sdk@3.6.0 - @hyperlane-xyz/utils@3.6.0 ## @hyperlane-xyz/helloworld@3.6.0 ### Patch Changes - Updated dependencies [`67a6d971e`] - Updated dependencies [`612d4163a`] - Updated dependencies [`0488ef31d`] - Updated dependencies [`8d8ba3f7a`] - @hyperlane-xyz/sdk@3.6.0 - @hyperlane-xyz/core@3.6.0 ## @hyperlane-xyz/utils@3.6.0 ## @hyperlane-xyz/infra@3.6.0 ### Patch Changes - 67a6d971e: Added `shouldRecover` flag to deployContractFromFactory so that the `TestRecipientDeployer` can deploy new contracts if it's not the owner of the prior deployments (We were recovering the SDK artifacts which meant the deployer won't be able to set the ISM as they needed) - Updated dependencies [`67a6d971e`] - Updated dependencies [`612d4163a`] - Updated dependencies [`0488ef31d`] - Updated dependencies [`8d8ba3f7a`] - @hyperlane-xyz/sdk@3.6.0 - @hyperlane-xyz/helloworld@3.6.0 - @hyperlane-xyz/utils@3.6.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	11 months ago
Kunal Arora	9561931571	fix: failing ci tests for `SmartProvider` and `OpStackIsm.t.sol` (#3148 ) ### Description - Problem: OpStackIsm.t.sol was failing because of very stale block number for fork Fix: Excluding foundry fork testing from CI and updating block number - Problem: SmartProvider getLogs tests failing because the the results end up being an empty list and getConfirmations results a smaller number of confirmations than expected (712 vs 1705184) fix: excluded from ci ### Drive-by changes None ### Related issues None ### Backward compatibility Yes ### Testing Manual	11 months ago
Kunal Arora	8d8ba3f7ab	fix:`HyperlaneIsmFactory` doesn't fail with missing chainMetadata errors (#3142 ) ### Description HyperlaneIsmFactory is now wary of (try)getDomainId or (try)getChainName calls which may fail and handles them appropriately. - switched from chainName to domain in `routingModuleDelta` - replace `getDomainId` with `tryGetDomainId` and `getChainName` with `tryGetChainName` wherever necessary. ### Drive-by changes None ### Related issues None ### Backward compatibility Yes ### Testing Hardhat unit tests	11 months ago
Kunal Arora	67a6d971ed	fix: `testRecipient` CLI bug (#3138 ) ### Description - we were recovering `TestRecipient` from sdk artifacts which means the deployer won't have ownership. So, I added a optional `shouldRecover` boolean which I turned off for TestRecipient deployer (this is only for our artifacts, if they have their own testRecipient, it will still recover that if provided) - moved `TestRecipientDeployer` from cli to sdk and removed duplicated code from infra ### Drive-by changes None ### Related issues - fixes https://github.com/hyperlane-xyz/issues/issues/895 ### Backward compatibility Yes ### Testing Manual (between anvil1 and optimismgoerli)	11 months ago
Paul Balaji	d3d7ad7f97	feat: add foundry and rosetta setup steps (#3134 )	11 months ago

... 5 6 7 8 9 ...

2276 Commits (70c4c28c2fb98efc8bcef48ad33972a2130461b4) All Branches Search

2276 Commits (70c4c28c2fb98efc8bcef48ad33972a2130461b4)

All Branches