hyperlane-monorepo

Commit Graph

Author	SHA1	Message	Date
Paul Balaji	f4ad66a1a1	ci: fix slither (#3956 ) - ci: try fix slither - drive-by: fix a bunch of the warnings from running `yarn` --------- Signed-off-by: Paul Balaji <paul@hyperlane.xyz>	5 months ago
github-actions[bot]	cb9c2aa571	Version Packages (#3910 ) This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @hyperlane-xyz/cli@3.14.0 ### Minor Changes - f4bbfcf08: AVS deployment on mainnet ### Patch Changes - @hyperlane-xyz/sdk@3.14.0 - @hyperlane-xyz/utils@3.14.0 ## @hyperlane-xyz/core@3.14.0 ### Patch Changes - a8a68f6f6: fix: make XERC20 and XERC20 Lockbox proxy-able - @hyperlane-xyz/utils@3.14.0 ## @hyperlane-xyz/helloworld@3.14.0 ### Patch Changes - Updated dependencies [`a8a68f6f6`] - @hyperlane-xyz/core@3.14.0 - @hyperlane-xyz/sdk@3.14.0 ## @hyperlane-xyz/sdk@3.14.0 ### Patch Changes - Updated dependencies [`a8a68f6f6`] - @hyperlane-xyz/core@3.14.0 - @hyperlane-xyz/utils@3.14.0 ## @hyperlane-xyz/utils@3.14.0 ## @hyperlane-xyz/infra@3.14.0 ### Patch Changes - @hyperlane-xyz/helloworld@3.14.0 - @hyperlane-xyz/sdk@3.14.0 - @hyperlane-xyz/utils@3.14.0 ## @hyperlane-xyz/ccip-server@3.14.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	5 months ago
Kunal Arora	f4bbfcf08a	feat: AVS mainnet deployment (#3945 ) ### Description - Added all the strategies used by EigenDA on mainnet here:https://github.com/Layr-Labs/eigenlayer-contracts?tab=readme-ov-file#deployments - Deployed AVS contracts to mainnet - Added contract address to CLI (reminder: strategies are just LST tokens supported for restaking. These are not relevant for us but brings us to parity with most other AVSs). ### Drive-by changes - `avsSigningKey` renamed to `avsSigningKeyAddress` as `avsSigningKey` may imply the private key and confuse operators. ### 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	29f368513f	ci: temporarily skip a flaky test (#3940 ) temporarily skipping this test that occasionally flakes until we can fix it for good --------- Signed-off-by: Paul Balaji <paul@hyperlane.xyz>	5 months ago
Daniel Savu	5a31e7b5d3	chore: debug slow relayer startup (#3932 ) ### Description Opened this PR to debug slow relayer startup, but it actually looks like that's already been fixed by hook indexing. The requirement for fast startup is that the processor sees new messages and then one of the following happens: - (1) if the message is meant for an unknown domain, it drops it ([this log](`6d132b02a3/rust/agents/relayer/src/msg/processor.rs (L269)`)), otherwise - it forwards the message to the submitter, which then: - (2) adds it straight to the confirm queue because it's already been submitted ([here](`6d132b02a3/rust/agents/relayer/src/msg/pending_message.rs (L159)`)) - (3) successfully builds metadata ([here](`6d132b02a3/rust/agents/relayer/src/msg/op_submitter.rs (L231)`)) - (4) in some cases building metadata fails because the ism doesn't exist The relayer logs either of the four cases (in most cases (2), because we're running a second relayer for now). To be even more confident in fast startup, I ran a single relayer and restarted it. New messages were successfully processed according to one of the four cases above, and the prep queues didn't increase ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->	5 months ago
Paul Balaji	9f19cdf469	ci: update action versions (#3927 ) - update to latest versions of actions - notably docker tasks get a couple of major bumps - rename the foundry action to its current name --------- Signed-off-by: Paul Balaji <paul@hyperlane.xyz>	5 months ago
Paul Balaji	b0d26b66e4	fix: test filtering for `.md` changes (#3936 ) fix: test filtering for `.md` changes - fix the rust-skipped flow - add a test-skipped flow to still go green on the required status checks --------- Signed-off-by: Paul Balaji <paul@hyperlane.xyz>	5 months ago
Sergey Kaunov	cb7ae33cde	chore: Update Solidity README.md (#3545 ) Pls, review I got that right. ### Description Corrects a semantic typo. ### Drive-by changes relative paths to the libs are corrected ### Related issues none ### Backward compatibility Yes ### Testing None	5 months ago
overallteach	42a6dbc3e6	chore: remove repetitive words (#3644 ) ### Description <!-- What's included in this PR? --> remove repetitive words ### 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 --> Signed-off-by: overallteach <cricis@foxmail.com>	5 months ago
vamsisai	41e739b513	chore: fix typos in code_of_conduct.md (#3890 ) This PR addresses minor typographical errors and readability improvements in the Code of Conduct file. Specifically: - Corrected "critism" to "criticism". - Corrected "tenant" to "tenet". - Corrected "discrimnate" to "discriminate. These changes are intended to enhance the professionalism and clarity of the document, ensuring it accurately reflects the project's standards.	5 months ago
Paul Balaji	47831d5211	ci: ignore `*.md` changes when triggering rust/test workflows (#3930 ) - skips unnecessary tests for PRs on just markdown changes e.g. README Signed-off-by: Paul Balaji <paul@hyperlane.xyz>	5 months ago
Paul Balaji	65e4b05f77	chore: fix mainnet3 agent config (#3931 ) chore: fix mainnet3 agent config follow-on from https://github.com/hyperlane-xyz/hyperlane-registry/pull/49 Signed-off-by: Paul Balaji <paul@hyperlane.xyz>	5 months ago
Connor McEwen	939fa814d9	chore: add release steps to readme (#3928 ) ### Description Add some release/prerelease directions to readme	6 months ago
Daniel Savu	826b4ae57f	feat: batching igp (#3870 ) ### Description Deducts IGP cost from senders of messages within a batch, based on the total gas used by the batch and the estimates for submitting messages individually. The formula is `gas_used_by_operation = gas_used_by_tx * (operation_estimated_gas / total_estimated_cost)` Note that the individual estimate have a buffer value added to them (currently 75k), which will slightly skew proportions, though by a negligible amount. For example, given these estimates in a batch: 150k, 160k, 180k, if we add 80k to each, we go from e.g. 0.312 for the first message to 0.319 -> 2.25% error which isn't so bad. The error can be larger if operations within a batch have very different estimates, but realistically within a 5% range based on back-of-the-napkin calculations. ### Drive-by changes - The batching feature introduced an bug whereby gas expenditure would only be deducted in the `confirm` step. Now this is done in the `submit` step to account for txs that revert - Sealevel e2e can now be disabled for faster iteration! I've not done the cleanest job, but even the fact that we have this will reduce the time to run e2e locally by more than half. To use it, set `SEALEVEL_ENABLED=false` when running `run-locally` - e2e uses a new utility called `get_matching_lines`, that can be used to count (and in the future _parse_) logs, to reconstruct the state of the relayer and have more expressive correctness checks. This is used to make sure that gas is deducted for all messages, including those in batches. ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3709 ### Backward compatibility Yes ### Testing E2E, using `get_matching_lines`	6 months ago
Mohammed Hussan	36e9a2e783	feat(infra): Command to create endpoint secrets; cleaning up endpoints (#3922 ) ### Description - clean up references to the single rpc secrets which are redundant as the multi rpc secret includes the single one - add get-rpc-urls script to get secret rpc urls for a given environment and chain - add set-rpc-urls script to: 1) create the secret if it does not exist and add the first secret version or 2) add new secret version to an existing secret and disable the previous version of the secret. The script with test all rpc urls to ensure that they are valid example usage: get-rpc-urls `yarn tsx scripts/secret-rpc-urls/get-rpc-urls.ts -e testnet2 -c fuji` set-rpc-urls `yarn tsx scripts/secret-rpc-urls/set-rpc-urls.ts -e testnet2 -c fuji -r https://api.avax-test.network/ext/bc/C/rpc,https://rpc.ankr.com/avalanche_fuji` <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> - replace `withNetwork` util with `withChain` as we rarely use network internally to reference a chain ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing - manual <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->	6 months ago
Daniel Savu	942aba8e55	feat(evm): collaborative indexing through txid sharing (#3833 ) ### Description - improved indexing reliability by sharing channels between indexing tasks, such that they inform one another when they come across a hyperlane-related transaction - the receiving end will then get the receipt of that tx and filter it for events relevant to it - this adds some flexibility to indexing since we can stop relying on watermark cursor entirely: as long as we have one task using sequence indexing, all others can rely on being informed by their channels about what txs to index - this PR is only for the EVM chains, but can be easily extended ### Drive-by changes - Enforces gas payments for all chains in e2e (previously this only used to be the case for sealevel) - The channel size is configured per type, similarly to the indexing cursor, in `contract_sync/cursors/mod.rs` - Reduces log verbosity is some places, e.g. by manually implementing `Debug` to exclude fields that aren't relevant to debugging (maybe there's even a macro annotation to exclude, but I haven't checked) - Renames `MpmcReceiver` -> `BroadcastReceiver` ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3267 ### 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 e2e tested with the watermark cursor manually disabled	6 months ago
Daniel Savu	4261df74bb	chore: restrict for how long the backward syncer can block (#3918 ) ### 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 -->	6 months ago
Avi Atkin	8693ca33a7	chore: create `funding.json` (#3919 ) ### Description - Add verification for OP retro funding round 4 --------- Co-authored-by: Nam Chu Hoai <nambrot@googlemail.com> Co-authored-by: Paul Balaji <paul@hyperlane.xyz>	6 months ago
Paul Balaji	50d2f29324	ci: configure merge queue for `main` (#3913 ) - configure the rust/test workflows to support merge queues into `main` --------- Signed-off-by: Paul Balaji <paul@hyperlane.xyz>	6 months ago
Noah Bayindirli 🥂	ba946f1eff	fix(config): switch to recommended 'rust-analyzer' from deprecated 'cargo' (#3886 ) ### Description - switch to recommended `rust-analyzer` since `cargo` is deprecated	6 months ago
Mohammed Hussan	cfa20a46fa	chore(infra): Update docker image tag for kathy and key funder (#3902 ) ### Description Update docker image tag for kathy and key funder <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->	6 months ago
Yorke Rhodes	a8a68f6f61	test: XERC20 and XERC20 Lockbox integration tests (#3849 )	6 months ago
Daniel Savu	335310355c	feat: relayer dashboard template (#3898 ) ### Description Relayer metrics template for monitoring & alerting. Looks like so: ![Screenshot 2024-05-29 at 18 08 26](https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/23065004/581fdd7e-3f68-490f-bd6d-bf58ad688ba3)	6 months ago
Paul Balaji	d10b035ec2	fix: testnet4 holesky config (#3900 ) ran `yarn tsx ./scripts/agents/update-agent-config.ts -e testnet4` and updated testnet4 config Signed-off-by: Paul Balaji <paul@hyperlane.xyz>	6 months ago
Mohammed Hussan	efa9025f5e	chore(infra): Remove RpcConsensusType usage in infra now that SmartProvider is used instead (#3882 ) ### Description Removed references to RpcConsensusType where TS-based providers are used in infra <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->	6 months ago
Kunal Arora	554f875ebf	feat: core deployment on Holesky (#3776 ) ### Description Core deployment on Holesky ### Drive-by changes None ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3597 ### Backward compatibility Yes ### Testing Manual	6 months ago
Trevor Porter	db9f733e4f	fix: use secret RPC urls in infra, apply environment-specific registry overrides (#3875 ) ### Description A while back, it seems secret RPC URLs stopped being used by monorepo services (see https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3179/files#diff-ba3b7bea2b5c046acd88d25ed382df875b49d77e061f2ef8347ffcc741c0353eR34). This adds them back. Some things to note on the approach: - Sadly, due to the way some of the infra config generation works, we're forced to use synchronous interfaces for getting chain metadata in a bunch of places. This is why `getRegistry` returns a `FileSystemRegistry`, which is a `SynchronousRegistry`. - Applying secrets / overrides requires us to do things async for two reasons -- one is just that fetching from GCP secrets is an async operation, the other is that a `MergedRegistry` is not a `SynchronousRegistry`. The approach I've taken is that there are two ways of getting a registry - using `getRegistry` will give the synchronous version that can continue to be used by our sync config generation, but it won't have any environment-specific overrides (tx overrides or secrets). To get an async registry with environment-specific overrides, the `getRegistry` function on the EnvironmentConfig is used. - Overrides are now more succinct as the merging happens later in the pipeline ### Drive-by changes - Started moving away from using the gcloud CLI under the hood for GCP operations and toward using the GCP secret SDK - Updated the mainnet3 key funder to fix an incident, but will follow up with a fresh deploy once this is mergd ### Related issues - These are the code changes for https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3774, but I'll follow up with fresh deploys for the monorepo services ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: Connor McEwen <connor.mcewen@gmail.com> Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz> Co-authored-by: J M Rossy <jm.rossy@gmail.com>	6 months ago
github-actions[bot]	8a6654477e	Version Packages (#3842 ) This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @hyperlane-xyz/core@3.13.0 ### Minor Changes - babe816f8: Support xERC20 and xERC20 Lockbox in SDK and CLI - b440d98be: Added support for registering/deregistering from the Hyperlane AVS ### Patch Changes - Updated dependencies [`0cf692e73`] - @hyperlane-xyz/utils@3.13.0 ## @hyperlane-xyz/cli@3.13.0 ### Minor Changes - b22a0f453: Add hyperlane validator address command to retrieve validator address from AWS - 39ea7cdef: Implement multi collateral warp routes - babe816f8: Support xERC20 and xERC20 Lockbox in SDK and CLI - b440d98be: Added support for registering/deregistering from the Hyperlane AVS ### Patch Changes - b6b26e2bb: fix: minor change was breaking in registry export - Updated dependencies [`39ea7cdef`] - Updated dependencies [`babe816f8`] - Updated dependencies [`0cf692e73`] - @hyperlane-xyz/sdk@3.13.0 - @hyperlane-xyz/utils@3.13.0 ## @hyperlane-xyz/sdk@3.13.0 ### Minor Changes - 39ea7cdef: Implement multi collateral warp routes - babe816f8: Support xERC20 and xERC20 Lockbox in SDK and CLI - 0cf692e73: Implement metadata builder fetching from message ### Patch Changes - Updated dependencies [`babe816f8`] - Updated dependencies [`b440d98be`] - Updated dependencies [`0cf692e73`] - @hyperlane-xyz/core@3.13.0 - @hyperlane-xyz/utils@3.13.0 ## @hyperlane-xyz/utils@3.13.0 ### Minor Changes - 0cf692e73: Implement metadata builder fetching from message ## @hyperlane-xyz/helloworld@3.13.0 ### Patch Changes - b6b26e2bb: fix: minor change was breaking in registry export - Updated dependencies [`39ea7cdef`] - Updated dependencies [`babe816f8`] - Updated dependencies [`b440d98be`] - Updated dependencies [`0cf692e73`] - @hyperlane-xyz/sdk@3.13.0 - @hyperlane-xyz/core@3.13.0 ## @hyperlane-xyz/infra@3.13.0 ### Minor Changes - 39ea7cdef: Implement multi collateral warp routes - 0cf692e73: Implement metadata builder fetching from message ### Patch Changes - b6b26e2bb: fix: minor change was breaking in registry export - Updated dependencies [`b6b26e2bb`] - Updated dependencies [`39ea7cdef`] - Updated dependencies [`babe816f8`] - Updated dependencies [`0cf692e73`] - @hyperlane-xyz/helloworld@3.13.0 - @hyperlane-xyz/sdk@3.13.0 - @hyperlane-xyz/utils@3.13.0 ## @hyperlane-xyz/ccip-server@3.13.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	6 months ago
omahs	806f9842de	fix: duplicate word typos (#3854 )	6 months ago
Kunal Arora	b440d98be3	feat: CLI command for (de)registering from AVS (#3790 ) ### Description - CLI commands for registering/deregistering an operator from the AVS - uses the encrypted local key store as source of operator key - Web3Signer not implemented yet ### Drive-by changes None ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3598 (duplicate) - also fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3758 ### Backward compatibility Yes ### Testing Onchain https://holesky.etherscan.io/tx/0x95d95f6fcf1f80d0911124bd0a85ac848eecedc8ec39b3ceba6e1a30792c5651 and https://holesky.etherscan.io/tx/0xd1d1b56d45c30276596b73e040e3747ca7ef90977182f1912c5b399559d2a503 --------- Co-authored-by: Connor McEwen <connor.mcewen@gmail.com> Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>	6 months ago
Kunal Arora	d0ce9081dd	feat: support attesting signing key for Hyperlane AVS (#3847 ) ### Description - Adding support for attesting signing key and key rotation from here https://github.com/Layr-Labs/eigenlayer-middleware/pull/252 ### Drive-by changes None ### Related issues None ### Backward compatibility Yes ### Testing Tested by Eigenlayer here: https://github.com/Layr-Labs/eigenlayer-middleware/blob/dev/test/unit/ECDSAStakeRegistryUnit.t.sol	6 months ago
Yorke Rhodes	0cf692e731	Implement metadata fetching from message (#3702 ) ### Description - Uses derived hook and ISM config and dispatchTx of message to implement metadata fetching ### Drive-by changes - Change yarn cache key to workaround https://github.com/actions/toolkit/issues/658 - Make `hyperlane message send` use `HyperlaneCore.sendMessage` ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3450 ### Backward compatibility Yes ### Testing E2E testing BaseMetadataBuilder	6 months ago
Yorke Rhodes	babe816f86	feat: support xerc20 and xerc20Lockbox in CLI (#3753 ) ### Description - Supports xERC20 and xERC20Lockbox in CLI and UI ### Drive-by changes - Rename XERC20Collateral to XERC20 ### Backward compatibility - Yes ### Testing - Manual	6 months ago
Connor McEwen	b6b26e2bb8	fix: minor change was breaking in registry export (#3821 ) ### Description Fixes compat with with breaking changes in registry 1.3.0 --------- Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz> Co-authored-by: J M Rossy <jm.rossy@gmail.com>	6 months ago
Daniel Savu	214f503e53	feat: forward-backward message processor (#3775 ) ### Description - adds logic for iterating message nonces in the processor task in forward-backward fashion - removes all manual calls that were updating the next nonce to query. This is done automatically in the iterator struct now - stores the highest known message nonce in the db, which is used to initialize the iterator ### Drive-by changes - Converts the concrete HyperlaneDb type stored in the processor to a trait obj, to enable mocking db responses ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3796 - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3816 ### Backward compatibility Yes - if there is no db entry for the new prefix, the processor starts from nonce zero, so no migration is required ### Testing Unit testing + e2e	6 months ago
Trevor Porter	704675c7e1	chore: update infra service images (key funder, kathy) (#3843 ) ### Description - Updates key funder and kathy images on testnet4 and mainnet3 - Sorts desired balances and is more explicit about requirements for kathy chains (https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3732 will expand on this to make sure we keep this up to date) - I found it surprising that if the kathy balance wasn't specified in the config, then key funder would default to funding the full relayer amount. Made this not be the case ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: Paul Balaji <paul@hyperlane.xyz>	6 months ago
Nam Chu Hoai	f2dc925cb3	Remove nambrot from codeowners (#3846 ) It had to happen #RIP, my getting review requested ended up too noisy to miss actual tags in issues	6 months ago
Yorke Rhodes	39ea7cdef9	feat: multi collateral warp routes (#3820 ) ### Description Adds multicollateral warp route support to the CLI. Dedupes SDK warp route types and zod schemas (via type inference). ### Drive-by changes - Removes scattered ICA logic from deployers in favor of config time resolution ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3639 ### Backward compatibility - No ### Testing - E2E Tests	6 months ago
Ali Alaoui	b22a0f4538	feat: CLI command to get validator address by S3 bucket or KMS key ID (#3795 ) ### Description Create the `hyperlane validator address` command, making it easy for users to get the address of their validator key. ### Related issues Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3341 ### Backward compatibility Yes ### Testing Manual testing under all conditions/edge cases --------- Co-authored-by: J M Rossy <jm.rossy@gmail.com>	6 months ago
Trevor Porter	fdd1421540	fix: fetch the registry's `main` branch in the monorepo Docker image (#3841 ) ### Description Infra services require the presence of a registry. This is expected to be found at the env var REGISTRY_URI. This PR fetches the latest registry from `main` and uses that as the registry in the monorepo image for infra services / scripts to make use of. To prevent caching of this git clone, we use a build-time arg such that if the arg changes, any later layers in the image will be ran. See https://stackoverflow.com/a/73501716 ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Partially fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3827 - we'll need a deploy to fully close it out ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->	6 months ago
Trevor Porter	3f2216574c	fix: fix CI tests to correctly use registry from `main` (#3840 ) ### Description As part of #3788, we moved to using the registry's `main` branch in CI. I accidentally didn't include this for other non-required tests that I didn't realize were failing, and then automerge merged that PR. This ensures the registry is usable by these other tests ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->	6 months ago
Trevor Porter	37af3dc6ba	feat: deploy to zetachain and redstone (#3788 ) ### Description - Deploys to zetachain and redstone - Some learnings can be found in https://discord.com/channels/935678348330434570/1240168332813144084 Chains not yet fully connected: - inevm (Mailbox ownership situation makes this hard) - mantapacific (waiting on an update to the multisig ownership set there, then will create the tx) - non-EVM chains ### Drive-by changes - decreased ethereum cost from $2 to $1.5 following some feedback - Added Superform to the blast set - Allowed for concurrent deploys I originally had some ugly caching to avoid checking storage gas oracles so much (we check them for each route in a routing hook configuration), but I've removed this. Calling it out for the future though `232695dd6c` ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->	6 months ago
Daniel Savu	27aabf238c	feat: Relayer tokio task instrumentation (#3760 ) ### Description - Started off adding tokio-metrics but then realised those are quite general, so while we do have instrumentation it's not exposed in our metrics endpoint - switched to adding [tokio-console](https://github.com/tokio-rs/console/tree/main), which does give insight into the lifetime of specific tasks, so we can check which ones take up a long time during relayer startup. These are only visible at the `dependencyTrace` log level, so don't affect performance in the `hyperlane` context. ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Helps debug https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3454 and any future performance issues - Does half the work for https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3239 (still need to expose these in the metrics endpoint and import the grafana template) ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->	6 months ago
Yorke Rhodes	1f9a3e9be6	fix: Ensure dir exists before reading in fixture tests (#3819 ) ### Description - Makes SDK tests not require solidity tests have run first	6 months ago
J M Rossy	6971d8da02	chore: update outdated info in Readme files (#3830 )	6 months ago
Daniel Savu	1c4cf44c91	fix: allow all log levels in release build (#3824 ) ### Description Found the reason why we never had `trace` level logs in release builds - the `tracing` crate had a feature flag enabled that would wipe out all trace calls at compile time :( ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3823 ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->	6 months ago
Avi Atkin	5ae6e329ac	chore: Update README to reflect v2 deprecation (#3654 )	6 months ago
Trevor Porter	335a0d7479	feat: add agent config for Osmosis Mainnet (#3825 ) ### Description - Added agent config description for Osmosis Mainnet - Updated infra test to allow agent config chains to be a superset of infra chains Taken from @byeongsu-hong's https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3766, but with a fixed test ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: byeongsu-hong <hong@byeongsu.dev>	6 months ago
Trevor Porter	a574b76584	Update clusters to use new prometheus version (#3772 ) ### Description GKE was complaining that the kube-state-metrics version we were running with was hitting deprecated APIs, I expect this to fix it. Some minor changes to the infra setup meant that now the push gateway has a different service name, kinda annoyingly with a double `prometheus` in the name. I updated key funder to push to the new gateway ### Drive-by changes We no longer use GKE autopilot, so started using the node exporter too ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->	6 months ago
Connor McEwen	767c20f9ee	chore: enforce conventional commits on PR titles (#3803 ) ### Description uses this github action: https://github.com/amannn/action-semantic-pull-request	6 months ago

1 2 3 4 5 ...

2228 Commits (f4ad66a1a1d6dc09cd04144362bbbb44fa0092d3) All Branches Search

2228 Commits (f4ad66a1a1d6dc09cd04144362bbbb44fa0092d3)

All Branches