hyperlane-monorepo

Commit Graph

Author	SHA1	Message	Date
Trevor Porter	a109937f96	chore: some throughput tweaks (#4036 ) ### Description Context: https://discord.com/channels/935678348330434570/1254036693217054794 ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->	5 months ago
Paul Balaji	7adbd27634	feat(infra): deploy to a set of specific chains (#4040 ) - feat(infra): deploy to a set of specific chains - allows users to specify more than 1 target chain to deploy to - provides suggestions of available chains to deploy (given local registry) ![image](https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/10051819/020939a9-220d-47dc-b434-e9342ea2ff0f) --------- Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Paul Balaji	1876f68127	feat: pin monorepo to a specific registry version (#4031 ) feat: pin monorepo to a specific registry version - introducing a `.registryrc`, which can be a commit hash, branch or tag - introduce a new action just for checking out a registry - remove registry caching because it's quicker now to just checkout the specified version --------- Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	5 months ago
J M Rossy	6398aab727	chore: Upgrade registry to 2.1.1 (#4033 ) ### Description To pickup fix in https://github.com/hyperlane-xyz/hyperlane-registry/pull/71 ### Backward compatibility Yes	5 months ago
Daniel Savu	b54c14cd31	chore: re-enforce a whitelist policy in the RC relayer (#4032 ) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->	5 months ago
Snoppy	f1fe882e3b	chore: fix typos (#3645 ) fix minor typos Signed-off-by: snoppy <michaleli@foxmail.com> Co-authored-by: Paul Balaji <paul@hyperlane.xyz>	5 months ago
Paul Balaji	18056aafdd	chore(ci): fix ci workflow filters on main (#4022 ) chore(ci): fix ci workflow filters on main generally copying the path/filters for `pull_request` into `push` so that we correctly run the right workflows --------- Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Paul Balaji	c5a5e264b8	chore: enable `osmosis` on relayer (#4028 ) - chore: enable `osmosis` on relayer - drive-by add default chain signer/key/type to agent config - `signer.key` is copied from `neutron` --------- Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Trevor Porter	832351d0d0	chore: set agent and environment specific resource requests (#4027 ) ### Description - based off https://abacusworks.grafana.net/d/FSR9YWr7k, updated resource requests for all agents. Because mainnet3 sees so many more messages and more chains, the resource needs there are higher - allows for resources to be defined in infra - previously we'd just use the default value in the values.yaml of the helm charts. Also makes the resources specific to the type of agent, which is nice because relayers require much higher spec than validators - I haven't deployed this yet, will do so when I get a review ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Fixes https://github.com/hyperlane-xyz/issues/issues/1288 ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->	5 months ago
Paul Balaji	23ad36ab98	feat(infra): allow specifying chains to deploy validators for in infra (#4014 ) - allow someone to provide a specific set of chains to deploy validators for deploying validator: ![image](https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/10051819/906c3c45-27e1-43ca-ac21-176ade91a500) deploying relayer: ![image](https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/10051819/a5c6af09-1f6a-4c1a-8652-05fbb10ced30) --------- Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Trevor Porter	9aca29260b	chore: deploy relayer with new image and ezETH metrics (#3993 ) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->	5 months ago
Paul Balaji	0d12ff31cd	feat(ci): rust caching in `test` workflow (#4015 ) - draft: improve rust target caching in ci - separate caches for e2e-cosmwasm, e2e-noncosmwasm, cli-e2e test - drive-by adding `restore-keys` test expectation: - 1st commit of rust changes will take the full required time as it'll have to do a fresh build and then cache - subsequent builds of a particular rust change will be faster because it'll pickup the rust cache from before --------- Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	6 months ago
Trevor Porter	c84a1dc73b	feat: address blacklisting in the relayer (#4000 ) ### Description See context here https://discord.com/channels/935678348330434570/1236041564673806427/1252918894755319920 and https://discord.com/channels/935678348330434570/1252953507833708605/1252954456400592997 This is a rudimentary first step toward blacklisting addresses. Future options are outlined in https://discord.com/channels/935678348330434570/1236041564673806427/1252918894755319920. Eventually we can also fetch these addresses directly within the agent from an updated list that we cache and re-fetch occasionally. For now, this just relies on configured addresses. The approach is: - Allow hex addresses to be configured. These are intentionally treated as a Vec<u8> instead of an H160 / H256. This is because treating them as H160 is a leak of Ethereum-specific logic into non-chain-specific code in the relayer, and treating them as H256 would pad Ethereum addresses with a bunch of zeroes which would diminish the accuracy of our heuristic implemented in this. The subsequence stuff is a bit unfortunate because it's O(n^2) but 🤷‍♂️ - The heuristic is as follows - if any of the configured addresses are found as a subsequence in the message sender, recipient, or body, it's thrown out by the message processor, and the message will never make its way to the op_submitter. This heuristic for the body is to prevent warp route transfers that include that address. We could maybe convert Vec<u8> to H256 for the sender and recipient, I'm open to this - I just went with the substring approach bc it felt easiest tbh. ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Fixes https://github.com/hyperlane-xyz/issues/issues/1285 ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->	6 months ago
Nam Chu Hoai	c6ba381e44	chore: add more multisigs (#3974 ) ### Description Add multisig owners for linea, mode and blast. Expected violations are mailbox,proxyadmin, and ism violations (since the routing ism expected owner is now different) --------- Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>	6 months ago
github-actions[bot]	b758a5949c	Version Packages (#3991 ) This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @hyperlane-xyz/sdk@3.16.0 ### Minor Changes - 5cc64eb09: Add validator addresses for linea, fraxtal, sei. Estimate gas and add 10% buffer inside HyperlaneIsmFactory as well. ### Patch Changes - f9bbdde76: Fix initial total supply of synthetic token deployments to 0 - @hyperlane-xyz/core@3.16.0 - @hyperlane-xyz/utils@3.16.0 ## @hyperlane-xyz/core@3.16.0 ### Patch Changes - @hyperlane-xyz/utils@3.16.0 ## @hyperlane-xyz/cli@3.16.0 ### Patch Changes - Updated dependencies [`f9bbdde76`] - Updated dependencies [`5cc64eb09`] - @hyperlane-xyz/sdk@3.16.0 - @hyperlane-xyz/utils@3.16.0 ## @hyperlane-xyz/helloworld@3.16.0 ### Patch Changes - Updated dependencies [`f9bbdde76`] - Updated dependencies [`5cc64eb09`] - @hyperlane-xyz/sdk@3.16.0 - @hyperlane-xyz/core@3.16.0 ## @hyperlane-xyz/utils@3.16.0 ## @hyperlane-xyz/infra@3.16.0 ### Minor Changes - 5cc64eb09: Add support for new chains: linea, fraxtal, sei. Support osmosis remote. Drive-by fix to always fetch explorer API keys when running deploy script. ### Patch Changes - 5cc64eb09: Allow selecting a specific chain to govern in check-deploy script - Updated dependencies [`f9bbdde76`] - Updated dependencies [`5cc64eb09`] - @hyperlane-xyz/sdk@3.16.0 - @hyperlane-xyz/helloworld@3.16.0 - @hyperlane-xyz/utils@3.16.0 ## @hyperlane-xyz/ccip-server@3.16.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	6 months ago
Trevor Porter	47338f983d	fix: set resource requests for prometheus server & node exporter (#3998 ) ### Description See https://discord.com/channels/935678348330434570/935679524534911007/1252943931121864824 - an attempt to fix some intermittent issues we've seen with prometheus ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->	6 months ago
Daniel Savu	f227eec892	fix: e2e invariant flake (#4017 ) ### Description Context is explained in the comment, copying it here: ``` // TODO: Sometimes we find more logs than expected. This may either mean that gas is deducted twice for the same message due to a bug, // or that submitting the message transaction fails for some messages. Figure out which is the case and convert this check to // strict equality. // EDIT: Having had a quick look, it seems like there are some legitimate reverts happening in the confirm step // (`Transaction attempting to process message either reverted or was reorged`) // in which case more gas expenditure logs than messages are expected. ``` ### 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
Paul Balaji	8ce2a71f20	chore: reconcile mainnet config json with registry (#4016 ) chore: reconcile mainnet config json with registry Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	6 months ago
Tien Dao	683a96257e	fix: reduce loop test igpconfig (#4005 ) ### Description Refactor `testIgpConfig` in `testUtils.ts` for Enhanced Readability and Maintainability by reduce loop <!-- What's included in this PR? --> ### Drive-by changes 1. Constant Usage: Introduced `OVERHEAD_COST` as a constant to replace the magic number `60000`, making the purpose of this value clearer and the code easier to update. 2. Improved Readability: By using descriptive names and constants, the function is now easier to understand at a glance, which is particularly beneficial for new contributors or during code reviews. 3. Dynamic Configuration Logic: Ensured that the configuration for `overhead` and `oracleConfig` is dynamically generated for each chain, excluding the current chain to simulate realistic test scenarios. <!-- Are there any minor or drive-by changes also included? --> These changes do not alter the logic but make the codebase cleaner and more maintainable. ### 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: tiendn <tiendn.works@gmail.com>	6 months ago
Yorke Rhodes	f9bbdde764	fix: derived token supply to 0 (#4010 ) ### Description Token deployer should always derive token metadata's total supply to 0, otherwise the collateral token's total supply will be minted initially on the synthetic, creating 2x the desired total supply. ### Related issues - Regression introduced by https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3820 - opens https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4013 ### Backward compatibility Yes ### Testing Unit Tests	6 months ago
Tien Dao	6cff4a2a9e	fix: prevent duplication in verification artifacts array (#4001 ) ## Enhance Artifact Deduplication in HyperlaneDeployer ### Description Overview: The `addVerificationArtifacts` method in the `HyperlaneDeployer` class previously added verification artifacts without checking for duplicates, potentially leading to redundant data that could affect performance and reliability. This PR introduces a mechanism to prevent such duplication by implementing a shallow comparison check before adding new artifacts. Changes: - Modified the `addVerificationArtifacts` method to include a shallow comparison against existing artifacts. - Used direct property comparisons to efficiently prevent the addition of duplicate entries. - Ensured that the comparison handles large ABI-encoded strings efficiently by comparing string references. Benefits: - Efficiency: Reduces unnecessary processing and storage by avoiding duplicate entries. - Accuracy: Ensures that the verification process uses a unique set of artifacts, improving the reliability of deployment verifications. - Performance: Minimizes the overhead associated with handling large sets of data, particularly with large ABI-encoded strings. Testing: - Added unit tests to verify that duplicates are not added to the artifacts array. - Ensured existing integration tests pass with the new changes, confirming backward compatibility and functional integrity. This update streamlines the deployment process by ensuring that only necessary and unique verification artifacts are considered, thereby optimizing both memory usage and processing time during contract deployments. --------- Co-authored-by: tiendn <tiendn.works@gmail.com>	6 months ago
Daniel Savu	030eaf1204	chore: bump agent docker images (#3999 ) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->	6 months ago
Daniel Savu	3bb9d0a767	fix(cosmos): validator checkpoint & agent indexing improvements (#3958 ) - propagates RPC errors to the indexing logic, so errors cause sleeps instead of overwhelming the RPCs. This also greatly reduces cosmos log noisiness: from 9.5k logs per min, to 2.5k logs per min. - checks for published checkpoints in reverse, to prioritize recent messages among those from before the validator was spun up - fixes a validator bug where errors in checkpoint publishing would cause the entire checkpoint queue to be reiterated through, from scratch - Builds on top of https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3887 so we can test this out on osmosis ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->	6 months ago
Trevor Porter	bbbe93206f	chore: bump default ISM max depth from 5 to 7 (#3989 ) ### Description Needed for some Renzo messages that hit the max depth ### Drive-by changes - drive by to update the agent config with the updated registry ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->	6 months ago
Paul Balaji	9c7cf45c41	feat: reduce extraneous entries in generated registry/agent artifacts (#3988 ) - filters out remote domain metadata from configs written to disk ``` "ancient8": { // this gets removed "arbitrum": { "aggregationHook": "0xblahblahblah", "interchainSecurityModule": "0xblahblah" ...etc }, // keep the usual entries like this "aggregationHook": "0x1EF4ED658d542524d1D547ba2F94d3B038a55b8f", "batchContractAddress": "0x4C97D35c668EE5194a13c8DE8Afc18cce40C9F28", "blockExplorers": [ ...etc ``` - no longer include secret overrides in the configs written to disk - i.e. use public registry RPCs and chain metadata (want our output to be like that of update-agent-config, but with updated contract addresses only) --------- Signed-off-by: Paul Balaji <paul@hyperlane.xyz>	6 months ago
Paul Balaji	5cc64eb095	feat: deploy to new chains (fraxtal, linea, sei) (#3887 ) https://github.com/hyperlane-xyz/issues/issues/1279 - adds `fraxtal`, `linea`, `sei` - supports `osmosis` as a remote - ~drive-by hack to skip reconfiguring the same gas oracle (cc @tkporter)~ - drive-by fix to bring the logic of estimating tx + adding 10% buffer into the ism factory (as originally seen in the multiprovider handleDeploy function) - drive-by fix for creating custom safes - drive-by support of `osmosis` as a remote chain - drive-by addition of `osmosis` to the rust agent --------- Signed-off-by: Paul Balaji <paul@hyperlane.xyz> Co-authored-by: Trevor Porter <tkporter4@gmail.com> Co-authored-by: nambrot <nambrot@googlemail.com>	6 months ago
Ayene	6171d82c82	chore: fix broken links (#3970 ) ### Description changed links pointing to Solana docs due to migration to different repository	6 months ago
github-actions[bot]	6b5a763e78	Version Packages (#3980 ) This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @hyperlane-xyz/core@3.15.1 ### Patch Changes - 6620fe636: fix: `TokenRouter.transferRemote` with hook overrides - @hyperlane-xyz/utils@3.15.1 ## @hyperlane-xyz/cli@3.15.1 ### Patch Changes - 921e449b4: Support priorityFee fetching from RPC and some better logging - Updated dependencies [`acaa22cd9`] - Updated dependencies [`921e449b4`] - @hyperlane-xyz/sdk@3.15.1 - @hyperlane-xyz/utils@3.15.1 ## @hyperlane-xyz/helloworld@3.15.1 ### Patch Changes - 6620fe636: fix: `TokenRouter.transferRemote` with hook overrides - Updated dependencies [`6620fe636`] - Updated dependencies [`acaa22cd9`] - Updated dependencies [`921e449b4`] - @hyperlane-xyz/core@3.15.1 - @hyperlane-xyz/sdk@3.15.1 ## @hyperlane-xyz/sdk@3.15.1 ### Patch Changes - acaa22cd9: Do not consider xERC20 a collateral standard to fix fungibility checking logic while maintaining mint limit checking - 921e449b4: Support priorityFee fetching from RPC and some better logging - Updated dependencies [`6620fe636`] - @hyperlane-xyz/core@3.15.1 - @hyperlane-xyz/utils@3.15.1 ## @hyperlane-xyz/utils@3.15.1 ## @hyperlane-xyz/infra@3.15.1 ### Patch Changes - Updated dependencies [`6620fe636`] - Updated dependencies [`acaa22cd9`] - Updated dependencies [`921e449b4`] - @hyperlane-xyz/helloworld@3.15.1 - @hyperlane-xyz/sdk@3.15.1 - @hyperlane-xyz/utils@3.15.1 ## @hyperlane-xyz/ccip-server@3.15.1 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	6 months ago
Alex	acaa22cd90	fix: Do not consider xERC20 a collateral standard 2 (#3977 ) Amending https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3973 to ensure output of the CLI doesn't incorrectly add `collateralAddressOrDenom` to xERC20 configs. --------- Co-authored-by: nambrot <nambrot@googlemail.com>	6 months ago
Yorke Rhodes	1579ca221c	fix: disable initializers in xERC20 adapters (#3979 ) ### Description - Follow OZ best practice from https://docs.openzeppelin.com/upgrades-plugins/1.x/writing-upgradeable#initializing_the_implementation_contract ### Backward compatibility Yes ### Testing Unit tests	6 months ago
Nam Chu Hoai	921e449b41	feat: support priorityFee fetching from RPC and some better logging (#3972 ) ### Description `main` equivalent for https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3971 to get it in for the latest warp UI deployment	6 months ago
Yorke Rhodes	6620fe6367	fix: eliminate branching from `TokenRouter` (#3878 ) ### Description Fixes bug in `TokenRouter` which dispatches messages to token recipient rather than address in `Router` table when hook overrides are provided. ### Drive-by changes Simplifies inheritance tree of `TokenRouter` > `GasRouter` > `Router` > `MailboxClient` ### Backward compatibility Yes ### Testing Unit Tests	6 months ago
github-actions[bot]	27580329eb	Version Packages (#3967 ) This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @hyperlane-xyz/core@3.15.0 ### Minor Changes - 51bfff683: Mint/burn limit checking for xERC20 bridging Corrects CLI output for HypXERC20 and HypXERC20Lockbox deployments ### Patch Changes - @hyperlane-xyz/utils@3.15.0 ## @hyperlane-xyz/cli@3.15.0 ### Minor Changes - 51bfff683: Mint/burn limit checking for xERC20 bridging Corrects CLI output for HypXERC20 and HypXERC20Lockbox deployments ### Patch Changes - Updated dependencies [`51bfff683`] - @hyperlane-xyz/sdk@3.15.0 - @hyperlane-xyz/utils@3.15.0 ## @hyperlane-xyz/sdk@3.15.0 ### Minor Changes - 51bfff683: Mint/burn limit checking for xERC20 bridging Corrects CLI output for HypXERC20 and HypXERC20Lockbox deployments ### Patch Changes - Updated dependencies [`51bfff683`] - @hyperlane-xyz/core@3.15.0 - @hyperlane-xyz/utils@3.15.0 ## @hyperlane-xyz/helloworld@3.15.0 ### Patch Changes - Updated dependencies [`51bfff683`] - @hyperlane-xyz/sdk@3.15.0 - @hyperlane-xyz/core@3.15.0 ## @hyperlane-xyz/utils@3.15.0 ## @hyperlane-xyz/infra@3.15.0 ### Patch Changes - Updated dependencies [`51bfff683`] - @hyperlane-xyz/sdk@3.15.0 - @hyperlane-xyz/helloworld@3.15.0 - @hyperlane-xyz/utils@3.15.0 ## @hyperlane-xyz/ccip-server@3.15.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	6 months ago
Alex	51bfff683e	feat(sdk): XERC20 token adapter (#3911 ) ### Description `HypXERC20Adapter` that allows checking for mint and burn limits put in place on XERC20 contracts. ### Drive-by changes - Couple methods added to the `XERC20` interface - Corrects `HypXERC20Lockbox` and `HypXERC20` config during CLI deployments ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3851 ### Backward compatibility Yes ### Testing CLI testing.	6 months ago
Daniel Savu	12840964b9	chore: add all new chains to `KnownHyperlaneDomain` struct (#3960 ) ### Description So validators can be run with `--originChainName <chainname>`, like in the docs [here](https://docs.hyperlane.xyz/docs/operate/validators/run-validators#running-the-binary) <!-- 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
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>	6 months ago
github-actions[bot]	cb9c2aa571	Version Packages (#3910 ) This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @hyperlane-xyz/cli@3.14.0 ### Minor Changes - f4bbfcf08: AVS deployment on mainnet ### Patch Changes - @hyperlane-xyz/sdk@3.14.0 - @hyperlane-xyz/utils@3.14.0 ## @hyperlane-xyz/core@3.14.0 ### Patch Changes - a8a68f6f6: fix: make XERC20 and XERC20 Lockbox proxy-able - @hyperlane-xyz/utils@3.14.0 ## @hyperlane-xyz/helloworld@3.14.0 ### Patch Changes - Updated dependencies [`a8a68f6f6`] - @hyperlane-xyz/core@3.14.0 - @hyperlane-xyz/sdk@3.14.0 ## @hyperlane-xyz/sdk@3.14.0 ### Patch Changes - Updated dependencies [`a8a68f6f6`] - @hyperlane-xyz/core@3.14.0 - @hyperlane-xyz/utils@3.14.0 ## @hyperlane-xyz/utils@3.14.0 ## @hyperlane-xyz/infra@3.14.0 ### Patch Changes - @hyperlane-xyz/helloworld@3.14.0 - @hyperlane-xyz/sdk@3.14.0 - @hyperlane-xyz/utils@3.14.0 ## @hyperlane-xyz/ccip-server@3.14.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	6 months ago
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 -->	6 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>	6 months ago
Daniel Savu	5a31e7b5d3	chore: debug slow relayer startup (#3932 ) ### Description Opened this PR to debug slow relayer startup, but it actually looks like that's already been fixed by hook indexing. The requirement for fast startup is that the processor sees new messages and then one of the following happens: - (1) if the message is meant for an unknown domain, it drops it ([this log](`6d132b02a3/rust/agents/relayer/src/msg/processor.rs (L269)`)), otherwise - it forwards the message to the submitter, which then: - (2) adds it straight to the confirm queue because it's already been submitted ([here](`6d132b02a3/rust/agents/relayer/src/msg/pending_message.rs (L159)`)) - (3) successfully builds metadata ([here](`6d132b02a3/rust/agents/relayer/src/msg/op_submitter.rs (L231)`)) - (4) in some cases building metadata fails because the ism doesn't exist The relayer logs either of the four cases (in most cases (2), because we're running a second relayer for now). To be even more confident in fast startup, I ran a single relayer and restarted it. New messages were successfully processed according to one of the four cases above, and the prep queues didn't increase ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->	6 months ago
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>	6 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>	6 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	6 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>	6 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.	6 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>	6 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>	6 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

1 2 3 4 5 ...

2263 Commits (a109937f962ea60384e0845e11c678f08a1a8b66) All Branches Search

2263 Commits (a109937f962ea60384e0845e11c678f08a1a8b66)

All Branches