hyperlane-monorepo

Commit Graph

Author	SHA1	Message	Date
Trevor Porter	9ca2333bf0	feat: more app contexts (#4874 ) ### Description - Adds the endurance USDC warp deploy so it's a relayer app context - Adds Velodrome contracts, contracts were found from their private fork / in tg with them https://github.com/velodrome-finance/superchain-contracts-private/tree/main/deployment-addresses - Adds Aave contracts, contracts were found by poking around https://app.aave.com/governance/v3/proposal/?proposalId=92, which led to https://github.com/bgd-labs/aave-delivery-infrastructure?tab=readme-ov-file#deployed-addresses and seeing which contracts were sending/receiving messages in our explorer. They don't have a typical router setup -- some messaging is unidirectional. The sending address is more static than the receiving address, so I've set the matching list to be based off the sender to make configuration simpler. https://github.com/bgd-labs/aave-delivery-infrastructure?tab=readme-ov-file#deployed-addresses is the source of truth for these addresses ### Drive-by changes - Forces a warp ID to be picked in the warp monitor flow ### 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 days ago
Danil Nemirovsky	33b6f58418	fix: Use block slot instead of block height for Sealevel chains (#4862 ) ### Description Use block slot instead of block height for Sealevel chains ### Backward compatibility Yes ### Testing Manual run of validator against Solana mainnet Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>	6 days ago
Danil Nemirovsky	57346defe3	refactor: Refactor Hyperlane store for Scraper (#4855 ) ### Description Refactor Hyperlane store for Scraper. Just moved source code into submodules. ### Backward compatibility Yes ### Testing E2E test Ethereum and Sealevel --------- Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>	1 week ago
Danil Nemirovsky	25a927de3a	fix: Remove call to GetBlock for Sealevel for time being (#4858 ) ### Description Remove call to GetBlock for Sealevel for time being ### Related issues https://discord.com/channels/935678348330434570/935679524534911007/1306588981185740811 ### Backward compatibility Yes ### Testing E2E Test for Ethereum and Sealevel --------- Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>	1 week ago
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 -->	1 week ago
Trevor Porter	f76984baa5	fix: update warp monitors with latest registry to fix collateral value (#4849 ) ### Description - To include some fixes to the coinGeckoIds of warp routes recently merged into the registry ### Drive-by changes - made an agent metrics log `warn`, which helped debugging some recent issues - Update the eclipsemainnet owner in owners.ts, a mostly symbolic change as this isn't actually used in our tooling in infra ### 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
Danil Nemirovsky	408b975900	feat: Scraper populates gas payments for Sealevel (#4843 ) ### Description Scraper populates gas payments for Sealevel ### Related issues - Contributes into https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4272 ### Backward compatibility Yes ### Testing Manual run of Scraper --------- Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>	2 weeks ago
Danil Nemirovsky	5bebd6d0a3	feat: Scraper populates delivered messages for Sealevel (#4817 ) ### Description Scraper populates delivered messages for Sealevel ### Related issues - Contributes into https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4301 ### Backward compatibility Yes ### Testing Manual run of Scraper Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>	2 weeks ago
Danil Nemirovsky	8e3085ad0c	feat: Scraper report mailbox as recipient of transactions for Sealevel (#4813 ) ### Description Scraper reports mailbox as recipient of transactions for Sealevel ### Related issues - Contributes into https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4272 ### Backward compatibility Yes ### Testing Manual test of Scraper E2E tests for Ethereum and Sealevel --------- Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>	2 weeks ago
Paul Balaji	40d59a2f47	feat: deploy to abstracttestnet, treasuretopaz (#4839 ) ### Description - deploy to abstracttestnet, treasuretopaz - standard deployments from this branch - zksync deployments themselves done from https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4761 ### Drive-by changes - testnet igp - fix validator announce script, should only be skipping `lumia` ### 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 --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	2 weeks ago
Paul Balaji	bbb970a442	feat: nov 6 chain deploy batch (#4833 ) ### Description - redeploy to alephzeroevmmainnet chilizmainnet flowmainnet immutablezkevmmainnet metal polynomialfi rarichain rootstockmainnet superpositionmainnet - deploy to flame prom ### Drive-by changes - igp updates ### 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 --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	2 weeks ago
Danil Nemirovsky	8e50c2af21	feat: Remove unique chain id index from db migration script (#4834 ) ### Description Remove unique chain id index from db migration script ### Related issues - Contributes into https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4798 ### Backward compatibility Yes ### Testing Manual run of DB migration script --------- Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>	2 weeks ago
Paul Balaji	0264f709e4	feat: deploy to arcadiatestnet, alephzeroevmtestnet, inksepolia (#4827 ) ### Description feat: deploy to arcadiatestnet, alephzeroevmtestnet, inksepolia ### Drive-by changes - update agent configs ### 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 --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	2 weeks ago
Trevor Porter	e6f9d5c4fd	feat: add weETHs warp route, some drive-by cleanup (#4826 ) ### Description - Deploys weETHs between Ethereum and Eclipsemainnet - Removes all the warp route generation scripts in favor of a single one - Renames some things throughout infra to be closer to the canonical warp IDs (e.g. add all chain names, sort them, etc) - Removes a bunch of now unnecessary ts-ignores - Moves toward using router configs for non-EVM chains in the warp configs Waiting to merge https://github.com/hyperlane-xyz/hyperlane-registry/pull/362 before updating the registryrc in here so the warp config checker works ### 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 -->	2 weeks ago
Paul Balaji	e3b97c4555	feat: detangle chainId / domainId EVM assumptions (#4798 ) ### Description Detangle assumption that chainId == domainId for EVM chains. - required to support new domain IDs for sept26 chain deploy batch https://github.com/hyperlane-xyz/hyperlane-registry/pull/352 Domain IDs and Chain Names are still unique, but chainId is no longer guaranteed to be a unique identifier. - required to support shadow lumia (current deployment) + prod lumia (new deployment with different domain id) Touches: - evm core/ism/hook/warp modules - multiprovider + chain metadata manager - safe service - renaming `ChainNameOrId` to `ChainNameOrDomain` (where bulk of the diff comes from) ### Drive-by changes - ~~add name of a `chain` to `Annotated` types, since chain ID on a populated transaction is a looser tie to a chain than `domainId` or `chain`~~ - ~~simplify multiprovider.sendtransaction, since `chain` is provided with the annotated transaction~~ - ensure domainId is not optional in the chain metadata schema - requires registry fix https://github.com/hyperlane-xyz/hyperlane-registry/pull/357 - update ethers v5 json rpc submitter to require a `chain` as well ### Related issues - mostly redoes work from https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4599 - will have to be rechecked after zksync changes are also in ### Backward compatibility no ### Testing ci, manual --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	3 weeks ago
Daniel Savu	b72c881a93	feat: alert instead of crashing relayer when building cursors (#4811 ) ### Description - we should make sure there are no `unwrap`s outside a `tokio::spawn`, otherwise they'll take down the entire relayer. The offenders have so far been the indexing cursors, so this PR just logs an error and sets a new metric flag instead of panicking: `critical_error`, an `IntGauge` type because prometheus doesn't have boolean gauges. For now this is only used for origin chains, but I envision this as being set when a critical error occurs in the submitter too, in the future - before setting the flag, cursor instantiation is now retried 10 times (to avoid short lived RPC hiccups) ### Drive-by changes Removes usage of `Builder` derive macro in metric types, since they're not complex enough to warrant it ### Related issues ### Backward compatibility Yes ### Testing the existing e2e	3 weeks ago
Danil Nemirovsky	c064881727	feat: Scraper populates transaction fields for Solana (#4801 ) ### Description Scraper populates transaction fields for Solana ### Related issues - Contributes into https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4272 ### Backward compatibility Yes (configuration is updated) ### Testing Manual test of Scraper Run E2E tests for Ethereum and Solana --------- Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>	3 weeks ago
Trevor Porter	3660ebe47b	feat: update eclipse ISM (#4802 ) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### 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 -->	3 weeks ago
Daniel Savu	2f0495914a	feat: eclipse warp batch #2 (#4799 ) ### Description - ORCA (eclipse <> solana) - WBTC (ethereum <> eclipse) - USDT (ethereum <> eclipse <> solana)	3 weeks ago
Danil Nemirovsky	38bd1ae49f	feat: Scraper stores input data from Ethereum transactions (#4794 ) ### Description Scraper stores input data from Ethereum transactions ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4778 ### Backward compatibility Yes ### Testing Manual run of Scraper against 1. local database 2. database restored from backup of production database Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>	3 weeks ago
IvanPsurtcev	21a0cf964f	fix: GCS folder support (#4652 ) ### Description This PR fixes the problem of this issue: [https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4449](url) The change was only in the gcs_storage.rs file. Slightly tweaked methods so that you can write files to a specified folder in the terminal. When trying to run a validator specifying checkpointSyncer settings for GCS: `--checkpointSyncer.type gcs --checkpointSyncer.bucket an-s3-signatures-repository --checkpointSyncer.folder atletaolympia` ``` Building provider without signer thread 'main' panicked at 'Failed to report agent metadata: error validating bucket name an-s3-signatures-repository/atletaolympia Caused by: Character '/' @ 27 is not allowed Location: hyperlane-base/src/types/gcs_storage.rs:181:9', agents/validator/src/validator.rs:178:14 ``` To solve this problem I added the `folder: Option<String>` field to the GcsStorageClient structure, I also added bucket and folder processing to the impl CheckpointSyncer, GcsStorageClientBuilder methods	3 weeks ago
Danil Nemirovsky	c87cfbd512	feat: Scrape Sealevel dispatched messages (#4776 ) ### Description Scraper is able to index dispatch messages: 1. Blocks are stored into database 2. Transactions are stored into database (need population of all fields) 3. Dispatched messages are stored into database ### Drive-by changes Initial indexing of delivered messages (so that Scraper does not crush) ### Related issues - Contributes into https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4272 ### Backward compatibility Yes (Solana-like chains should not be enabled for Scraper) ### Testing Manual run of Scraper E2E Tests --------- Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>	4 weeks ago
Daniel Savu	8dbc2e636e	fix: another sealevel unit test flake (#4784 ) Applies the same fix from https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4655 to a flake that showed up in this PRs CI: https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4693#event-15004545304	4 weeks ago
Mantas-M	fc82b30a2e	feat: Refactor Relayer Retry Server (#4693 ) ### Description Refactor of the Relayer Retry Server to utilize matching lists. This allows for a single POST request to be able to retry a wide range of messages. Since a matching list is used it is now possible to retry messages depending on: - Message Id - Origin Domain - Destination Domain - Recipient Address - Sender Address ## Example Instead of the old request format ``` GET http://127.0.0.1:60843/message_retry?destination_domain=42 GET http://127.0.0.1:60843/message_retry?message_id=0x46910b1329ee53c86a023b322e9ca1c17e5f9f0bee789c77b0abced0a173d714 ``` The new one should be used ``` POST http://127.0.0.1:60843/message_retry ``` With a JSON body like so: ``` [{"messageid": "", "origindomain": "", "senderaddress": "", "destinationdomain": "", "recipientaddress": "*"}] ``` Retry params can be both specific values and wildcards. ### Drive-by changes - Moved `MockPendingOperation` to `hyperlane-test` - Moved certain test utils for the relayer server to `hyperlane-test` - Added functions to retrieve recipient and sender address from the `PendingOperation` - Added a `message_id` to the `MatchingList` struct to allow retries by message id - Removed `MessageRetryRequest` enum since it was no longer in use ### Related issues Fixes #3571 #4079 ### Backward compatibility Yes ### Testing Unit tests	4 weeks ago
Mantas-M	8ff194dc47	feat: Cosmos RPC client supporting fallback rpcs (#4752 ) ### Description Added fallback functionality to the Cosmos RPC client ### Drive-by changes N/A ### Related issues - Fixes #3425 ### Backward compatibility Yes ### Testing Unit tests already in place, no additional added, as the generic CosmosFallbackProvider which is used is already tested	4 weeks ago
Paul Balaji	d9505ab585	feat: oct 25 deployment batch (#4766 ) ### Description - feat: oct 25 deployment batch - apechain, arbitrumnova, b3, fantom, gravity, harmony, kaia, morph, orderly, snaxchain - deployed as normal - zeronetwork, zksync - deployed from special zksync branch containing txfusion's changes + latest `main` pulled in - https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4761 ### Drive-by changes - igp updates ### Related issues n/a ### Backward compatibility yes ### Testing manual using local CLI from this branch, no tx fusion changes required for hyperlane send or self-relay to work	4 weeks ago
Daniel Savu	1bd8e3e384	feat: Stride <> Eclipse TIA and stTIA (#4749 ) ### 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 -->	4 weeks ago
Danil Nemirovsky	14e4719f00	feat: Use H512 as transaction hash in HyperlaneProvider and Scraper (#4759 ) ### Description Use H512 as transaction hash in HyperlaneProvider and Scraper. ### Related issues - Contributes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4272 ### Backward compatibility Yes ### Testing Manual run of Scraper for Ethereum and Neutron --------- Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>	4 weeks ago
Trevor Porter	89c60ab9c0	feat: update Stride IGP to our own, temporarily whitelist our Stride deployment (#4748 ) ### Description - We have an IGP on Stride now. We expect not to fully index this till at least Friday - so for now we just whitelist the messages we care about. ### 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: Daniel Savu <23065004+daniel-savu@users.noreply.github.com>	1 month ago
Trevor Porter	15db5c112d	chore: update Eclipse validator sets to include Stride, minor cleanup (#4747 ) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### 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 -->	1 month ago
Danil Nemirovsky	ffbe1dd82e	feat: Make HyperlaneProvider to request block by height, not by hash (#4727 ) ### Description Make HyperlaneProvider to request block by height, not by hash. Since it is hard to find a block by hash for Solana, we switch to use block height. We have to do it for all type of chains since we need to change signature of chain-agnostic method ### Drive-by changes * Small method rename ### Related issues - Contributes into https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4272 ### Backward compatibility Yes ### Testing Manual run of Scraper for Ethereum and Neutron chains. --------- Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>	1 month ago
Paul Balaji	a64af8be9a	fix: revert chiliz reorg period back to 9 (#4744 ) ### Description fix: revert chiliz reorg period back to 9 ### Drive-by changes na ### Related issues na ### Backward compatibility ye ### Testing relayer sad times - [context](https://discord.com/channels/935678348330434570/1298963431743029359/1298965217757102100)	1 month ago
Paul Balaji	29bf1d8c73	chore: set finalized reorgPeriod (#4741 ) ### Description - chore: set finalized reorgPeriod - update reorg period ### Drive-by changes na ### Related issues na ### Backward compatibility agents are already updated ### Testing manual Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	1 month ago
Trevor Porter	f9f0ece7c4	feat: add zkSync enum variant to HyperlaneDomainTechnicalStack (#4740 ) ### Description To match the new TS schema ### 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 -->	1 month ago
Paul Balaji	7f3e0669d2	feat: add stride to relayed chains (#4716 ) ### Description - feat: add stride to relayer - feat: add stride to scraper ### Drive-by changes - fix filtering non-evm addresses in appFromAddressesMapHelper - fallback to manual `yarn install` in `yarn-build-with-cache` action - fix bug in app governor to make inevm env-test pass ### Related issues na ### Backward compatibility yes ### Testing manual --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	1 month ago
Daniel Savu	5fc442b97f	chore: add sleep log in `fetch_logs_with_cursor` (#4734 ) ### 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 -->	1 month ago
Daniel Savu	937392b61d	chore(evm): optimize block number fetching (#4736 ) ### Description Fix for leftover [comment](https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4629#discussion_r1811084234) from https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4629 ### 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 -->	1 month ago
Alexander Pastushenka	c3e9268f1e	feat: Add block tag support in `reorgPeriod` parameter (#4629 ) ### Description <!-- What's included in this PR? --> Allows setting an arbitrary string in `reorgPeriod`, which is used as a block tag to get the finalized block. Currently, only the Ethereum connector supports this feature with the following tags: - finalized - safe - pending - latest - earliest This is currently useful for EVM-compatible chains that don't have a fixed reorganization period, but instead rely on the block tag `Finalized` to indicate finality. For such chains, you should set `reorgPeriod` to `finalized` instead of a number of blocks. ### 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 --> Yes ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: Daniel Savu <23065004+daniel-savu@users.noreply.github.com>	1 month ago
Trevor Porter	013d3211c0	fix: use hyp_message as tracing field instead of message (#4721 ) ### Description https://docs.rs/tracing/latest/tracing/#shorthand-macros > unlike other fields, `message`'s shorthand initialization is just the string itself. When using tracing::info etc, passing in an explicit `message` field takes precedence over the message string that's supplied as the second positional param! So we end up in situations where we see `message: HyperlaneMessage { id: ....` instead of the log message we want! e.g. https://cloudlogging.app.goo.gl/Nr8Q5W5KviD6sT8W9 Open to other field names, like `msg` or something, but this felt explicit ### 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 -->	1 month ago
Danil Nemirovsky	5300230c44	refactor: Make Sealevel RPC client more functional (#4699 ) ### Description Make Sealevel RPC client more functional. Move some methods and error mapping into RPC client. ### Backward compatibility Yes ### Testing E2E Ethereum + Sealevel test --------- Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>	1 month ago
Danil Nemirovsky	9c0c4bbe21	feat: Add logging block hash (#4707 ) ### Description Add logging block hash so that we have both block height and block hash. When Scraper will report that it cannot retrieve block by hash, we'll be able to find its block height. ### Backward compatibility Yes ### Testing Run Scraper locally to see the log message --------- Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>	1 month ago
Paul Balaji	3f48f5a8ed	chore: add scroll gasPrice override (#4701 ) ### Description chore: add back the scroll gasPrice override relayer's unaffected because we override that to 0.8 gwei ### Drive-by changes update agent config ### Related issues key funder :'( ### Backward compatibility yes ### Testing manual? --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	1 month ago
Daniel Savu	777ef084a6	fix: queue length metric bug (#4691 ) ### Description Fix for https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4689, where `Dropped` status operations weren't decremented from the metric. I noticed there's still a small difference on a handful of chains, such as celo, where even if Dropped ones are considered, the prep queue metric reports an extra 53 ops compared to the actual queue. Could be that I manually miscounted, I expect releasing this will be a big improvement anyway. ### Backward compatibility Yes ### Testing No, just checked all places where we `.pop_many` but don't `push`	1 month ago
Daniel Savu	efd438f9b2	chore: fix queue metric juggedness (#4689 ) ### Description See https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4068 for the problem description. In this fix, whenever an operation is moved from one queue to another, its metric count is decremented from the old queue and incremented for the new one. My initial implementation approach was to update these metrics inside `queue.push(op)`, but the metrics for the operation's previous queue aren't accessible there. #4068 suggests updating them in `op.set_status`, which can't be done for the same reason, even if `op` has a pointer to the current queue's metric internally. So the fix I went for does store a pointer to the current queue metric internally in `op`, but also adds a new `op.set_status_and_update_metrics(status, new_queue_metric)` method, which must be used if the queue metrics are to be correctly calculated. This works well except for when ops are removed from the confirm queue, because in the absence of a call to `set_status_and_update_metrics`, no metric decrementing is done. I considered using the `Drop` trait to decrement, but it'd have to be implemented individually for each `PendingOperation` type, which isn't very maintainable. I ended up decrementing the metric in `confirm_operation`, which is called for both batches and single submissions and, of course, all implementations of `PendingOperation`. Here's a screenshot of my local grafana server showing no jaggedness in the e2e run, with prometheus configured to scrape every 2s: ![Screenshot 2024-10-15 at 17 26 56](https://github.com/user-attachments/assets/26004e0e-2ccf-4cec-aa23-ee2d032df25a) ### Drive-by changes Adds the `prepare_queue` arg of `submit_single_operation` to the `instrument(skip(...))` list so it no longer pollutes logs. ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4068 ### Backward compatibility Yes ### Testing Manually, by checking the queue length metric of an e2e run in grafana	1 month ago
Paul Balaji	9382658db3	fix: update HyperlaneDomainTechnicalStack with latest stacks (#4688 ) ### Description fix: update HyperlaneDomainTechnicalStack with latest stacks We added new technical stacks, and updated these in registry, but did not update the enum in the agents. this caused a hard failure to load the configs when we tried deploying to prod. Note: we're omiting `zksync` because that is soon to be moved from a "tech stack" into a "protocol type", and we have no chains in registry with a `zksync` technical stack configured yet anyway. ### Drive-by changes update existing list of mainnets with "other" technical stack. can't just remove them right now because we have to ensure every value in the enum is mapped ### Related issues na ### Backward compatibility yes ### Testing todo: fix e2e	1 month ago
Paul Balaji	c08d842adf	feat: implement reorg audit remediations (#4682 ) ### Description Bump up .registryrc and update agent configs with updated chain metadata including: - reorg periods - technical stack Updates originally made in https://github.com/hyperlane-xyz/hyperlane-registry/pull/276 Relies on `objMerge` to be fixed https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4678 ### Drive-by changes - remove extraneous overrides + bring exiting relayer env vars into config - so it's in the image build directly, and we minimise break-glass-in-case-of-emergency overrides to the stateful set - ensure txOverrides are only included if defined in infra or registry - ensure we delete txo verrides from the read-in config, before merging with the generated config ### Related issues na ### Backward compatibility yes ### Testing na	1 month ago
Danil Nemirovsky	110d9d8877	feat: Record transaction with non-native fees (#4683 ) ### Description Record transaction with non-native fees. Fees will be recorded as a huge number: max value of unsigned 256-bit long integer. ### Backward compatibility Yes ### Testing Manual testing of Scraper Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>	1 month ago
Paul Balaji	7d7bcc1a30	feat: deploy to flow, metall2, polynomial (#4669 ) ### Description - deploy to flow, metall2, polynomial ### Drive-by changes na ### Related issues na ### Backward compatibility yes ### Testing manual ![image](https://github.com/user-attachments/assets/1d94e332-a64a-472d-878b-140865423a5a) --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	1 month ago
Danil Nemirovsky	470e53bb76	feat: Add support for flow from Celestia (#4668 ) ### Description Add support for flow from Celestia ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4646 ### Backward compatibility Yes ### Testing Local run of Scraper Check that transaction and messages can be parsed --------- Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>	1 month ago

1 2 3 4 5 ...

983 Commits (23a2679bbee23ce44d9fcda22f99df618f8a34e0)