hyperlane-monorepo

Commit Graph

Author	SHA1	Message	Date
Daniel Savu	f8b33d1270	chore: update deployed relayer image (#4088 ) ### 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
Nam Chu Hoai	4cc9327e52	fix(cli): ezETH deploy fixes (#4009 ) ### Description some minor fixes to make the ezEth deploy work. Does not include the modifications to contract verification retries that I made. --------- Co-authored-by: Lee <6251863+ltyu@users.noreply.github.com>	5 months ago
Paul Balaji	d35b54670d	feat(keyfunder): make IGP claim thresholds configurable via command line args (#4074 ) hit successor to https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3284 resolves https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4049 - igp claim thresholds are moved to command line args instead, like desired balances - making it easier to tweak IGP claim thresholds - default claim threshold is 20% of desired balance for that chain - roughly follows what I've seen with the other balance vs igp claim thresholds - adding thresholds for all chains we've configured a desired relayer balance for - drive-by fixing keyfunder logging to include the relevant metadata testing: - ran locally and successfully performed igp claims on [blast](https://blastscan.io/tx/0x314d83d16e0406f77731befc7e8387dc946af01f7dc2200a426ff9748ad76d27), [linea](https://lineascan.build/tx/0xa5f4731ebcff073dacc6c15326196002bafd9578059688fd2f29db1a2742cb14), [viction](https://www.vicscan.xyz/tx/0x39921d3018a7b019518aa7a55a45ff29cce379bb9aabf0910c14423bd88689d5) & more --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Trevor Porter	6f4ef05d41	feat: faster way of figuring out how many new scraper rows were inserted (#4073 ) ### Description ### Context Full context / thread: https://discord.com/channels/935678348330434570/1254871503825141923 Copied here: so this is kinda interesting basically the gas payment indexing in the scraper task is consistently prioritizing hook-based indexing work over block range indexing work this only manifests in the scraper and for arbitrum because: there are a lot of arbitrum origin messages on the scraper, each gas payment indexing tick takes a very long time because of some very suboptimal queries. store_payments can take like 10-15 seconds! You can see batches of logs Found log(s) in index range https://cloudlogging.app.goo.gl/Bo9Q7YwyziSqjsEu7 that correspond with the gas payment contract sync block height (green line) advancing https://abacusworks.grafana.net/goto/poW4KOQIg?orgId=1 ![image](https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/20362969/65da2e44-5728-4ecc-9c1f-52741805eb5b) but we're still indexing gas payments bc of hook indexing - there are tons of Found log(s) for tx id https://cloudlogging.app.goo.gl/QvDaBuf67SjjKviw6 In the scraper's store_payments we bizarrely end up performing 2 very expensive queries with the calls to payments_count - it gets the count of gas payments for the provided domain so it can figure out how many new gas payments were actually inserted https://github.com/hyperlane-xyz/hyperlane-monorepo/blob/main/rust/agents/scraper/src/db/payment.rs#L27-L64 These queries vary a bunch in how expensive they can be - sometimes each one is like 1-2 seconds, sometimes it gets up to 10 seconds each though https://cloudlogging.app.goo.gl/cDFNH3oxh6WWV3Go8 ![image](https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/20362969/612c7999-21b2-43f4-861f-8b42580e4cb7) easiest fix is probably to figure out how to make store_payments less expensive - we probably don't need to be making these calls to payments_count to figure out which ones are new which ill do atm there's maybe a decent argument to having hook indexing and range indexing not contend with one another but we should be able to kick that can also an annoying thing is https://github.com/hyperlane-xyz/hyperlane-monorepo/blob/main/rust/hyperlane-base/src/contract_sync/mod.rs#L155 this log not showing up, probably some weird instrumentation setup or something makes debugging harder ### The fix We want to keep supporting the possibility that we've double-indexed a data type, and to only return the number of new rows inserted. We want to keep each indexing task as non-conflicting as possible - we know that only one scraper is running at a time, but that a task for each chain and data type is executing concurrently. It's possible for e.g. two gas payment indexing tasks to try to insert into the same table concurrently, but it'll be for different domains. Insert statement concurrency issues aren't an issue because the only chance for conflict is the auto-incrementing primary key id, but this is all handled properly by database internals. Insert results only give the latest ID resulting from the insertion. E.g. if no matter how many rows were inserted, it gives the latest ID from that batch, but no info about how many were in the batch. We could do something like get the latest id in the table for all domains (this is cheap) before, then do the insert, and then get the latest id again, but this is susceptible to race conditions if concurrent tasks get an insertion in during that time as well. Shoving all these into a transaction doesn't seem to solve the problem either unless there's a lock on the table. However, sea-orm doesn't support table level locks, just select locks. We could also use a CTE to perform as a way to perform the select & insertion atomically and return the value of the select - but again sea-orm doesn't seem to provide a nice way of doing this from what I could tell. Instead, my suggested fix is: 1. Get the latest id in the table relating to the specific domain (this is cheap, < 100ms) 2. Perform the insertion 3. Count how many new rows for the specific domain now exist whose id is > the id from (1). This is also cheap, < 100ms. If there is a very long time since the last insertion for the domain, this could take longer, but in practice this doesn't seem to be the case. If this couple order of magnitude improvement still poses issues in the future, we can consider other alternatives, probably involving locking or fancier CTE queries. Some example queries and how long they take: Before (2x of these would occur!): <img width="477" alt="Screen Shot 2024-06-28 at 12 36 41 PM" src="https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/20362969/5cc8ac35-74fb-4847-9c6f-448deb253a0c"> Now: 1. Max id for a given domain <img width="494" alt="Screen Shot 2024-06-28 at 12 37 00 PM" src="https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/20362969/56dbb3ff-b540-458c-809c-56ebfbfd3b0f"> 2. Subsequent count but with an ID filter - note I actually changed this query to look for IDs > 3600000, which includes 55300 rows and it's still just 102ms! <img width="632" alt="Screen Shot 2024-06-28 at 12 37 49 PM" src="https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/20362969/11593180-682f-4867-9867-97fd93512802"> ### Drive-by changes - Updated the neutron image along with a deploy there ### Related issues ### Backward compatibility ### Testing Ran some sorta ad-hoc unit tests to test my new query by running against the prod db with a tokio::task. Tested for a new domain and an existing one	5 months ago
J M Rossy	36e75af4ed	feat: Add deployer to ChainMetadata schema (#3987 ) ### Description - Add optional deployer field to ChainMetadata schema ### Drive-by changes - Order ChainMetadata zod schema fields alphabetically ### Related issues Required for https://github.com/hyperlane-xyz/hyperlane-registry/issues/42 ### Backward compatibility Yes	5 months ago
J M Rossy	378a5b79f7	fix: Remove extra fields in warp core config (#4072 ) ### Description Remove extra fields in warp core configs. Context: https://github.com/hyperlane-xyz/hyperlane-registry/pull/73 Discussion: https://discord.com/channels/935678348330434570/1255901895503908934 ### Drive-by changes Improve type assertion of `assert` util ### Backward compatibility Yes ### Testing Took configs from CLI e2e test artifact and tested it in registry CI.	5 months ago
Noah Bayindirli 🥂	56f5d88e96	fix(cli): gracefully handle RPC failures on hook derivation (#4062 ) ### Description - gracefully handles RPC failures on hook derivation - TODO: - ISM derivation ### Drive-by changes - none ### Related issues - P1 ### Testing - manual	5 months ago
Daniel Savu	befc38daba	fix: agent log verbosity (#4054 ) ### Description tbh I don't know why, but this makes all the logs we were previously missing show up in e2e: - `b99920ecca/rust/hyperlane-base/src/contract_sync/mod.rs (L155)` - `f68319f46e/rust/hyperlane-base/src/db/rocks/hyperlane_db.rs (L93)` ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3915 ### 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 E2E, by counting occurrences of the two logs linked above in relayer log output. Before this change, those logs would be missing completely --------- Co-authored-by: Paul Balaji <paul@hyperlane.xyz>	5 months ago
github-actions[bot]	526984cc3c	Version Packages (#4034 ) 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@4.0.0 ### Major Changes - df6a18053: Release CLI v4.0.0. ### Minor Changes - 44cc9bf6b: Add CLI command to support AVS validator status check - b05ae38ac: Gracefully handle RPC failures during warp send & fix deriving hook error that prevents warp and core test messages on the cli. - 9304fe241: Use metadata builders in message relaying - 6398aab72: Upgrade registry to 2.1.1 - 5c8ba0b85: Rename hyperlane config create chain -> hyperlane registry init. Rename all `configure` to `init` - cd419c98a: Add a validator preFlightCheck command verifying that the validator has been announced for a given chain - 35f869950: Add command to support creating agent configs - bf7ad09da: feat(cli): add `warp --symbol` flag - b0828b3d0: Reintroduce `ism read` and `hook read` commands - 129bd871d: Add chain displayName prompt with default - 4040db723: Fix createDefaultWarpIsmConfig to default to trusted relayer and fallback routing without prompts - 6db9fa9ad: Implement hyperlane warp deploy - bd3ca9195: Updates ci-test.sh to ci-advanced-test.sh. - b7003cf35: Add stdout.rows to pagesize calculation with DEFAULT_PAGE_SIZE ### Patch Changes - 3283eefd6: Removes default pattern for chain name when creating a new chain. - 4dd2651ee: Add xerc20 limit lookups to warp read - 6b63c5d82: Adds deployment support for IsmConfig within a WarpRouteConfig - Updated dependencies [`b05ae38ac`] - Updated dependencies [`9304fe241`] - Updated dependencies [`bdcbe1d16`] - Updated dependencies [`6b63c5d82`] - Updated dependencies [`e38d31685`] - Updated dependencies [`e0f226806`] - Updated dependencies [`6db9fa9ad`] - @hyperlane-xyz/sdk@4.0.0 - @hyperlane-xyz/utils@4.0.0 ## @hyperlane-xyz/core@4.0.0 ### Minor Changes - 44cc9bf6b: Add CLI command to support AVS validator status check ### Patch Changes - @hyperlane-xyz/utils@4.0.0 ## @hyperlane-xyz/helloworld@4.0.0 ### Minor Changes - 6398aab72: Upgrade registry to 2.1.1 - bf7ad09da: feat(cli): add `warp --symbol` flag ### Patch Changes - Updated dependencies [`44cc9bf6b`] - Updated dependencies [`b05ae38ac`] - Updated dependencies [`9304fe241`] - Updated dependencies [`bdcbe1d16`] - Updated dependencies [`6b63c5d82`] - Updated dependencies [`e38d31685`] - Updated dependencies [`e0f226806`] - Updated dependencies [`6db9fa9ad`] - @hyperlane-xyz/core@4.0.0 - @hyperlane-xyz/sdk@4.0.0 ## @hyperlane-xyz/sdk@4.0.0 ### Minor Changes - b05ae38ac: Gracefully handle RPC failures during warp send & fix deriving hook error that prevents warp and core test messages on the cli. - 9304fe241: Use metadata builders in message relaying - bdcbe1d16: Add EvmWarpModule with create() - e38d31685: Add logic to set smart provider log level to disable provider logs during Warp TokenType derive - e0f226806: - Enables creation of new Hooks through the `EvmHookModule`. - Introduces an `EvmModuleDeployer` to perform the barebones tasks of deploying contracts/proxies. - 6db9fa9ad: Implement hyperlane warp deploy ### Patch Changes - 6b63c5d82: Adds deployment support for IsmConfig within a WarpRouteConfig - Updated dependencies [`44cc9bf6b`] - @hyperlane-xyz/core@4.0.0 - @hyperlane-xyz/utils@4.0.0 ## @hyperlane-xyz/utils@4.0.0 ## @hyperlane-xyz/infra@4.0.0 ### Minor Changes - 6398aab72: Upgrade registry to 2.1.1 - bf7ad09da: feat(cli): add `warp --symbol` flag ### Patch Changes - Updated dependencies [`b05ae38ac`] - Updated dependencies [`9304fe241`] - Updated dependencies [`6398aab72`] - Updated dependencies [`bdcbe1d16`] - Updated dependencies [`6b63c5d82`] - Updated dependencies [`bf7ad09da`] - Updated dependencies [`e38d31685`] - Updated dependencies [`e0f226806`] - Updated dependencies [`6db9fa9ad`] - @hyperlane-xyz/sdk@4.0.0 - @hyperlane-xyz/helloworld@4.0.0 - @hyperlane-xyz/utils@4.0.0 ## @hyperlane-xyz/ccip-server@4.0.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	5 months ago
Paul Balaji	892efd4fe7	feat(cli): merge in cli-2.0 (v4.0.0) (#3981 ) CLI v4.0.0	5 months ago
Paul Balaji	653bbcff52	fix(e2e): hardcode kathy chains for e2e in send-test-messages.ts (#4067 ) resolves https://github.com/hyperlane-xyz/issues/issues/1291 - remove test4 from kathy test - drive-by tidy-up of `test4` metadata - resets e2e test timeout back to original figure - reuse original e2e rust cache gonna keep the original commits on here as a trail of thought --------- Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Paul Balaji	d51813a1da	bump E2E_CI_TIMEOUT_SEC on non-cosmwasm test to 1hr Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Paul Balaji	a23cf6420c	tidy up test.yml branch triggers Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Paul Balaji	cf253328a0	Update e2e-non-cosmwasm ci timeout	5 months ago
Paul Balaji	45dc4f99c9	use clean rust cache for e2e	5 months ago
Noah Bayindirli 🥂	df6a180538	add changeset	5 months ago
Noah Bayindirli 🥂	78b2eb8fee	update retreive ==> retrieve	5 months ago
Noah Bayindirli 🥂	66ec15af3d	chore(cli): merge branch 'main' into cli-2.0 (#4063 ) ### 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
Noah Bayindirli 🥂	a2a633b4df	Merge branch 'main' into noah/merge	5 months ago
Mohammed Hussan	44cc9bf6b3	feat(cli): Add avs validator status command (#4056 ) ### Description <!-- What's included in this PR? --> - Command to check all operators on our AVS and show the chains that they are validating on - Already been reviewed here https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4004, this PR was to merge it main instead of cli-2.0 Example usage: ``` yarn hyperlane avs check --chain ethereum --registry $REGISTRY Hyperlane CLI Checking AVS validator status for ethereum, this may take up to a minute to run... ❗️ MerkleTreeHook is not deployed on anvil8545 Operator name: Abacus Works AVS Operator Operator address: 0xFe114FcC7609578f525219a8eF77e2CCe27C5357 Validator address: 0x03c842db86A6A3E524D4a6615390c1Ea8E2b9541 Validating on... ethereum Storage location: s3://hyperlane-mainnet3-ethereum-validator-0/us-east-1 Latest merkle tree checkpoint index: 8219 Latest validator checkpoint index: 8219 ✅ Validator is signing latest checkpoint Operator name: Kelp by Kiln Operator address: 0x96fC0751e0febe7296d4625500f8e4535a002c7d Validator address: 0xEa5f21513182e97D0169a4d2E7aC71Ae8827F5bC Validating on... ethereum Storage location: s3://kiln-mainnet-hyperlane-validator-signatures/eu-west-1/ethereum Latest merkle tree checkpoint index: 8219 ❌ Failed to fetch latest signed checkpoint index The following warnings were encountered: ❗️ Failed to fetch latest signed checkpoint index of validator on ethereum, this is likely due to failing to read an S3 bucket ``` ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> - Fixes #3976 ### 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 --> No ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> Manual	5 months ago
Paul Balaji	2de63aab28	fix(cli): add hook/ism commands (#4060 ) Forgot to add the new commands to the top-level cli.ts when I added back the commands in https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3990 Noticed when trying to test https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4055 Tested with: ```sh $ yarn workspace @hyperlane-xyz/cli run hyperlane ism read --chain inevm --address 0x79A7c7Fe443971CBc6baD623Fdf8019C379a7178 Hyperlane CLI {"level":30,"time":1719408936852,"pid":74170,"msg":"Your CLI version: 3.15.0, latest version: 3.16.0"} Hyperlane ISM Read ------------------ ISM Config at 0x79A7c7Fe443971CBc6baD623Fdf8019C379a7178 on inevm: address: "0x79A7c7Fe443971CBc6baD623Fdf8019C379a7178" type: staticAggregationIsm modules: - address: "0x718901b7570c59241304758345aF297Ff47D83A1" type: messageIdMultisigIsm validators: - "0x5450447aeE7B544c462C9352bEF7cAD049B0C2Dc" - "0x570AF9B7B36568C8877eeBBA6c6727aA9DAB7268" - "0x8292B1A53907eCE0f76Af8A50724e9492bcDc8A3" - "0xEAF5cF9100f36A4BaEeA779F8745DDa86159103C" threshold: 2 - address: "0x8dac7Df615Cb7599aCfD4EC2CBd9c67Cd5DF6BF6" type: merkleRootMultisigIsm validators: - "0x5450447aeE7B544c462C9352bEF7cAD049B0C2Dc" - "0x570AF9B7B36568C8877eeBBA6c6727aA9DAB7268" - "0x8292B1A53907eCE0f76Af8A50724e9492bcDc8A3" - "0xEAF5cF9100f36A4BaEeA779F8745DDa86159103C" threshold: 2 threshold: 1 ``` ```sh $ yarn workspace @hyperlane-xyz/cli run hyperlane hook read --chain polygon --address 0x0071740Bf129b05C4684abfbBeD248D80971cce2 Hyperlane CLI {"level":30,"time":1719409044431,"pid":75236,"msg":"Your CLI version: 3.15.0, latest version: 3.16.0"} Hyperlane Hook Read ------------------ Hook Config at 0x0071740Bf129b05C4684abfbBeD248D80971cce2 on polygon: owner: "0xa7ECcdb9Be08178f896c26b7BbD8C3D4E844d9Ba" address: "0x0071740Bf129b05C4684abfbBeD248D80971cce2" type: interchainGasPaymaster beneficiary: "0xa7ECcdb9Be08178f896c26b7BbD8C3D4E844d9Ba" oracleKey: "0xa7ECcdb9Be08178f896c26b7BbD8C3D4E844d9Ba" overhead: ancient8: 159736 blast: 159736 ethereum: 166887 bsc: 160545 inevm: 159736 gnosis: 160545 injective: 600000 celo: 160948 avalanche: 159736 fraxtal: 159337 arbitrum: 166887 base: 160948 sei: 159337 osmosis: 600000 scroll: 160545 mode: 159337 mantapacific: 182044 moonbeam: 160545 linea: 159736 neutron: 600000 polygonzkevm: 159736 redstone: 159337 optimism: 160948 zetachain: 159337 viction: 159736 oracleConfig: ancient8: tokenExchangeRate: "89752048061167" gasPrice: "483551859" blast: tokenExchangeRate: "89752048061167" gasPrice: "500000000" ethereum: tokenExchangeRate: "89752048061167" gasPrice: "20000000000" bsc: tokenExchangeRate: "15385035499726" gasPrice: "5000000000" inevm: tokenExchangeRate: "572910977607" gasPrice: "30301230683" gnosis: tokenExchangeRate: "27292763517" gasPrice: "633618644641" injective: tokenExchangeRate: "572910977607" gasPrice: "9777321413" celo: tokenExchangeRate: "15645849262" gasPrice: "1103178625684" avalanche: tokenExchangeRate: "656744948115" gasPrice: "43212830197" fraxtal: tokenExchangeRate: "89790551611140" gasPrice: "484265767" arbitrum: tokenExchangeRate: "89752048061167" gasPrice: "500000000" base: tokenExchangeRate: "89752048061167" gasPrice: "480773616" sei: tokenExchangeRate: "9438558163" gasPrice: "1842759845538" osmosis: tokenExchangeRate: "1448574549300000000" gasPrice: "3866" scroll: tokenExchangeRate: "89752048061167" gasPrice: "1445081549" mode: tokenExchangeRate: "89752048061167" gasPrice: "484473517" mantapacific: tokenExchangeRate: "89752048061167" gasPrice: "437064663" moonbeam: tokenExchangeRate: "5307373020" gasPrice: "3258335859000" linea: tokenExchangeRate: "89752048061167" gasPrice: "483551859" neutron: tokenExchangeRate: "1169238121200000000" gasPrice: "11976" polygonzkevm: tokenExchangeRate: "89752048061167" gasPrice: "3950000000" redstone: tokenExchangeRate: "89752048061167" gasPrice: "193789404" optimism: tokenExchangeRate: "89752048061167" gasPrice: "480773616" zetachain: tokenExchangeRate: "22360158382" gasPrice: "777856564583" viction: tokenExchangeRate: "9926843254" gasPrice: "1748784306278" ``` Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Lee	b05ae38ac0	fix(cli): RPC errors while sending test messages (#4055 ) ### Description This PR fixes RPC errors when trying to send a test message using the CLI for older chains that don't have tokenType (e.g., `hyperlane send message --relay --origin fuji --destination betaop`) Additional details: https://discord.com/channels/935678348330434570/1254873902480359435/1255215832959811687 ### Backward compatibility Yes ### Testing - tested with `hyperlane warp deploy` and then `hyperlane warp send --relay --warp $HOME/.hyperlane/deployments/warp_routes/ETH/alfajores-betaop-config.yaml` - tested `hyperlane send message --relay --origin fuji --destination betaop` - tested `hyperlane send message --relay --origin alfrajores --destination betaop` - tested `hyperlane send message --relay --origin holesky --destination betaop` - tested `hyperlane core read --mailbox 0xEf9F292fcEBC3848bF4bB92a96a04F9ECBb78E59 --chain alfajores ` --------- Co-authored-by: Noah Bayindirli 🥂 <noah@primeprotocol.xyz>	5 months ago
Daniel Savu	aecb65a986	feat: persist status labels (#4043 ) ### Description Builds on top of https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4003 to persist updates to an operation's status to the db, so we no longer default to `FirstPrepareAttempt` upon restarting the relayer ### Drive-by changes Moves `hyperlane_db` from `hyperlane_base` to `hyperlane_core` so it can be added to the `PendingOperation` trait. `PendingMessage` already stores a reference to the db in `ctx`, so I figured it doesn't break any assumptions. ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility Yes ### Testing Unit tests encoding of `PendingOperationStatus`, need to manually tests e2e	5 months ago
Yorke Rhodes	4dd2651ee9	feat: add xerc20 limit lookups to warp read (#4020 ) ### Description Adds xerc20 mint and burn limit fetching to `warp read --symbol` ### Backward compatibility Yes ### Testing Manual ![Screenshot 2024-06-20 at 3 19 13 PM](https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/3020995/9692e3fd-eecb-4758-af39-04639639b482)	5 months ago
Noah Bayindirli 🥂	c81721e59c	feat(cli): display formatted deployment plan to confirm core deploy (#4050 ) ### Description - Displays formatted deployment plan to confirm core deploy ### Drive-by changes - none ### Related issues - Fixes P1 ### Backward compatibility - yes ### Testing - Output: ``` ➜ cli git:(cli-2.0) ✗ hl core deploy --registry $HOME/workplace/Hyperlane/hyperlane-registry Hyperlane CLI Hyperlane permissionless deployment ------------------------------------------------ ? Select chain to connect: alpha Deployment plan =============== Transaction signer and owner of new contracts: 0x16F4898F47c085C41d7Cc6b1dc72B91EA617dcBb Deploying core contracts to network: alpha ┌────────────────────────┬──────────────────────────────────────────────┐ │ (index) │ Values │ ├────────────────────────┼──────────────────────────────────────────────┤ │ Name │ 'alpha' │ │ Display Name │ 'Alpha' │ │ Chain ID │ 75904 │ │ Domain ID │ 75904 │ │ Protocol │ 'ethereum' │ │ JSON RPC URL │ 'https://alpha-tk.rpc.caldera.xyz/http' │ │ Native Token: Symbol │ 'ETH' │ │ Native Token: Name │ 'Ether' │ │ Native Token: Decimals │ 18 │ └────────────────────────┴──────────────────────────────────────────────┘ Note: There are several contracts required for each chain, but contracts in your provided registries will be skipped. ? Is this deployment plan correct? (Y/n) ```	5 months ago
Paul Balaji	b99920ecca	fix(ci): use the correct commit sha for agent/monorepo image tags (#4052 ) - use the correct commit hash for the agent and monorepo image tag - the actual checked out commit was correct, but this now ensures that the TAG_SHA matches the checked out commit hash - drive-by ensure that workflow gets triggered on changes to itself --------- Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Daniel Savu	d213e32341	feat: relayer queue operation labels (#4003 ) ### Description - adds status labels to operations in the relayer queues. In practice, the most useful ones are those for when a message is retried due to an error. Labels are defined as enums to keep the cardinality finite, the size of prometheus metrics could get very large - whenever a message is pushed to a queue, the interface requires specifying the new status as a `Option<PendingOperationStatus>`. If `None`, the status is left as before (such as in the case when an operation isn't ready to be retried). - a limitation is that labels aren't stored in the DB, so messages are loaded with the `FirstPrepareAttempt` label. I just triggered retries for destinations I wanted to get labels for, but we could persist to the db in a follow-up PR - Example prep queue labels for inevm: <img width="621" alt="Screenshot 2024-06-21 at 18 05 58" src="https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/23065004/f53b2858-371f-4b6b-86d9-5c21409d641f"> ### Drive-by changes - removes `make_op_try` as it doesn't really add anything that couldn't be done with regular Rust - bumps the `strum` version because there was a bug in the previous one, preventing inner enum fields from being converted to strings ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Yes ### Testing Manual	5 months ago
Trevor Porter	e6b9d0e1bf	chore: bump arb costs (#4018 ) ### Description Big gas spike on arb rn, see https://discord.com/channels/935678348330434570/1253313812652888154 for context ### 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
Daniel Savu	718d2c27da	chore: don't reset retry count when processing retry API reqs (#4037 ) ### Description When messages are retried due to the Message Retry API, we bring messages to the front of the queue (by changing their `next_attempt_after`), but also reset their retry count. For messages that are unprocessable due to various reasons (and hence have very high `next_attempt_after`), resetting the retry count will cause the relayer to waste time instead of trying to process newer messages. This PR makes it such that the retry API will cause messages to be retried immediately once, but won't boost their priority in the queue afterwards (because `num_retries` isn't changed). ### 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
Yorke Rhodes	7c7e0dd5ed	docs: add docstrings for multisig signature ordering (#4042 ) ### Description Update `MultisigISM.verify` docs with clarity around signature ordering	5 months ago
J M Rossy	47cba13522	chore: Upgrade registry to 2.1.1 (#4035 )	5 months ago
Paul Balaji	cc0ea73360	feat: pin monorepo to a specific registry version (#4041 ) - feat: pin monorepo to a specific registry version (cherry-pick #4031) - drive-by agent config update --------- Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	5 months ago
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
Noah Bayindirli 🥂	3941c99416	chore(cli): display new chain config after registry init (#4038 ) ### Description - displays new chain config after `hl registry init` ### Drive-by changes - none ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4039 ### Backward compatibility - yes ### Testing - manual	5 months ago
Paul Balaji	91d2f6d56a	chore: include 10% gas estimate bump in EvmIsmModule (#3957 ) - in the multiprovider we already do a 10% bump on the estimated gas, as a cover for unpredictable gas estimation - we recently found that the ism factories do not do this, which caused problems in a recent hyperlane core deployment - added this into the ism factories on `main` - so we are ensuring that this change is properly reflected in the new ism module as well	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
Noah Bayindirli 🥂	7add7bf871	chore(cli): format message stdout during hl send message (#4025 ) ### Description - formats message stdout during hl send message ### Drive-by changes - none ### Related issues - P1 ### Backward compatibility - yes ### Testing - manual example output: ``` ➜ cli git:(06-20-fix_cli_add_units_and_explanation_to_protocol_fee_input) ✗ hl send message --relay --registry $HOME/workplace/Hyperlane/hyperlane-registry Hyperlane CLI ? Select the origin chain fuji ? Select the destination chain brown Running pre-flight checks for chains... ✅ Chains are valid ✅ Signer is valid ✅ Balances are sufficient Dispatching message Pending https://testnet.snowtrace.io/tx/0x5d0793052ad6df340242f332a218b14a8182b083bebbf5666faac83f7c20ed66 (waiting 3 blocks for confirmation) Sent message from fuji to 0xb2b1125501aA997b912A0fa32f74B3041C0c4FcB on brown. Message ID: 0x2ba918e23225a7dc67ec803cff998cbe9beefd45c7243422349035dcac5e20d0 Message: parsed: version: 3 nonce: 2605 origin: 43113 sender: "0x00000000000000000000000016f4898f47c085c41d7cc6b1dc72b91ea617dcbb" destination: 6700087 recipient: "0x000000000000000000000000b2b1125501aa997b912a0fa32f74b3041c0c4fcb" body: "0x48656c6c6f21" originChain: fuji destinationChain: brown id: "0x2ba918e23225a7dc67ec803cff998cbe9beefd45c7243422349035dcac5e20d0" message: "0x0300000a2d0000a86900000000000000000000000016f4898f47c085c41d7cc6b1d\ c72b91ea617dcbb00663c37000000000000000000000000b2b1125501aa997b912a0fa32f74b3\ 041c0c4fcb48656c6c6f21" ```	5 months ago
Noah Bayindirli 🥂	bb0c7afab7	fix(cli): add units and explanation to protocol fee input (#4024 ) ### Description - add units and explanation to protocol fee input - adds `inputWithInfo` to allow optional info developers can request with `i` ### Drive-by changes - none ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4023 ### Backward compatibility - yes ### Testing - manual example output: ``` ➜ cli git:(cli-2.0) ✗ hl core init --registry $HOME/workplace/Hyperlane/hyperlane-registry --advanced Hyperlane CLI Hyperlane Core Configure ------------------------ Creating a new core deployment config... ? Detected owner address as 0x16F4898F47c085C41d7Cc6b1dc72B91EA617dcBb from signer, is this correct? yes Creating a new advanced ISM config WARNING: USE AT YOUR RISK. Advanced ISM configs require knowledge of different ISM types and how they work together topologically. If possible, use the basic ISM configs are recommended. ? Select ISM type trustedRelayerIsm Creating trustedRelayerIsm... ? Detected relayer address as 0x16F4898F47c085C41d7Cc6b1dc72B91EA617dcBb from signer, is this correct? yes Created trustedRelayerIsm! ? Select default hook type protocolFee Creating protocolFee... ? Detected owner address as 0x16F4898F47c085C41d7Cc6b1dc72B91EA617dcBb from signer, is this correct? yes ? Use this same address (0x16F4898F47c085C41d7Cc6b1dc72B91EA617dcBb) for the beneficiary? yes ? Enter max protocol fee for protocol fee hook (wei): [enter 'i' for more info] i The max protocol fee (ProtocolFee.MAX_PROTOCOL_FEE) is the maximum value the protocol fee on the ProtocolFee hook contract can ever be set to. Default is set to 100000000000000000 wei; between 0.001 and 0.1 wei is recommended. For more information, please visit https://docs.hyperlane.xyz. ? Enter max protocol fee for protocol fee hook (wei): [enter 'i' for more info] 0.1 ? Enter protocol fee for protocol fee hook (wei): [enter 'i' for more info] i The protocol fee is the fee collected by the beneficiary of the ProtocolFee hook for every transaction executed with this hook. Default is set to 0 wei; must be less than max protocol fee of 100000000000000000. For more information, please visit https://docs.hyperlane.xyz. ? Enter protocol fee for protocol fee hook (wei): [enter 'i' for more info] 0 Created protocolFee! ```	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
Lee	e38d31685e	feat: Add smart provider log setter (#4007 ) ### Description - Add logic to enable setting of log levels to the SmartProvider. - Add logic to set log level to `silent` in the beginning of `deriveTokenType()`, and then resetting it after. ### Related issues - Fixes #4006 ### Backward compatibility Yes ### Testing Manual	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	39f66df326	feat(ci): rust caching in `test` workflow (#4021 ) - brings https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4015 to cli-2.0 branch - cherry-pick e2e flake fix - ensure tests run on pushes to `cli-2.0` --------- Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com> Co-authored-by: Daniel Savu <23065004+daniel-savu@users.noreply.github.com>	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>	5 months ago

1 2 3 4 5 ...

2452 Commits (69fba689b9975ed6c70fa58f7f44e809cc206bbe) All Branches Search

2452 Commits (69fba689b9975ed6c70fa58f7f44e809cc206bbe)

All Branches