Merge upstream main ef46219ab (sync to ef46219ab from 5b6c65da)#197
Merged
Merge upstream main ef46219ab (sync to ef46219ab from 5b6c65da)#197
Conversation
### Description This PR adds a check to `warp check` CLI verifying that decimals are consistent and have the correct scale if not. ### Related issues hyperlane-xyz#5173 ### Backward compatibility Yes ### Testing Two E2E tests checking for missing and incorrect scale, when decimals are not consistent.
### Description This PR extends `wfragJTO` with SonicSVM. ### Drive-by changes N/A ### Backward compatibility Yes ### Testing N/A
### Description This PR extends `wfragSOL` with SonicSVM. ### Drive-by changes N/A ### Backward compatibility Yes ### Testing N/A
### Description This PR adds `wfragBTC` token config and program IDs. ### Related PRs [Registry PR](hyperlane-xyz/hyperlane-registry#932) ### Backward compatibility Yes ### Testing N/A
### Description This PR adds `adraSOL` token config and program IDs. ### Drive-by changes N/A ### Related PRs hyperlane-xyz/hyperlane-registry#936 ### Backward compatibility Yes ### Testing N/A
### Description - To include hyperlane-xyz#6470 - Only deployed Starknet - Updates some Velo app context addresses ### 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 -->
…xyz#6480) ### Description - Some context here https://hyperlaneworkspace.slack.com/archives/C08HRKU6HE0/p1749231858340619 as we started monitoring some new contracts of theirs ### 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 -->
hyperlane-xyz#6468) ### Description * Rename PendingInclusion into Pending * Rename TransactionId into TransactionUuid * Rename PayloadId into PayloadUuid ### Backward compatibility Yes ### Testing Current tests pass --------- Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>
### Description - Changes `EthereumAdapter` so it can more easily be mocked - Creates a new tests module (`./lander/src/tests/ethereum`) where a test for the inclusion stage is added. The test successfully gets a transaction processed, which requires mocking every method in the `EvmProviderForLander` trait. - The new test setup serves as scaffolding for reproducing all submission incidents we've listed in the Lander design doc Fixes https://linear.app/hyperlane-xyz/issue/ENG-1710/submitter-evm-integration-testing-setup ### Drive-by changes - there is some code shift, as tests are moved from `dispatcher/stages/inclusion_stage.rs` into their own file - renames two methods each on the TransactionDb and PayloadDb traits, because there used to be a naming clash which prevents mocking both traits on the same struct at the same time - small and inconsequential (you can ignore): slightly changes the mocking setup for the Lander `Db` - now we use mockall and instead of storing the state inside the Db struct, we pass it as an arcmutex to the mocked methods ### Backward compatibility Yes ### Testing Unit tests
…ne-xyz#6491) ### Description chore(infra): normalise before checking warp config equality - so that we don't flag up mismatch in ordering between infra/registry ### 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 tested with hyperlane-xyz#6358 - https://github.com/hyperlane-xyz/hyperlane-monorepo/actions/runs/15539520388/job/43747085969?pr=6358
…-xyz#6489) ### Description Set the same reorg period on Hyperliquid EVM Testnet as on Hyperliquid Mainnet ### Backward compatibility Yes ### Testing None --------- Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com> Co-authored-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>
…perlane-xyz#6490) ### Description For safety, we want to make sure that each contract only has one initializer.
### Description Using `delete` does not delete the inner mapping (`_indexes`) in `EnumerableSet.Set`. See OpenZeppelin v4.9 [here](https://github.com/OpenZeppelin/openzeppelin-contracts/blob/bd325d56b4c62c9c5c1aff048c37c6bb18ac0290/contracts/utils/structs/EnumerableSet.sol#L56)
…yz#6487) ### Description > In PR hyperlane-xyz#6471, the metadata of the OptimismPortal.WithdrawalTransaction was modified to include two Hyperlane message IDs (proveMessageId and finalizeMessageId). However, this patch allows an attacker to create a separate OP to L1 withdrawal transaction with the same pair of message IDs in the metadata, and execute OPL2ToL1CcipReadIsm.verify() using that forged metadata. In other words, it is possible to use the metadata of a different withdrawal transaction instead of the legitimate one. To address this issue, OPL2ToL1CcipReadIsm.verify() should verify that the _tx.sender() from IOptimismPortal.WithdrawalTransaction matches the sender() of the _message Fixes this issue by enforcing message sender matches tx sender. ### Backward compatibility No, requires new deployments ### Testing Unit Tests
### Description > In hyperlane-xyz#6386 PR, the patch still allows a 1:N mapping between CCTP messages and Hyperlane messages. For example, verify() does not check whether the length of _hyperlaneMessage.body().metadata() is exactly 8 bytes. If it is longer than 8 bytes, it will automatically be truncated to bytes8, discarding the trailing bytes. This allows malformed metadata values to pass through verify() as if they were valid. Additionally, other parts of _hyperlaneMessage.body() such as amount, recipient, and even _hyperlaneMessage.sender() can be manipulated. Fixes this issue by checking all fields match. ### Backward compatibility Requires new CCTP deploy ### Testing Unit Tests
### Description This PR adds the option to configure remote routers/gas and rebalancing bridges using the chain name instead of the domain id in the config ### Drive-by changes - Fixes all the failing e2e tests in the CLI - Adds support for the ICA router ISM to fix the tests ### Related issues - ### Backward compatibility - Yes ### Testing - E2E - Manual --------- Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>
### Description feat: extend ousdt to bob+hsk - also add ccip token pools for eth, celo, base, op, sonic ### Drive-by changes - add try-catch to export-warp-configs - add option to export configs for specific warp ids - fix bug in xerc20 utils that prevented two bridges with the same address on separate chains to be updated correctly - add script to generate ousdt submitter config - add script to prune the warp route connections from the warp config - could be extracted out in the future if there's wider usage - support parsing txs to ManagedLockboxes (stopgap) - rename to `oUSDT/production` and `oUSDT/staging` ### Related issues hyperlane-xyz/hyperlane-registry#895 ### 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 -->
…6496) ### Backward compatibility Yes ### Testing Manual <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **Chores** - Updated Docker image versions for relayer and scraper components to the latest releases in the testnet environment. <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>
### Description Updates the SVM IGP config and adds the missing soon <> eclipse connection ### Drive-by changes - Updated the rust cli to add a command to set the remote gas on a token ### Related issues - None ### Backward compatibility - YES ### Testing - Manual <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Added a new CLI subcommand to set destination gas configurations for tokens. - Introduced configuration files for mainnet environments, including program ID mappings and token settings for multiple blockchains. - **Refactor** - Improved instruction handling for enrolling remote routers in the CLI tool. - **Chores** - Added JSON files to define program IDs and token configurations for kySOL-kyros routes on mainnet. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Sebastiano Faiella <xeno097@Sebastianos-MacBook-Pro.local>
### Description add `app_context` to `hyperlane_operations_processed_count` ### Related issues - fixes https://linear.app/hyperlane-xyz/issue/ENG-1667/add-app-context-to-the-relayers-operations-processed-count-metric-then
Co-authored-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>
hyperlane-xyz#6773) Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>
Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>
Co-authored-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>
Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…erlane-xyz#6788) Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>
danwt
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Drive-by changes
Related issues
Backward compatibility
Testing