hyperlane-monorepo

Commit Graph

Author	SHA1	Message	Date
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>	2 months 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>	2 months 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`	2 months 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	2 months 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	2 months 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	2 months 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>	2 months 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>	2 months 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>	2 months ago
Paul Balaji	46044a2e98	feat: deploy to odysseytestnet (#4670 ) ### Description feat: deploy to odysseytestnet ### Drive-by changes na ### Related issues na ### Backward compatibility yes ### Testing manual	2 months ago
Paul Balaji	adedb3db8e	feat: add arcadiatestnet, sonictestnet, unichaintestnet (#4665 ) ### Description feat: add arcadiatestnet, sonictestnet, unichaintestnet ### Drive-by changes testnet igp ### Related issues n/a ### Backward compatibility yes ### Testing manual	2 months ago
Danil Nemirovsky	bb82b1cc01	feat: Store as much as possible from every range (#4660 ) ### Description Currently, if Scraper cannot fetch and parse a block or a transaction, it will fail the whole chunk of logs. It means that a transaction which can be fetched and parsed, but happens to be in the same chunk as unparseable transaction, won't be inserted into database. This PR fixes it. Scraper will do its best to insert as many as possible blocks and transactions into database from the chunk. ### Related issues https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4632 ### Backward compatibility Yes ### Testing Local run of E2E tests. Local run of Scraper --------- Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>	2 months ago
Paul Balaji	e89f9e35d4	chore: update registry to v4.7.0 (#4662 ) ### Description chore: update registry to v4.7.0 ### Drive-by changes agent config updates, because they're derived from registry ### Related issues n/a ### Backward compatibility yes ### Testing n/a --------- Co-authored-by: Daniel Savu <23065004+daniel-savu@users.noreply.github.com>	2 months ago
Paul Balaji	3254472e02	feat: sept 30 mainnet batch (#4613 ) ### Description Deploy to immutablezkevm rari rootstock alephzeroevm chiliz lumia superposition ### Drive-by changes - fix igp defaults - helper for updating agent configs + running prettier ### Related issues na ### Backward compatibility ye ### Testing manual	2 months ago
Daniel Savu	ad4d61f962	chore: agave 2.x validator in sealevel e2e (#4643 ) ### Description Solana Mainnet is hard forking in 1-2 weeks and one of the RPC methods we were using will be removed. This PR updates that RPC and runs e2e with an agave `v2.x` network to ensure compatibility. As in the [svm warp route guide](https://docs.hyperlane.xyz/docs/guides/deploy-svm-warp-route), we still use `v1.14.x` to compile programs. More details: - `v2.0` migration [guide](https://github.com/anza-xyz/agave/wiki/Agave-v2.0-Transition-Guide) - `v2.0` release [schedule](https://github.com/anza-xyz/agave/wiki/v2.0-Release-Schedule) - `solana` to `agave` client transition [guide](https://github.com/anza-xyz/agave/wiki/Agave-Transition) ### Drive-by changes The solana cli installer logic in e2e is parameterized with `version` and `url` ### Backward compatibility Yes - no dependency upgrade was needed to switch to the new rpc method ### Testing E2E for general network compatiblity. The Jito submission retry logic (where the new rpc is used) wasn't tested - I'm confident it works but this is non-critical, as failed submission will eventually end up in the prep queue again	2 months ago
Danil Nemirovsky	e490e77445	feat: Generate Cosmos address for Injective (#4618 ) ### Description Injective uses different logic compared to Neutron and Osmosis to generate account addresses from public key. It is implemented in this PR so that sender address is correctly generated from signer info of transaction. Depending on the type of public key communicated in the transaction, we shall generate either Bitcoin-like or Ethereum-like address for Injective. We can also specify the type of account id for the signer. Bitcoin-like will be chosen by default, so, we don't need to change the configuration of Relayer. ### Drive-by changes Made some errors to be warnings. We'll add metrics to measure how frequent the issues are and decide how to fix them: 1. transaction contains multiple contract execution messages 2. transaction contains fees in unsupported denominations Made Scraper to refrain from recording transaction which it cannot parse properly. ### Backward compatibility Yes ### Testing Added unit tests Manual testing with Injective blockchain --------- Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>	2 months ago
Daniel Savu	7dccf80b57	feat: do not start up validator if fraud was reported (#4627 ) ### Description Builds on top of https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4587 Adds a check in the `CheckpointSubmitter` builder which emits a panic if a reorg flag was posted, since this potentially signals fraud ### Drive-by changes `CheckpointSubmitter::build` was made private, so any use of it is now replaced by the `build_and_submit` flow ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility Yes ### Testing Unit Tests - which is enough as long as `CheckpointSubmitter::build` is kept private	2 months ago
Daniel Savu	8809f37271	feat: checkpoint syncer fraud flag (#4587 ) Upon detection of a merkle root mismatch between the local merkle tree (built from indexed events) and the onchain one, reorg diagnostic data is posted to checkpoint storage. This PR focuses on the submitter logic and leaves two things for a follow up PR: - adding logic to not spin up the validator if a fraud flag has been posted - integration testing with S3 and GCP I assume rolling out to validators will happen after the follow up PR, but running with logic from this PR will already mean the reorg diagnostic flag is posted to S3 (though not tested).	2 months ago
Daniel Savu	e2b5a4c785	feat: HyperlaneDb trait (#4609 ) ### Description Defines a `HyperlaneDb` trait for use in the validator submitter, so a mock can be passed in to simulate indexed data from reorged state. Although the `HyperlaneDb` trait can't be `Clone` to be object safe, as long as we use `Arc`s everywhere, all will be ok. Eventually the aim is to replace all direct usage of `HyperlaneRocksDb` with `Arc<dyn HyperlaneDb>`.	2 months ago
Daniel Savu	4f92871c2b	feat: include `id` field in `list_operations` endpoint (#4610 ) ### Description The `id` field was missing if the serialized `PendingOperation` was a `PendingMessage`, which made it hard to look up the message in relayer logs or the explorer. This PR takes advantage of `id()` being a required method on `PendingOperation` to derive and display the ID as part of endpoint logic. ### Testing Unit Tests	2 months ago
Paul Balaji	3c819c777e	revert: "feat: Generate cosmos account addresses for Injective" (#4615 ) Reverts hyperlane-xyz/hyperlane-monorepo#4576 context: https://discord.com/channels/935678348330434570/1291354470730436680/1291357041624875010 > The problem is that Injective supports both "normal cosmos" signing with the bitcoin style address, and also ethereum style addresses. They disambiguate depending on the type of the pubkey that's signed in the tx > The relayer signs things using a bitcoin style address on Injective bc this was easier than making code changes to have it do ethereum-style (which isn't supported easily out of the box with the cosmos libs we use) > So we want the relayer account balance metric to look at the bitcoin-style address relating to our relayer key, not the Ethereum-style one at least this is the theory behind what happened	2 months ago
Danil Nemirovsky	22871425d6	feat: Dispatch messages before and after start of the agents (#4604 ) ### Description Dispatch messages before and after start of the agents so that we test both forward and backward looking sequence based indexers. ### Related issues - Successfully scrape Cosmos chains in e2e test #3355 ### Backward compatibility Yes ### Testing - E2E Cosmos Test - Manual check on E2E Cosmos Test logs --------- Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>	2 months ago
Paul Balaji	330b0580e2	chore: enable citreatestnet + testnet igp fixes (#4583 ) chore: enable citreatestnet + igp fixes - enable citreatestnet - set chunk size to 999 - flat price for testnet tokens - avoids problem where chains that have a non-eth native gas token end up paying way higher IGP fees than required	2 months ago
Danil Nemirovsky	6e787a9b39	feat: Generate cosmos account addresses for Injective (#4576 ) ### Description Injective uses different logic on generating account addresses from public key. It is implemented in this PR so that sender address is correctly generated from signer info of transaction. ### Backward compatibility Yes ### Testing Added unit tests Manual testing with Injective blockchain --------- Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>	2 months ago
Daniel Savu	bf53f087c3	fix(relayer): dry-run before sending txs (#4565 ) ### Description Fixes a bug in the individual submission logic. There is a race condition where a message can become undeliverable between when it was simulated in the `prepare` step and when it's actually submitted. ### Context The bug was discovered as part of batched messages but affects chains without batching too. - when delivery fails inside batch submission simulation, we fall back to individual submission - individual submission doesn't simulate the tx outcome, and instead just submits directly - this is wrong, because the batch may cause messages to become undeliverable for long periods of time (such as when a mint cap is reached) - I believe simulation used to happen in the individual submission step, but we switched to using the already computed gas estimate from the IGP check in the `prepare` step, to save an RPC call - this results in senders being charged from their IGP allowance unnecessarily, and messages becoming undeliverable due to insufficient gas The correct flow requires three delivery simulations: 1. in the `prepare` step, to estimate gas and check the IGP policy 2. in the batch submission logic, to filter messages that are made invalid by earlier messages in the batch 3. right before submitting again, in case the batch caused the message to not be deliverable ### Solution Dry-run right before submitting an operation, and if it fails send it back to the prep queue	2 months ago
Paul Balaji	642a349b7f	feat: sep 24 testnet deployments (#4574 ) feat: add more testnets - `berabartio` - `camptestnet` - `formtestnet` - `soneiumtestnet` - `suavetoliman` if RPCs get sorted: - `citreatestnet` - `hyperliquidevmtestnet`	2 months ago
Roman V	8fee6aedc5	fix: GCS correctly splitting storage location into bucket and folder (if present) (#4539 ) ### Description Previously Checkpoint Syncer wasn't correctly parsing the storage location string. If no folder was provided, it treated the object name as folder, e.g. reading `gs://bucket-name/gcsLatestIndexKey` initialized StorageClient with bucket `bucket-name` and folder `gcsLatestIndexKey`. This was due to incorrect logic for splitting the string by `/` that expected a folder to be present. In this PR I fixed this logic, treating a location with only one `/` as _bucket/object_ and with two `/`s as _bucket/folder/object_. ### Backward compatibility Yes ### Testing Manual --------- Co-authored-by: Trevor Porter <tkporter4@gmail.com>	2 months ago
Paul Balaji	ba15abef17	feat: revamp testnet4 gasoracle/igp calculations (#4562 ) looking to resolve https://github.com/hyperlane-xyz/issues/issues/1374 more longer term feat: revamp testnet4 gasoracle/igp calculations - update print-gas-prices script to support testnets - update print-token-prices script to support testnets (requires https://github.com/hyperlane-xyz/hyperlane-registry/pull/228) - remove the common/rare/mythic nomenclature, use mainnet prices - refactor igp utils, reuse across both mainnet3 + testnet4	2 months ago
Danil Nemirovsky	5cb1787044	feat: E2E Test Cosmos Scraper Invariant (#4536 ) ### Description - Add metrics based Scraper invariant into E2E Test for Cosmos - Report error if transaction contains multiple contract execution messages - Report error if fee are expressed in unsupported denomination ### Related issues - Successfully scrape Cosmos chains in e2e test #3355 ### Backward compatibility Yes ### Testing E2E Testing --------- Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>	2 months ago
Daniel Savu	4508b4fed1	fix: don't reuse prefix key in relayer (#4560 ) ### Description This PR fixes a bug @tkporter flagged, which would cause agents to reindex every igp payment on restart (but luckily with no impact on message processing). Unfortunately the same DB prefix key was used to store different items: `gas_payment_by_sequence` and `gas_payment_block_by_sequence`, with the latter overwriting the former. Sequence indexing relies on `gas_payment_by_sequence` to know whether a certain payment was already indexed - if not, it queries an RPC for it and stores it in the db. But because `gas_payment_by_sequence` would get overwritten and thus corrupted, checking whether a certain `gas_payment_by_sequence` is already in the db would fail with a decoding error, and because errors are treated as if the payment just wasn't indexed yet, the RPC call would be made again. Fortunately no migration is required, since just re-running the relayer will cause it to overwrite the old corrupted entries with correct ones, and would also create new prefix entries for the igp blocks.	2 months ago
Daniel Savu	0744137f38	feat: v3 Jito submission (#3429 ) (#4528 ) Ports this v2 fix to v3 https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3434 originally authored by @tkporter --------- Co-authored-by: Trevor Porter <tkporter4@gmail.com> Co-authored-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	2 months ago
Daniel Savu	35d4503b94	chore: new svm warp route artifacts (#4531 ) ### 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 --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>	2 months ago
Daniel Savu	b872d635e1	chore: include txids in indexing logs; add vscode config for rust-ana… (#4537 ) - adds support for rust-analyzer with the new workspace split - includes txids in agent indexing logs, to more easily link message_ids to their txid. @Mo-Hussain and I spent quite some time today trying to find the corresponding txid	2 months ago
Danil Nemirovsky	4151317b00	feat: Fetch logs by transaction hash (#4510 ) ### Description Cosmos indexers now can fetch logs by transaction hash. It allows to reprocess transaction which may be missed by range based indexers. ### Drive-by changes Quite a bit of refactoring ### Related issues Contributes into issue #4300 ### Backward compatibility Yes ### Testing E2E Tests --------- Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>	3 months ago
Daniel Savu	96ee728788	feat: turbo eth warp route (#4514 )	3 months ago
Danil Nemirovsky	040f7efd7f	chore: Remove pined dependencies on cargo-platform and predicates-core (#4502 ) ### Description Remove pined dependencies on cargo-platform and predicates-core since the pins are not needed. ### Backward compatibility Yes ### Testing Run E2E Tests Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>	3 months ago
Trevor Porter	57b0735472	feat: support multiple validator sets for a single app context in the relayer's observed validator metrics (#4495 ) ### Description - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4030 - The general idea of this change is that if the function `set_validator_latest_checkpoints` is called multiple times in a single message's metadata building, the reset of metrics relating to previously set validators now won't always occur. Atm, if two different multisig ISM validator sets are aggregated, they race each other to update the metric. With this change I expect the contention here to not occur anymore, and to still be able to handle changes in validator sets - This is a bit of a quick fix rather than something super robust tbh - I think in a vacuum I'd prefer something not dependent on time but instead dependent on a context of what message is being processed or something. But at the moment we're seeing very noisy alerts because of this issue, so would like to fix it ASAP. ### 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 months ago
Trevor Porter	78d6fcf5aa	fix: cap agent EVM tx limit to the latest block gas limit (#4489 ) ### Description - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4239 - I think ideally we'd maybe cache this, but there isn't a super accessible way of doing this atm and we need this ASAP to accommodate Everclear. So personally am happy to take on the extra RPC per transaction and at some point we'll likely want to revisit our tx submission efficiency, plus we end up needing the latest block for eip 1559 estimation anyways ### 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 months ago
Paul Balaji	a8f0ccd14f	chore: general fixes from enrolling new validators and chains (#4483 ) feat: enroll new validators and chains on core mailboxes - update token/gas prices - update to latest registry, containing the new ISM addresses - required some tooling fixes to handle solana/eclipse addresses being present - fix tooling where required - actually filter for EVM chains in HyperlaneAppChecker drive-by: - fix github-proxy changeset - fix print balances script - fix agent config update script - fix getRouterConfig - fix setting manual submission if unable to check on safe	3 months ago
Paul Balaji	1ab8751afb	fix: docker agent build (#4481 ) fix: docker agent build - update image from 1.72.1 -> 1.80.1 drive-by: update more `rust/` --> `rust/main/` drive-by: consolidate e2e non-cosmwasm cache, multiple cache steps per job can get in the way of each other --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	3 months ago

1 2

51 Commits (c53e3302b3c70c21cd0b620e8f2365d48c2ce289)