3 Commits (3ce70725ee62069272f6de51987fbc8a4b1ee7d6)

Author	SHA1	Message	Date
Trevor Porter	4f8245a1ed	chore: apply 10% gas buffer for Arbitrum Nitro txs, some drivebys (#4854) ... ### Description - Applies a 10% buffer to arbitrum nitro txs, see https://discord.com/channels/935678348330434570/1306264065110310987 for context ### Drive-by changes - Some drive-bys -- imo the Display impl of HyperlaneMessage isn't useful at all and should be the same as Debug (or we should stop using the Display impl) - Updates a sealevel comment that was inaccurate as flagged by some partners - makes sure that relayer pods update when there's a configmap change ### 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 -->	2 weeks ago
Trevor Porter	e1c6eef8ab	feat: relayer app contexts use warp route artifacts from the registry (#4845) ... ### Description This PR aims to solve 2 problems: forgetting to add warp routes as app contexts in the relayer, and deduplicating artifacts that live in infra and the registry - Removes a bunch of the duplicated warp route artifacts in infra, in favor of getting them from the registry - Now all WarpRouteIds defined in infra will be auto-populated into the mainnet3 relayers as app contexts, with the label as the warp route ID - This significantly increased the size of the metric app context configuration, which was previously supplied as an env var to the relayers. This caused the env var size limit to be hit. As a workaround, larger configuration strings are now moved into a configmap that will be read in as a JSON by the relayer. I intentionally kept some of the configs as env vars, e.g. the relayChains, because this is much more ergonomic to change on the fly and many of us have operational muscle memory around this that I didn't want to break. - Note one consequence of this is that merkly's ETH app is prone to running out of ETH and causing prep queues to rise. Because of this, I'll ignore merkly eth from our high urgency alert ### Drive-by changes - There are a few places we were whitelisting warp routes in the gas config that I've now removed. From what I can tell none of these are necessary anymore as they were intended to be temporary workarounds. - Updated the addresses for merkly from here https://minter.merkly.com/hyperlane/docs ### 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 -->	2 weeks ago
Mantas-M	096aeff13e	feat: Splitting `rust` workspace into `main` and `sealevel` (#4438) ... ### Description The single rust workspace has been split into 2 workspaces. The sealevel workspace includes the contents of the previous `sealevel` folder and the main workspace includes everything else. The workspaces differ in rust versions as the sealevel has the old one to ensure compatability, the main workspace has and updated `rustc` version of `1.80.1`. Some dependencies and sub-dependencies have been locked in versions of the old pre-split workspace to ensure no breaking code changes. The rust CI workflow has been updated to include both workspaces in the tests. ### Drive-by changes N/A ### Related issues Relates to https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4361 ### Backward compatibility No. ### Testing Rust Unit tests from the CI	3 months ago