hyperlane-monorepo

Commit Graph

Author	SHA1	Message	Date
Kunal Arora	b110a73f80	fix:deploy-core ci writing unnecessary cache fix (#3542 ) ### Description - For https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3483, I was passing in ica artifacts through the cachedAddressesMap function which in turn writes these addresses to the deploy addresses.json file and this causes chain not found error in the subsequent module deployments. Fix - Read from options.icaApp for the router address (extra step added to the deployer) ### Drive-by changes None ### Related issues - https://discord.com/channels/935678348330434570/1225043256782622730 ### Backward compatibility Yes ### Testing local manual	7 months ago
Kunal Arora	aab63d466e	fix: contract verification for ICAs (#3532 ) ### Description - verified ICA router and ISM contracts for mainnet and testnet chains excluding avalanche and alfajores. ### Drive-by changes - update contractName for ICA ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3526 ### Backward compatibility Yes ### Testing None	7 months ago
github-actions[bot]	b88b56a589	Version Packages (#3495 ) 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/core@3.10.0 ### Minor Changes - 96485144a: SDK support for ICA deployment and operation. - 38358ecec: Deprecate Polygon Mumbai testnet (soon to be replaced by Polygon Amoy testnet) ### Patch Changes - Updated dependencies [`96485144a`] - Updated dependencies [`4e7a43be6`] - @hyperlane-xyz/utils@3.10.0 ## @hyperlane-xyz/cli@3.10.0 ### Minor Changes - 3ec81081c: Breaking: Update the `hyperlane chains list` command to accept an `env` (either 'mainnet' or 'testnet') to list chains for. Update `hyperlane chains list` command to pull the set of core chains from the contract addresses constant in the SDK. - 96485144a: SDK support for ICA deployment and operation. - 4e7a43be6: Replace Debug logger with Pino ### Patch Changes - 5373d54ca: Add --log and --verbosity settings to CLI - Updated dependencies [`96485144a`] - Updated dependencies [`38358ecec`] - Updated dependencies [`ed0d4188c`] - Updated dependencies [`4e7a43be6`] - @hyperlane-xyz/utils@3.10.0 - @hyperlane-xyz/sdk@3.10.0 ## @hyperlane-xyz/helloworld@3.10.0 ### Minor Changes - 96485144a: SDK support for ICA deployment and operation. - 4e7a43be6: Replace Debug logger with Pino ### Patch Changes - Updated dependencies [`96485144a`] - Updated dependencies [`38358ecec`] - Updated dependencies [`ed0d4188c`] - Updated dependencies [`4e7a43be6`] - @hyperlane-xyz/sdk@3.10.0 - @hyperlane-xyz/core@3.10.0 ## @hyperlane-xyz/sdk@3.10.0 ### Minor Changes - 96485144a: SDK support for ICA deployment and operation. - 38358ecec: Deprecate Polygon Mumbai testnet (soon to be replaced by Polygon Amoy testnet) - ed0d4188c: Fixed an issue where warp route verification would fail at deploy time due to a mismatch between the SDK's intermediary contract representation and actual contract name. Enabled the ContractVerifier to pick up explorer API keys from the configured chain metadata. This allows users to provide their own explorer API keys in custom `chains.yaml` files. - 4e7a43be6: Replace Debug logger with Pino ### Patch Changes - Updated dependencies [`96485144a`] - Updated dependencies [`38358ecec`] - Updated dependencies [`4e7a43be6`] - @hyperlane-xyz/utils@3.10.0 - @hyperlane-xyz/core@3.10.0 ## @hyperlane-xyz/utils@3.10.0 ### Minor Changes - 96485144a: SDK support for ICA deployment and operation. - 4e7a43be6: Replace Debug logger with Pino ## @hyperlane-xyz/ccip-server@3.10.0 ### Minor Changes - 96485144a: SDK support for ICA deployment and operation. ## @hyperlane-xyz/infra@3.10.0 ### Minor Changes - 96485144a: SDK support for ICA deployment and operation. - 38358ecec: Deprecate Polygon Mumbai testnet (soon to be replaced by Polygon Amoy testnet) - 4e7a43be6: Replace Debug logger with Pino ### Patch Changes - Updated dependencies [`96485144a`] - Updated dependencies [`38358ecec`] - Updated dependencies [`ed0d4188c`] - Updated dependencies [`4e7a43be6`] - @hyperlane-xyz/helloworld@3.10.0 - @hyperlane-xyz/utils@3.10.0 - @hyperlane-xyz/sdk@3.10.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	7 months ago
Kunal Arora	d792309b8d	feat: govern using ICAs (#3381 ) ### Description - Add inferICAEncodedSubmissionType for submitting transactions through ICA routers ### Drive-by changes - SafeUrl doesn't throw for chains we don't have safe service for. (bc while checking for native SubmissionType.SAFE we'll still check) ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3199 ### Backward compatibility Yes ### Testing Unit tests --------- Signed-off-by: Paul Balaji <paul@hyperlane.xyz> Co-authored-by: Paul Balaji <paul@hyperlane.xyz> Co-authored-by: J M Rossy <jm.rossy@gmail.com> Co-authored-by: Trevor Porter <trkporter@ucdavis.edu> Co-authored-by: Daniel Savu <23065004+daniel-savu@users.noreply.github.com>	7 months ago
Noah Bayindirli 🥂	38358ececd	feat: deprecate Mumbai testnet (#3521 ) ### Description - Removes all reference to Mumbai testnet, since it is soon being [deprecated](https://polygon.technology/blog/polygon-pos-is-cooking-the-napoli-upgrade-means-better-ux-the-mumbai-testnet-takes-a-bow) by the Polygon team - Monorepo docker tag: https://console.cloud.google.com/gcr/images/abacus-labs-dev/global/hyperlane-monorepo@sha256:d4b44359cae9c4e3bdeb6f965c59d056f7fce72c42069adc0dea038ac600785a/details?authuser=5&project=abacus-labs-dev&tab=info - Agent docker tag: https://console.cloud.google.com/gcr/images/abacus-labs-dev/global/hyperlane-agent@sha256:a578d96f7f06721d0b6cd8095d6a1fa5d22f01b59eba3320ee3b1fe34ca3c5df/details?authuser=5&project=abacus-labs-dev&tab=info ### Drive-by changes - Adds missing Testnet domains, Fuji & BSC Testnet - Fix for failing `test-rs` CI check with ``` error[E0004]: non-exhaustive patterns: `chain::KnownHyperlaneDomain::Fuji` and `chain::KnownHyperlaneDomain::BinanceSmartChainTestnet` not covered --> hyperlane-core/src/utils.rs:226:15 \| 226 \| match $v { \| ^^ patterns `chain::KnownHyperlaneDomain::Fuji` and `chain::KnownHyperlaneDomain::BinanceSmartChainTestnet` not covered ``` ### Related issues - Dependency on #3523 - Fixes #1181 ### Backward compatibility - [x] Backwards compatible - [x] Requires docker image tags to be added post-build - [x] Requires agent artifact cleanup in cloud account: https://www.notion.so/hyperlanexyz/Runbook-83c755f2652943289cf98cd1309487a8?pvs=4#77730653a12f409dacfbd427cab545d3 ### Testing * Build success * `yarn hyperlane chains list -e testnet` does not return `mumbai` * fork.sh script success locally	7 months ago
Daniel Savu	9b11f327c5	Range retries in watermark cursor (#3500 ) ### Description Changes the logic in the watermark cursor, to update the range in the `update` method rather than in `get_next_range`. This means that RPC errors won't result in ranges being skipped, so IGP indexing should be more reliable. ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - First in a sequence of many, for https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3264 ### 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 -->	7 months ago
Kunal Arora	96485144a4	feat: ICA Router deployment on all core mainnet and testnet chains (#3493 ) ### Description - deployed InterchainAccountIsm and InterchainAccountRouter on all chains ### Drive-by changes - strongly ordered artifacts ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3475 ### Backward compatibility Yes ### Testing None --------- Signed-off-by: Paul Balaji <paul@hyperlane.xyz> Co-authored-by: Paul Balaji <paul@hyperlane.xyz> Co-authored-by: J M Rossy <jm.rossy@gmail.com> Co-authored-by: Trevor Porter <trkporter@ucdavis.edu> Co-authored-by: Daniel Savu <23065004+daniel-savu@users.noreply.github.com>	7 months ago
Kunal Arora	769f57d283	feat:ICA support in SDK (#3483 ) ### Description - Adding 'deployAccount` and `getCallRemote` helpers in InterchainAccount.ts for ease of use for the governor - Adding resolveAccountOwner/resolveInterchainAccountAsOwner wherever it's ambiguous if the owner is address (status quo) or AccountConfig (from this PR) - Added icaApp to HyperlaneDeployer for easier access to ICA ownership for any deployer - resolveAccountOwner vs resolveInterchainAccountAsOwner: the former is usable outside the deployers like the checker, etc whereas the latter is where we're already using the deployer and have the required localRouter already cached - includes the formatting change for the account verification file - owner needs casting in infra/config because of the type Address \| AccountConfig type (cannot use resolveAccountOwner here which requires multiprovider) - Add quoteGasPayment with gas limit override to the ICA router contract ### Drive-by changes - HyperlaneDeployer.cacheAddressesMap appends addresses two keys deep instead of overridding the whole cache - callData in utils now supports value to be compatible with CallData[] in the ICA Router contract and generally for V3 which allows msg.value on dispatch - `appFromAddressesMapHelper` doesn't intersect multiprovider with contractMap chains (this causes issues if the contracts map doesn't include chains we may want to read something like domainId from like ismfactory or ICADeployer) - HyperlaneHookDeployer is now using the owner as owner vs it was earlier using the deployer earlier for unknown reason - ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3505 ### Backward compatibility No (call value) ### Testing Unit testing/e2e testing through governor --------- Signed-off-by: Paul Balaji <paul@hyperlane.xyz> Co-authored-by: Paul Balaji <paul@hyperlane.xyz> Co-authored-by: J M Rossy <jm.rossy@gmail.com> Co-authored-by: Trevor Porter <trkporter@ucdavis.edu> Co-authored-by: Daniel Savu <23065004+daniel-savu@users.noreply.github.com>	7 months ago
Daniel Savu	00fcaf74db	fix: warn on tx reverts; log cosmos tx results (#3497 ) ### 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 -->	7 months ago
Daniel Savu	57e4a8acd9	relayer image with half the timeout for eth txs (#3511 ) ### 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 -->	7 months ago
Trevor Porter	9b06f3bfe1	Different key funder job name (#3506 ) ### Description - My changes in #3491 / #3492 were kind of accurate - according to https://github.com/prometheus/pushgateway/issues/65 even using pushAdd will displace existing metrics. It's all very confusing! - I tested this with a script that pushed some test metrics to the push gateway - basically by having the key funder use a different job name than the mainnet2 one, the metrics each of them push won't conflict with one another ### 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 -->	7 months ago
Noah Bayindirli 🥂	2093fe48fd	add 'mumbai' to chainsToSkip (#3523 ) ### Description - Adds `mumbai` to `chainsToSkip` as a preliminary step for deprecating Polygon Mumbai testnet ### Related Issues - Unblocks #3521 - Fixes #1181	7 months ago
Noah Bayindirli 🥂	d00500f505	update codeowners for @nbayindirli (#3522 ) ### Description * Updated codeowners for @nbayindirli	7 months ago
Lee	db85f8aaf4	Upgradable warp routes (#3474 ) ### Description Makes the following Warp Routes upgradable through CLI deployment ``` - FastHypERC20Collateral - FastHypERC20 - HypERC20 - HypERC20Collateral - HypERC20CollateralVaultDeposit - HypNative - HypNativeScaled - HypERC721Collateral - HypERC721 - HypERC721URICollateral - HypERC721URIStorage ``` - Adds `initialize()` to each contract - It mostly contains `_MailboxClient_initialize`, and any additional proxy specific constructor logic - Refactors - Update `GasRouterDeployer` to inherit from `ProxiedRouterDeployer` - Update `ProxiedRouterDeployer.routerContractName` to `abstract ProxiedRouterDeployer.routerContractName(): RouterKey` . - This allows child classes to specify their own contract name instead of being locked-in to a single name upon construction. Similar concept to the existing `ProxiedRouterDeployer.constructorArgs()` and `ProxiedRouterDeployer.initializeArgs()` - Update `router()` - Add function into `InterchainQueryDeployer` - Add function into `InterchainAccountDeployer` - Update to abstract function in `ProxiedRouterDeployer` - ### Drive-by changes ### Related issues Fixes #999 ### Backward compatibility - Should be backward compatible ### Testing - Updates contract unit tests - Manual testing through CLI and verified contracts	7 months ago
J M Rossy	5373d54ca5	Add global log options to CLI (#3519 ) ### Description - Add global log options to CLI - Improve consistency with agent log options - Other minor log-related cleanup ### Related issues Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3499 ### Backward compatibility Yes because the new log options haven't yet published	7 months ago
Kunal Arora	41cc7f5c4b	fix: config fallback as default on fuji (#3501 ) ### Description - default hook was misconfigured to a routing whereas it should have been a fallback routing hook ### Drive-by changes LOG_PRETTY=true in CI ### Related issues - https://discord.com/channels/935678348330434570/935678739663192184/1222618018098581575 ### Backward compatibility Yes ### Testing Manual through cast	7 months ago
Paul Balaji	ed0d4188c1	fix: add changeset for warp verify fix (#3513 )	7 months ago
Paul Balaji	3ec81081c6	feat: CLI chain list derived from SDK contract addresses artifact (#3514 )	7 months ago
Daniel Savu	ff6b06079e	Half the relayer timeout on v3 (#3508 ) ### Description V3 counterpart of https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3431 Co-authored-by: nambrot <nambrot@googlemail.com>	7 months ago
Paul Balaji	a9881dc128	fix: warp route deployment verification (#3494 )	7 months ago
J M Rossy	4e7a43be6a	Logging overhaul (#3481 ) ### Description - Replace use of debug lib with Pino - Replace `loggerName` params with Logger types - Update SDK Readme ### Related issues Fixes https://github.com/hyperlane-xyz/issues/issues/918 ### Backward compatibility No, breaks anyone passing in custom logger to SDK classes, which is likely no one ### Testing - Tested in CLI - Tested in Warp UI	7 months ago
Kunal Arora	4f0ea4361e	feat: add quoteGasPayment to ICA router (#3460 ) ### Description - for easier offchain use, we can directly call the ICA router to fetch the quote needed for the dispatch. ### Drive-by changes None ### Related issues None ### Backward compatibility Yes ### Testing Unit	7 months ago
github-actions[bot]	1af0babdec	Version Packages (#3489 ) # Releases ## @hyperlane-xyz/cli@3.9.0 ### Minor Changes - 11f257ebc: Add Yield Routes to CLI ### Patch Changes - Updated dependencies [`11f257ebc`] - @hyperlane-xyz/sdk@3.9.0 - @hyperlane-xyz/utils@3.9.0 ## @hyperlane-xyz/sdk@3.9.0 ### Minor Changes - 11f257ebc: Add Yield Routes to CLI ### Patch Changes - @hyperlane-xyz/core@3.9.0 - @hyperlane-xyz/utils@3.9.0 ## @hyperlane-xyz/core@3.9.0 ### Patch Changes - @hyperlane-xyz/utils@3.9.0 ## @hyperlane-xyz/helloworld@3.9.0 ### Patch Changes - Updated dependencies [`11f257ebc`] - @hyperlane-xyz/sdk@3.9.0 - @hyperlane-xyz/core@3.9.0 ## @hyperlane-xyz/utils@3.9.0 ## @hyperlane-xyz/infra@3.9.0 ### Patch Changes - Updated dependencies [`11f257ebc`] - @hyperlane-xyz/sdk@3.9.0 - @hyperlane-xyz/helloworld@3.9.0 - @hyperlane-xyz/utils@3.9.0 ## @hyperlane-xyz/ccip-server@3.9.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	7 months ago
Yorke Rhodes	ba6ab2ce37	Update static-analysis.yml (#3480 ) ### Description - Updates slither static analysis to run on main for use with github code scanning	7 months ago
Trevor Porter	3b520640d7	Don't overwrite pushgateway metrics, shift mainnet3 cron schedule (#3491 ) ### Description Copying from my Discord thread https://discord.com/channels/935678348330434570/1222226637026885652 > Instead of pushing new metrics to the pushgateway and allowing any existing metrics that exist there to stay there, we replace any existing metrics > We use `.push` instead of `.pushAdd` here `258bf85e43/typescript/infra/src/utils/metrics.ts (L29)` > And because we run two key funders on the mainnet cluster, the mainnet3 key funder metrics compete with the mainnet2 key funder metrics > We start them on the same cron job frequency I guess, but we have more keys on mainnet3 so it typically takes longer than the mainnet2 one, so the mainnet3 metrics tend to overwrite the mainnet2 ones > Wonder if we should start them at diff times for less nonce contention risk anyways > For posterity, I found this by port-forwarding to the push gateway ``` kubectl port-forward prometheus-pushgateway-587c8dc779-294wv 9091 -n monitoring ``` > Where I found only mainnet3 metrics at localhost:9091/metrics ``` # HELP hyperlane_wallet_balance Current balance of eth and other tokens in the `tokens` map for the wallet addresses in the `wallets` set # TYPE hyperlane_wallet_balance gauge hyperlane_wallet_balance{chain="arbitrum",hyperlane_context="hyperlane",hyperlane_deployment="mainnet3",instance="",job="key-funder",token_name="Native",token_symbol="Native",wallet_address="0xa7ECcdb9Be08178f896c26b7BbD8C3D4E844d9Ba",wallet_name="key-funder"} 9.10653822887378 ``` > even though the push gateway had been running for days So this PR: * Shifts the cron schedule for key funder by 30 mins to avoid nonce clobberring with the mainnet2 key funder * moves to by default not overwriting existing metrics I'll do a similar PR for v2 to stop overwriting existing metrics ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues Related: https://github.com/hyperlane-xyz/issues/issues/1141 ### 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 -->	7 months ago
Daniel Savu	6e39cf01af	Relayer retry endpoints (#3476 ) ### Description Adds a `/message_retry` relayer endpoint, which supports retrying OpQueue operations either by ID or by destination domain. Such a request will be sent to an `mpmc` channel's receiving end in the OpQueue, which is emptied when `OpQueue::pop` is called. Example calls: ``` GET http://127.0.0.1:60843/message_retry?destination_domain=42 GET http://127.0.0.1:60843/message_retry?message_id=0x46910b1329ee53c86a023b322e9ca1c17e5f9f0bee789c77b0abced0a173d714 ``` If the endpoint is called specifying both filters, two requests will be sent across the channel, one for each condition. Efficiency note: The entire queue is iterated over if there's at least one retry request in the channel. The good thing is that rebuilding the heap is `O(n)` so not too bad. ### Drive-by changes - Removed the usage of `enum_dispatch`, because it would have made unit tests messy. The drawback is that we have to work around object safety restrictions in `PendingOperation` - for instance it can't be cloned (but can be stored behind an `Arc` if we ever need this). - Added new methods to `PendingOperation`, either to match by ID, or to implement heap element prioritization without depending on the concrete `PendingMessage` type (as was done before). Additions: `id()`, `origin_domain()`, `priority()`. Don't think this conflicts with any operations we may add in the future (e.g. gas oracle updates). - Although `tokio`'s broadcast channel is multi-producer-multi-consumer by default, the consumer end isn't `Clone` - you instead need to have a producer to call `.subscribe()` on to get a new consumer, so I added an `MpmcChannel` struct to encapsulate keeping a producer around to get new consumers. - OpQueue is moved into its own file and has unit tests added for retries (covering broadcast to multi-queue, and both retry types). - Did a bit of agent `server `cleanup, including `EigenNodeApi` ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3098 ### Backward compatibility Yes ### Testing Unit tests for the server route (channel transmitter logic) and for the OpQueue retries (channel receiver logic).	7 months ago
Paul Balaji	258bf85e43	feat: migrate CLI send transfer command to WarpCore (#3470 )	7 months ago
Lee	11f257ebc6	Add changeset for yield route post merge (#3488 ) ### 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 -->	7 months ago
J M Rossy	adab1bec0c	Add code spellcheck CI job (#3467 ) ### Description Fix spelling mistakes and create codespell CI job. An extension of #3422 with the remaining mistakes fixed ### Backward compatibility Yes --------- Co-authored-by: miles <66052478+miles-six@users.noreply.github.com> Co-authored-by: Paul Balaji <paul@hyperlane.xyz>	7 months ago
J M Rossy	7913d7224e	Fix CLI e2e issue due to TestRecipient ISM (#3487 ) ### Description Fix issue with TestRecipient deployment introduced in #3360 ### Drive-by changes Skip SmartProvider tests ### Backward compatibility Yes	7 months ago
Yorke Rhodes	77de7abdd4	Configure additional onchain governance safeguards (#3360 ) ### Description - Set validator announce owner to deployer to minimize effective governance changes following https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3315 ### Drive-by changes - Remove special case hack in the core checker for proxy admin timelock ownership ### Related issues - Followup on https://github.com/hyperlane-xyz/issues/issues/813 ### Backward compatibility Yes ### Testing Env Tests	7 months ago
Paul Balaji	d535e66297	fix: proxy factory impl names (#3471 )	7 months ago
Yorke Rhodes	a153a034c4	Fix viction USDT address (#3473 ) ### Description Somehow the wrong viction USDT address was in the address artifacts	7 months ago
Kunal Arora	d224c060d4	fix: send_value fuzz test for ICA (#3469 ) ### Description make sure we assume `value <= balance - gasQuote` in ICA tests ### Drive-by changes none ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3468 ### Testing fuzz	7 months ago
Trevor Porter	fcb5f798ad	Only run 1 injective validator (#3443 ) ### 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 -->	7 months ago
Daniel Savu	140e3c4bb5	fix: neutron grpc url default; url parsing error message (#3466 ) ### Description The default neturon grpc url is plaintext but it was using a `http` prefix so all requests would fail ### 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 -->	7 months ago
Trevor Porter	176e710cae	Fix BSC gas price issues by treating chains with a base fee of 0 as non-1559 (#3462 ) ### Description - Fixes #3396 - See v2 backport here #3463 So turns out this is because: - BSC nodes tend to enforce a minimum gas price of 3 gwei when you submit a tx - it's possible for validators to include privileged txs at a lower gas price, so in practice (probably some mev stuff ?) there are a bunch of txs in blocks with transactions lower than 3 gwei - BSC's 1559 situation is they have a base fee of zero, so it's basically like they just use legacy txs - when we try to figure out what to pay in prio fees, we are suggested a 1 gwei priority fee: ``` $ cast rpc eth_feeHistory 10 latest "[5.0]" --rpc-url https://rpc.ankr.com/bsc {"oldestBlock":"0x23706f7","reward":[["0x3b9aca00"]],"baseFeePerGas":["0x0","0x0"],"gasUsedRatio":[0.1149265]} $ cast td 0x3b9aca00 1000000000 ``` So options are: 1. tx overrides for bsc, set it to 3 gwei 2. use a different eip 1559 estimator and set the percentile used in eth_feeHistory to something higher. Atm the percentile is 5%, if you change this to 50% we seem to get 3 gwei. This would have consequences for other chains tho 3. another heuristic, to fall back to legacy txs (where we can trust the eth_gasPrice to give us an accurate price) whenever the base fee is 0 I'm a tx override hater and we don't have this in the agents so far so I'm gonna go with 3. It's the least intrusive change	7 months ago
Kunal Arora	59e89afc5c	feat: add account -> owner mapping in ICA router (#3447 ) ### Description - added accountOwner mapping to the ICA router for easier tracking of remote owners for the transaction type inference by the AppGovernor ### Drive-by changes none ### Related issues none ### Backward compatibility yes ### Testing unit	7 months ago
Yorke Rhodes	5514ab1deb	Generalize matching list agent config fn (#3458 ) ### Description Generalizes `routerMatchingList` to `matchingList` for use with asymmetric app artifacts ### Drive-by changes - migrate to `matchingList` for some app context agent config ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3441 ### Backward compatibility - Yes ### Testing Unit tests	7 months ago
Lee	dcb67e97da	Token deployer yb route (#3435 ) ### Description Adds yield-bearing warp routes to CLI `create` and `deploy` ### Drive-by changes - hyperlane config create warp - Add logic to prompt user `Do you want this warp route to be yield-bearing (i.e. deposits into ERC-4626 vault)?` - If yes - Prompt `Enter the ERC-4626 vault address` - Otherwise, `Enter the collateral token address` - warp-token will be created with `base.address` set to the vault address - Updated prompt flow ``` Select base chain with the original token to warp sepolia? Are you creating a route for the native token of the base chain (e.g. Ether on Ethereum)? no Is this an NFT (i.e. ERC-721)? no Do you want this warp route to be yield-bearing (i.e. deposits into ERC-4626 vault)? // If yes Enter the ERC-4626 vault address // If not a warp route Enter the collateral token address ``` - hyperlane deploy warp - Adds logic to check if `base.type == collateralVault`, make sure that `base.address` exists (and not address(0)). - Deploys `HypERC20CollateralVaultDeposit.sol` using `base.address` - Update example/warp-route-deployment.yaml - Made some quality of life fixes - Add more details to logs - Add `yarn dev` in sdk to use `tsc --watch`. Similar to what's in the cli ### Related issues #3416 ### Backward compatibility Yes ### Testing Use this mock vault: 0xa2ecc6478d0aa9f4423a118c9a2d2b4bcf178a5b Manual/Unit Tests	8 months ago
github-actions[bot]	0338f81116	Version Packages (#3444 ) # Releases ## @hyperlane-xyz/core@3.8.2 ### Patch Changes - @hyperlane-xyz/utils@3.8.2 ## @hyperlane-xyz/cli@3.8.2 ### Patch Changes - bfc2b792b: Fix bug with HypCollateral warp route deployments - @hyperlane-xyz/sdk@3.8.2 - @hyperlane-xyz/utils@3.8.2 ## @hyperlane-xyz/helloworld@3.8.2 ### Patch Changes - @hyperlane-xyz/core@3.8.2 - @hyperlane-xyz/sdk@3.8.2 ## @hyperlane-xyz/sdk@3.8.2 ### Patch Changes - @hyperlane-xyz/core@3.8.2 - @hyperlane-xyz/utils@3.8.2 ## @hyperlane-xyz/utils@3.8.2 ## @hyperlane-xyz/infra@3.8.2 ### Patch Changes - @hyperlane-xyz/helloworld@3.8.2 - @hyperlane-xyz/sdk@3.8.2 - @hyperlane-xyz/utils@3.8.2 ## @hyperlane-xyz/ccip-server@3.8.2 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	8 months ago
J M Rossy	bfc2b792be	Fix bug with HypCollateral warp route deployments (#3442 ) ### Description - Fix incorrect adapter use in CLI's warp route deployment - Add a warp collateral deployment to cli e2e test ### Related issues Fixes https://github.com/hyperlane-xyz/issues/issues/1146 ### Backward compatibility Yes ### Testing Tested manually and via new e2e test coverage	8 months ago
Daniel Savu	3adc0e91ce	chore: add viction warp route labels to mainnet relayer (#3438 ) ### Description The prepare queue alert will automatically pick up viction if warp route labels are set. ### 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 -->	8 months ago
Daniel Savu	059bc9624f	chore: release relayers with op-queue labels (#3433 ) ### Description Follow-up to https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3415#issue-2183782377, to actually deploy with the labels ### 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 -->	8 months ago
Kunal Arora	d90dc92b22	fix: correctly recover the warp route router from artifacts (#3379 ) ### Description - Writing and read to cache as the [token.type]: address. NOTE: this breaks if the agents index by {router: address} for warp routes but can we easily fixed by checking for any of the tokenTypes Ideally, we want a multi-key artifact like { sepolia: [{type:synthetic, standard:erc20, name: 'USD Coin', address: 0x1233..}],} but that's more scope than intended for this issue. cc @daniel-savu @tkporter ### Drive-by changes None ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3296 ### Backward compatibility Yes ### Testing Manual	8 months ago
github-actions[bot]	8a216c116e	Version Packages (#3427 ) # Releases ## @hyperlane-xyz/core@3.8.1 ### Patch Changes - Updated dependencies [`5daaae274`] - @hyperlane-xyz/utils@3.8.1 ## @hyperlane-xyz/cli@3.8.1 ### Patch Changes - Updated dependencies [`5daaae274`] - @hyperlane-xyz/utils@3.8.1 - @hyperlane-xyz/sdk@3.8.1 ## @hyperlane-xyz/helloworld@3.8.1 ### Patch Changes - Updated dependencies [`5daaae274`] - @hyperlane-xyz/sdk@3.8.1 - @hyperlane-xyz/core@3.8.1 ## @hyperlane-xyz/sdk@3.8.1 ### Patch Changes - 5daaae274: Prevent warp transfers to zero-ish addresses - Updated dependencies [`5daaae274`] - @hyperlane-xyz/utils@3.8.1 - @hyperlane-xyz/core@3.8.1 ## @hyperlane-xyz/utils@3.8.1 ### Patch Changes - 5daaae274: Prevent warp transfers to zero-ish addresses ## @hyperlane-xyz/infra@3.8.1 ### Patch Changes - Updated dependencies [`5daaae274`] - @hyperlane-xyz/utils@3.8.1 - @hyperlane-xyz/sdk@3.8.1 - @hyperlane-xyz/helloworld@3.8.1 ## @hyperlane-xyz/ccip-server@3.8.1 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	8 months ago
J M Rossy	5daaae274d	Prevent warp transfers to zero-ish addresses (#3426 ) ### Description - Prevent warp transfers to zero-ish addresses - Increase address utility test coverage ### Related issues Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3421 ### Backward compatibility Yes ### Testing Tested in warp UI and added unit tests	8 months ago
Daniel Savu	a72c3cf1a5	feat: parse warp route artifacts with token-specific key names (#3420 ) ### Description Looks like all warp route artifacts until now used to have keys named `router`. The new artifacts (for USDC and USDT, inevm <> EVM) have their keys named according to the token type (e.g. `HypERC20`, `HypERC20Collateral` etc). This adds a script to parse such files, and updates agent images to deploy with these warp route app_context labels. ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3415 - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3397 ### 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? Manual on RC, by disabling the whitelist and applying the same `metricAppContexts` as for the hyperlane context: ``` hyperlane_submitter_queue_length{agent="relayer",app_context="injective_inevm_inj",hyperlane_baselib_version="0.1.0",queue_name="confirm_queue",remote="injective"} 9 hyperlane_submitter_queue_length{agent="relayer",app_context="injective_inevm_inj",hyperlane_baselib_version="0.1.0",queue_name="prepare_queue",remote="injective"} 0 hyperlane_submitter_queue_length{agent="relayer",app_context="inevm_ethereum_usdc",hyperlane_baselib_version="0.1.0",queue_name="confirm_queue",remote="inevm"} 7 hyperlane_submitter_queue_length{agent="relayer",app_context="inevm_ethereum_usdc",hyperlane_baselib_version="0.1.0",queue_name="prepare_queue",remote="inevm"} 1 hyperlane_submitter_queue_length{agent="relayer",app_context="inevm_ethereum_usdt",hyperlane_baselib_version="0.1.0",queue_name="confirm_queue",remote="inevm"} 10 hyperlane_submitter_queue_length{agent="relayer",app_context="inevm_ethereum_usdt",hyperlane_baselib_version="0.1.0",queue_name="prepare_queue",remote="inevm"} 0 ```	8 months ago
Lee	ae0990a0b3	LayerZero Hook and ISM (#3102 ) ### Description - Implements LayerZero V1 and V2 hook with V2 ISM. - V2 ISM is backwards compatible i.e., V1 hook (which uses V1 endpoint to send) can send to V2 ISM (which uses V2 endpoint to receive). See [here](https://docs.layerzero.network/explore/migration#configuring-ultralightnode301) for configuration. - V2 uses `AbstractsMessageIdAuthorized*`. In. other words, hook passes messageId through LayerZero, which stores into ISM to be used when relayer calls `verify()` . - Includes unit test for both V1 and V2 hook and ISM. - V1 uses official LayerZero endpoint mock. ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Implements #2853 ### Backward compatibility Yes ### Testing Manual/Unit Tests	8 months ago
Lee	b379336b91	Yield-earning Warp Routes with ERC4626 (#3076 ) ### Description Integrates ERC4626 compatible vaults. This PR assumes that the vault `asset` is the same as `wrappedToken` - `_transferFromSender()` deposits into the vault - `_transferTo()` withdraws from the vault - `sweep()` redeems excess shares for the vault asset - Uses internal `assetDeposited` store to keep track of assets deposited. Used to calculate excess shares to be withdrawn by owner - Makes minor changes to existing test files to allow new tests to inherit ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Implements #2450 ### Backward compatibility Yes ### Testing Manual/Unit Tests --------- Co-authored-by: Yorke Rhodes <email@yorke.dev>	8 months ago

1 2 3 4 5 ...

2151 Commits (c900da1877e58274c5c0b8d89d9f4869f7ee93d4) All Branches Search

2151 Commits (c900da1877e58274c5c0b8d89d9f4869f7ee93d4)

All Branches