2535 Commits (707db4a2793004053fc6be963672db3f16f28e6b)

 

All Branches   

Search

Author	SHA1	Message	Date
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 	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)  --------- 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:  deploying relayer:  --------- 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
Trevor Porter	c84a1dc73b	feat: address blacklisting in the relayer (#4000) ... ### Description See context here https://discord.com/channels/935678348330434570/1236041564673806427/1252918894755319920 and https://discord.com/channels/935678348330434570/1252953507833708605/1252954456400592997 This is a rudimentary first step toward blacklisting addresses. Future options are outlined in https://discord.com/channels/935678348330434570/1236041564673806427/1252918894755319920. Eventually we can also fetch these addresses directly within the agent from an updated list that we cache and re-fetch occasionally. For now, this just relies on configured addresses. The approach is: - Allow hex addresses to be configured. These are intentionally treated as a Vec<u8> instead of an H160 / H256. This is because treating them as H160 is a leak of Ethereum-specific logic into non-chain-specific code in the relayer, and treating them as H256 would pad Ethereum addresses with a bunch of zeroes which would diminish the accuracy of our heuristic implemented in this. The subsequence stuff is a bit unfortunate because it's O(n^2) but 🤷‍♂️ - The heuristic is as follows - if any of the configured addresses are found as a subsequence in the message sender, recipient, or body, it's thrown out by the message processor, and the message will never make its way to the op_submitter. This heuristic for the body is to prevent warp route transfers that include that address. We could maybe convert Vec<u8> to H256 for the sender and recipient, I'm open to this - I just went with the substring approach bc it felt easiest tbh. ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Fixes https://github.com/hyperlane-xyz/issues/issues/1285 ### 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	c6ba381e44	chore: add more multisigs (#3974) ... ### Description Add multisig owners for linea, mode and blast. Expected violations are mailbox,proxyadmin, and ism violations (since the routing ism expected owner is now different) --------- Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>	5 months ago
github-actions[bot]	b758a5949c	Version Packages (#3991) ... 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/sdk@3.16.0 ### Minor Changes - 5cc64eb09: Add validator addresses for linea, fraxtal, sei. Estimate gas and add 10% buffer inside HyperlaneIsmFactory as well. ### Patch Changes - f9bbdde76: Fix initial total supply of synthetic token deployments to 0 - @hyperlane-xyz/core@3.16.0 - @hyperlane-xyz/utils@3.16.0 ## @hyperlane-xyz/core@3.16.0 ### Patch Changes - @hyperlane-xyz/utils@3.16.0 ## @hyperlane-xyz/cli@3.16.0 ### Patch Changes - Updated dependencies [f9bbdde76] - Updated dependencies [5cc64eb09] - @hyperlane-xyz/sdk@3.16.0 - @hyperlane-xyz/utils@3.16.0 ## @hyperlane-xyz/helloworld@3.16.0 ### Patch Changes - Updated dependencies [f9bbdde76] - Updated dependencies [5cc64eb09] - @hyperlane-xyz/sdk@3.16.0 - @hyperlane-xyz/core@3.16.0 ## @hyperlane-xyz/utils@3.16.0 ## @hyperlane-xyz/infra@3.16.0 ### Minor Changes - 5cc64eb09: Add support for new chains: linea, fraxtal, sei. Support osmosis remote. Drive-by fix to always fetch explorer API keys when running deploy script. ### Patch Changes - 5cc64eb09: Allow selecting a specific chain to govern in check-deploy script - Updated dependencies [f9bbdde76] - Updated dependencies [5cc64eb09] - @hyperlane-xyz/sdk@3.16.0 - @hyperlane-xyz/helloworld@3.16.0 - @hyperlane-xyz/utils@3.16.0 ## @hyperlane-xyz/ccip-server@3.16.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	5 months ago
Trevor Porter	47338f983d	fix: set resource requests for prometheus server & node exporter (#3998) ... ### Description See https://discord.com/channels/935678348330434570/935679524534911007/1252943931121864824 - an attempt to fix some intermittent issues we've seen with prometheus ### 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	f227eec892	fix: e2e invariant flake (#4017) ... ### Description Context is explained in the comment, copying it here: ``` // TODO: Sometimes we find more logs than expected. This may either mean that gas is deducted twice for the same message due to a bug, // or that submitting the message transaction fails for some messages. Figure out which is the case and convert this check to // strict equality. // EDIT: Having had a quick look, it seems like there are some legitimate reverts happening in the confirm step // (`Transaction attempting to process message either reverted or was reorged`) // in which case more gas expenditure logs than messages are expected. ``` ### 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	8ce2a71f20	chore: reconcile mainnet config json with registry (#4016) ... chore: reconcile mainnet config json with registry Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Tien Dao	683a96257e	fix: reduce loop test igpconfig (#4005) ... ### Description Refactor `testIgpConfig` in `testUtils.ts` for Enhanced Readability and Maintainability by reduce loop <!-- What's included in this PR? --> ### Drive-by changes 1. **Constant Usage:** Introduced `OVERHEAD_COST` as a constant to replace the magic number `60000`, making the purpose of this value clearer and the code easier to update. 2. **Improved Readability:** By using descriptive names and constants, the function is now easier to understand at a glance, which is particularly beneficial for new contributors or during code reviews. 3. **Dynamic Configuration Logic:** Ensured that the configuration for `overhead` and `oracleConfig` is dynamically generated for each chain, excluding the current chain to simulate realistic test scenarios. <!-- Are there any minor or drive-by changes also included? --> These changes do not alter the logic but make the codebase cleaner and more maintainable. ### 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: tiendn <tiendn.works@gmail.com>	5 months ago
Noah Bayindirli 🥂	bd3ca9195a	chore(cli): update ci-test to ci-advanced-test (#4011) ... ### Description - updates `ci-test.sh` name to `ci-advanced-test.sh` ### Drive-by changes - none ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3995 ### Backward compatibility - yes ### Testing - implicit	5 months ago
Yorke Rhodes	f9bbdde764	fix: derived token supply to 0 (#4010) ... ### Description Token deployer should always derive token metadata's total supply to 0, otherwise the collateral token's total supply will be minted initially on the synthetic, creating 2x the desired total supply. ### Related issues - Regression introduced by https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3820 - opens https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4013 ### Backward compatibility Yes ### Testing Unit Tests	5 months ago
Lee	5c8ba0b850	fix(cli): Rename `hyperlane config create chain` -> `hyperlane registry init` (#3978) ... ### Description Renames `hyperlane config create chain` -> `hyperlane registry init` as according to https://www.notion.so/hyperlanexyz/Must-use-config-to-create-a-new-chain-instead-of-the-registry-command-f7b407b29a834f7288f20e4c08bc206e?pvs=4 ### Drive-by changes - Rename `configure` to `init` for all functions - Reorder functions alphabetically ### Backward compatibility No ### Testing Manual	5 months ago
Noah Bayindirli 🥂	28f047739c	fix(cli): make native token required in chain config (#3944) ... ### Description - addresses P1 in https://www.notion.so/hyperlanexyz/CLI-Bug-Bash-5fc0833e51034baeba3beba9319160ff?pvs=4 - NOTE: Mimicking this behaviour: https://github.com/hyperlane-xyz/hyperlane-monorepo/blob/main/typescript/cli/src/utils/balances.ts#L23 - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4008 #### TODO: - Once merged, this section of the quickstart guide should be removed: https://www.notion.so/hyperlanexyz/Hyperlane-Quickstart-Beta-4d9ff48720ee43fa8456a7d1517098dd?pvs=4#15534475fd8d4b398e51e9e0d527fb48 - cc @avious00	5 months ago
Nam Chu Hoai	290c8cb6f6	feat: Script to generate Renzo Warp Route Configuration (#3983) ... ### 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
Lee	b7003cf356	feat: add stdout.rows to pagesize calculation with DEFAULT_PAGE_SIZE (#3968) ... ### Description - Add process.stdout.rows to pageSize adjustment for chain selection - Defaults to 15 if process.stdout.rows < 0 ### Backward compatibility Yes ### Testing Manual	5 months ago
Yorke Rhodes	bf7ad09da3	feat(cli): add `warp --symbol` flag (#3992) ... ### Description - This allows users to interact read warp routes from the registry with symbol identifier rather than chain/address ### Drive-by Rename `wei` to `amount` ### Backward compatibility No, outputs chain map ### Testing - Manual (single) ```sh $ yarn hyperlane warp read --symbol EZETH $ yarn hyperlane warp send --symbol EZETH ``` (multiple) ```sh $ yarn hyperlane warp read --symbol USDC $ yarn hyperlane warp send --symbol USDC ``` --------- Co-authored-by: Noah Bayindirli 🥂 <noah@hyperlane.xyz>	5 months ago
Tien Dao	6cff4a2a9e	fix: prevent duplication in verification artifacts array (#4001) ... ## Enhance Artifact Deduplication in HyperlaneDeployer ### Description **Overview**: The `addVerificationArtifacts` method in the `HyperlaneDeployer` class previously added verification artifacts without checking for duplicates, potentially leading to redundant data that could affect performance and reliability. This PR introduces a mechanism to prevent such duplication by implementing a shallow comparison check before adding new artifacts. **Changes**: - Modified the `addVerificationArtifacts` method to include a shallow comparison against existing artifacts. - Used direct property comparisons to efficiently prevent the addition of duplicate entries. - Ensured that the comparison handles large ABI-encoded strings efficiently by comparing string references. **Benefits:** - Efficiency: Reduces unnecessary processing and storage by avoiding duplicate entries. - Accuracy: Ensures that the verification process uses a unique set of artifacts, improving the reliability of deployment verifications. - Performance: Minimizes the overhead associated with handling large sets of data, particularly with large ABI-encoded strings. **Testing:** - Added unit tests to verify that duplicates are not added to the artifacts array. - Ensured existing integration tests pass with the new changes, confirming backward compatibility and functional integrity. This update streamlines the deployment process by ensuring that only necessary and unique verification artifacts are considered, thereby optimizing both memory usage and processing time during contract deployments. --------- Co-authored-by: tiendn <tiendn.works@gmail.com>	5 months ago
Daniel Savu	030eaf1204	chore: bump agent docker images (#3999) ... ### 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	e0f226806e	feat: implement `create()` for `EvmHookModule` (#3861) ... resolves https://github.com/hyperlane-xyz/issues/issues/1153 - enables creation of new Hooks through the EvmHookModule - introduce `EvmModuleDeployer` - separate from `HyperlaneDeployer` - contains some basic methods to deploy a contract/proxy - reduces module necessity HyperlaneDeployer IN PROGRESS: - [x] tests - [x] figure out why randomly generated routing/fallbackrouting hooks fail - [x] figure out why protocol fee hooks fail  --------- Signed-off-by: Paul Balaji <paul@hyperlane.xyz>	5 months ago