2650 Commits (6e787a9b3964a4892674f095709557b19763dc41)

 

All Branches   

Search

Author	SHA1	Message	Date
J M Rossy	78b77eecff	Fixes for CLI dry-runs (#3713) ... ### Description - Fixes type of dry-run arg in deploy command definitions - Runs verifyAnvil during dry-run context setup	7 months ago
Daniel Savu	8e5ef272a6	fix: agent config check, run relayer on mantapacific (#3714) ... ### 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
github-actions[bot]	6f9c7511c7	Version Packages (#3533) ... 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.11.0 ### Minor Changes - b6fdf2f7f: Implement XERC20 and FiatToken collateral warp routes - b63714ede: Convert all public hyperlane npm packages from CJS to pure ESM ### Patch Changes - Updated dependencies [b63714ede] - Updated dependencies [2b3f75836] - Updated dependencies [af2634207] - @hyperlane-xyz/utils@3.11.0 ## @hyperlane-xyz/cli@3.11.0 ### Minor Changes - f8b6ea467: Update the warp-route-deployment.yaml to a more sensible schema. This schema sets us up to allow multi-chain collateral deployments. Removes intermediary config objects by using zod instead. - b6fdf2f7f: Implement XERC20 and FiatToken collateral warp routes - aea79c686: Adds single-chain dry-run support for deploying warp routes & gas estimation for core and warp route dry-run deployments. - 917266dce: Add --self-relay to CLI commands - b63714ede: Convert all public hyperlane npm packages from CJS to pure ESM - 450e8e0d5: Migrate fork util from CLI to SDK. Anvil IP & Port are now optionally passed into fork util by client. - 3528b281e: Restructure CLI params around registries - af2634207: Introduces `hyperlane hook read` and `hyperlane ism read` commands for deriving onchain Hook/ISM configs from an address on a given chain. ### Patch Changes - 8246f14d6: Adds defaultDescription to yargs --key option. - Updated dependencies [811ecfbba] - Updated dependencies [f8b6ea467] - Updated dependencies [d37cbab72] - Updated dependencies [b6fdf2f7f] - Updated dependencies [a86a8296b] - Updated dependencies [2db77f177] - Updated dependencies [3a08e31b6] - Updated dependencies [917266dce] - Updated dependencies [aab63d466] - Updated dependencies [2e439423e] - Updated dependencies [b63714ede] - Updated dependencies [3528b281e] - Updated dependencies [450e8e0d5] - Updated dependencies [2b3f75836] - Updated dependencies [af2634207] - @hyperlane-xyz/sdk@3.11.0 - @hyperlane-xyz/utils@3.11.0 ## @hyperlane-xyz/helloworld@3.11.0 ### Minor Changes - b63714ede: Convert all public hyperlane npm packages from CJS to pure ESM ### Patch Changes - Updated dependencies [811ecfbba] - Updated dependencies [f8b6ea467] - Updated dependencies [d37cbab72] - Updated dependencies [b6fdf2f7f] - Updated dependencies [a86a8296b] - Updated dependencies [2db77f177] - Updated dependencies [3a08e31b6] - Updated dependencies [917266dce] - Updated dependencies [aab63d466] - Updated dependencies [2e439423e] - Updated dependencies [b63714ede] - Updated dependencies [3528b281e] - Updated dependencies [450e8e0d5] - Updated dependencies [af2634207] - @hyperlane-xyz/sdk@3.11.0 - @hyperlane-xyz/core@3.11.0 ## @hyperlane-xyz/sdk@3.11.0 ### Minor Changes - 811ecfbba: Add EvmCoreReader, minor updates. - f8b6ea467: Update the warp-route-deployment.yaml to a more sensible schema. This schema sets us up to allow multi-chain collateral deployments. Removes intermediary config objects by using zod instead. - d37cbab72: Adds modular transaction submission support for SDK clients, e.g. CLI. - b6fdf2f7f: Implement XERC20 and FiatToken collateral warp routes - 2db77f177: Added RPC `concurrency` property to `ChainMetadata`. Added `CrudModule` abstraction and related types. Removed `Fuel` ProtocolType. - 3a08e31b6: Add EvmERC20WarpRouterReader to derive WarpConfig from TokenRouter address - 917266dce: Add --self-relay to CLI commands - aab63d466: Adding ICA for governance - b63714ede: Convert all public hyperlane npm packages from CJS to pure ESM - 3528b281e: Remove consts such as chainMetadata from SDK - 450e8e0d5: Migrate fork util from CLI to SDK. Anvil IP & Port are now optionally passed into fork util by client. - af2634207: Moved Hook/ISM config stringify into a general object stringify utility. ### Patch Changes - a86a8296b: Removes Gnosis safe util from infra in favor of SDK - 2e439423e: Allow gasLimit overrides in the SDK/CLI for deploy txs - Updated dependencies [b6fdf2f7f] - Updated dependencies [b63714ede] - Updated dependencies [2b3f75836] - Updated dependencies [af2634207] - @hyperlane-xyz/core@3.11.0 - @hyperlane-xyz/utils@3.11.0 ## @hyperlane-xyz/utils@3.11.0 ### Minor Changes - b63714ede: Convert all public hyperlane npm packages from CJS to pure ESM - af2634207: Moved Hook/ISM config stringify into a general object stringify utility. ### Patch Changes - 2b3f75836: Add objLength and isObjEmpty utils ## @hyperlane-xyz/infra@3.11.0 ### Minor Changes - af2634207: Moved Hook/ISM reading into CLI. ### Patch Changes - a86a8296b: Removes Gnosis safe util from infra in favor of SDK - Updated dependencies [811ecfbba] - Updated dependencies [f8b6ea467] - Updated dependencies [d37cbab72] - Updated dependencies [b6fdf2f7f] - Updated dependencies [a86a8296b] - Updated dependencies [2db77f177] - Updated dependencies [3a08e31b6] - Updated dependencies [917266dce] - Updated dependencies [aab63d466] - Updated dependencies [2e439423e] - Updated dependencies [b63714ede] - Updated dependencies [3528b281e] - Updated dependencies [450e8e0d5] - Updated dependencies [2b3f75836] - Updated dependencies [af2634207] - @hyperlane-xyz/sdk@3.11.0 - @hyperlane-xyz/helloworld@3.11.0 - @hyperlane-xyz/utils@3.11.0 ## @hyperlane-xyz/ccip-server@3.11.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	7 months ago
Yorke Rhodes	b6fdf2f7fe	Implement Connext xERC20 and Circle FiatToken collateral (#3618) ... ### Description - Implement XERC20 Collateral contract - Implement FiatToken Collateral contract ### Drive-by - Move vault collateral extension into token extensions folder ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3486 ### Backward compatibility - Yes ### Testing - Unit tests	7 months ago
Daniel Savu	22f367ff6c	fix: sleep after submitting to cosmos chains (#3699) ... ### 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	5aeb83a2e5	Relayer Message Batching to EVM (#3656) ... ### Description Status: - [x] op-queue scaffolding - [x] hyperlane-ethereum integration with multicall - [x] new config items - [x] actually build batch in the op-queue submit step - [x] e2e tests with batching configured - [x] dynamic batch sizes (batch as many messages as the prepare step has ready) - [x] parallelize metadata building - [ ] proportional IGP deduction ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Fixes #3628 - Fixes #3630 ### 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: Trevor Porter <tkporter4@gmail.com>	7 months ago
J M Rossy	bd6ca01fd4	Fix CLI dry run flag handling (#3698) ... ### Description - Fix dry run flag - Prevent invalid selection in warp config create - Improve logging of warp validation errors - Avoid module-scoped logger in SDK	7 months ago
Noah Bayindirli 🥂	8246f14d6d	add defaultDescription to yargs --key option (#3697) ... ### Description * Adds defaultDescription to yargs --key option to avoid printing sensitive data ### Drive-by changes * None ### Related issues * None ### Backward compatibility * Yes ### Testing * Manual	7 months ago
Noah Bayindirli 🥂	02888359d5	do not exit if @safe-global/protocol-kit/**/Multi_send.ts dne (#3696) ... ### Description * do not exit if `@safe-global/protocol-kit/**/Multi_send.ts` dne * This fixes an issue where successfully building the sdk 2+ times exits out, when instead `tsc` should always be executed ### Drive-by changes * n/a ### Related issues * n/a ### Backward compatibility * yes ### Testing * manual	7 months ago
Noah Bayindirli 🥂	a86a8296b2	export tx provider from sdk & remove safe util from infra (#3694) ... ### Description * Exports new tx provider + Gnosis safe util from SDK * Removes the Gnosis safe util from infra ### Drive-by changes * Reminder to add a changeset * Output: ``` ➜ hyperlane-monorepo-official git:(noah/move-safe) ✗ git commit -m "add changeset reminder to husky script" → No staged files match any configured task. 📝 If you haven't yet, please add a changeset for your changes via 'yarn changeset' [noah/move-safe 3e668d0a7] add changeset reminder to husky script 1 file changed, 2 insertions(+) ``` ### Related issues * Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3684 ### Backward compatibility * Yes ### Testing * n/a	7 months ago
Noah Bayindirli 🥂	d37cbab724	feat: Modular Tx Submission – Create Transformer + Submitter + Builder Abstraction (#3627) ... ## Description - Adds modular transaction submission support for SDK clients, e.g. CLI. To-do: - [ ] Failing CI build due to linting Gnosis Safe package import - [ ] Export to `sdk/src/index.ts` Note: - Built to eventually expand to [Sealevel/CW support](dc62847615/typescript/sdk/src/providers/ProviderType.ts (L51-L85)) ### Transformers - Input: `PopulatedTx[]` - Output: `HTX[]` (where `HTX extends HyperlaneTx`) - Purpose: Given a set of populated transactions, transform those transactions into a set a HyperlaneTxs (for the corresponding submitter), e.g. ``` ... const somePopulatedTxs = ... const transformer = new InterchainAccountTxTransformer(mp,o,d,p); const populatedTxs = transformer.transformTxs(somePopulatedTxs); ``` ### Submitters - Input: `HTX[]` (where `HTX extends HyperlaneTx`) - Output: `TxReceipt[] | ResponseData[]` - Purpose: Given a set of Hyperlane transactions, execute those transactions for the specified submitter (submitter of type HTX should enforce the transactions being passed are of type HTX), e.g. ``` ... const submitter = new GnosisSafeTxSubmitter(mp,c,p); const txReceipts = submitter.submitTxs(populatedTxs); --- Client-side example: for each gnosisTxReceipt display transactionHash ``` ### Builder (Utilizes both Submitters & Transformer) - Input: `(TxTransformer<HTX> | TxTransformerType & Chain) & (TxSubmitter<HTX,HTR> | TxSubmitterType & Chain) & HTX[]` (where `HTX extends HyperlaneTx`) - Output: `TxReceipt[] | *response data*` - Purpose: Given a submitter, an optional transformer, and a set of PopulatedTransactions, transform and submit all transactions, e.g. ``` ... const eV5builder = new TxSubmitterBuilder<EV5Transaction, EV5TransactionReceipt>(); let txReceipts = eV5builder.for( new GnosisSafeTxSubmitter(chainA) ).transform( InterchainAccountTxTransformer(chainB) ).submit( txs ); txReceipts = eV5builder.for( new ImpersonatedAccountTxSubmitter(chainA) ).submit(txs); txReceipts = eV5builder.for( new JsonRpcTxSubmitter(chainC) ).submit(txs); --- Client-side example: for each txReceipt display transactionHash | response data ``` ### Drive-by changes * None ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3547 ### Backward compatibility - Yes ### Testing - Testing through CLI unit testing	7 months ago
J M Rossy	cf727db3d4	Avoid sinon import in exported lib files (#3685)	7 months ago
J M Rossy	3528b281e3	Migrate SDK consts to Registry and use new registry utilities (#3615) ... ### Description - Remove most consts from SDK - Refactor tests that relied on chainMetadata - Remove JSON imports/exports in the SDK - Update the HelloWorld package to read metadata from the registry lib - Update the Infra package to read/write to a LocalRegistry - Update the CLI to read and write from registries ### Drive-by changes - Fix typo in `EvmHypCollateralVault` token standard - Use consistent, newest yaml lib version ### Related issues Fixes https://github.com/hyperlane-xyz/issues/issues/917 Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2810 ### Backward compatibility No: - Several SDK exports like `chainMetadata` have been removed - Common args for the CLI like `--chain` have been replaced with `--registry` and `--overrides`	7 months ago
Yorke Rhodes	292879126c	Ensure owners are configured correctly (#3677) ... ### Description Fixes owner config to be safes ### Backward compatibility Yes	7 months ago
Lee	3a08e31b6d	Derive WarpConfig from TokenRouter address (#3671) ... ### Description Add Reader to derive WarpConfig from TokenRouter address ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Fixes #3579 ### Backward compatibility Yes ### Testing Unit Tests	7 months ago
Paul Balaji	2db77f177f	feat: abstract crud module (#3621)	7 months ago
Trevor Porter	c4b7ad3196	Update Mode and Blast validator sets & gas oracles (#3669) ... ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: nambrot <nambrot@googlemail.com>	7 months ago
Trevor Porter	21cd38c2f3	Update IGP gas oracles with new heuristics, get Cosmos gas prices from registry (#3662) ... ### Description The original and main motivation of this PR was to feel confident when running `deploy.ts -m igp` off of main. Prior to this, running it off main could result in misconfiguring gas oracles, particularly when it came to non-EVM remotes. See https://github.com/hyperlane-xyz/issues/issues/1178 for some context. This PR does a number of things: - Fetches Cosmos gas prices from the Cosmos registry - the `gasPrices.json` now lets you specify the decimals relating to the amount in there. There are 2 reasons for this: it's easier for us to deal with gwei values for EVM chains (as we often end up manually changing these instead of just relying on the script). The second reason is covered in the next bullet - Handles decimals when it comes to gas prices. The existing tooling assumed gas prices would always be denominated in wei. An extra weird situation arises with non-EVM chains: chains like Neutron have gas prices that are quotes in the smallest denomination (ie the equivalent of "wei" for NTRN), but the gas price is not an integer and is very small, e.g. `0.0053`. This poses issues because the IGP contracts require the gas price that's configured onchain to be an integer. Simply rounding up from 0.0053 to 1 results in almost 2 orders of magnitude difference :(. So the solution here is to have some logic that accommodates really tiny gas prices by scaling up the configured gas price and scaling down the configured token exchange rate. - Applies some "non-linear" gas pricing heuristics. See https://github.com/hyperlane-xyz/issues/issues/1204 and https://discord.com/channels/935678348330434570/935678739663192184/1232293417309044818 for some context - Running `update-agent-config.ts` will fetch gas prices for Cosmos chains from the Cosmos registry and ensure they're accurate ### Drive-by changes Some logging messages when applying IGP gas oracle changes to make it more clear what the change actually does ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3386 - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3484 - Fixes https://github.com/hyperlane-xyz/issues/issues/1178 - Fixes https://github.com/hyperlane-xyz/issues/issues/1206 - Fixes https://github.com/hyperlane-xyz/issues/issues/1204 ### Backward compatibility Fully backward compatible ### Testing Ran deploy.ts for the IGP on all chains! --------- Co-authored-by: nambrot <nambrot@googlemail.com>	7 months ago
Paul Balaji	af26342079	feat: add `hyperlane hook read` + `hyperlane ism read` to cli (#3648)	7 months ago
Trevor Porter	d6f25ed035	Deploy to Mode & Blast (#3653) ... ### 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
Lee	f8b6ea467a	CLI warp route deploys do not support ISM configuration (#3611) ... ### Description This PR fixes multiple related issues (see Related issues). The primary changes are 1) Update the warp-route-deployment.yaml to a more sensible [schema](75d590eff8/typescript/cli/examples/fork/warp-route-deployment.yaml). This schema _sets_ us up to allow multi-chain collateral deployments 2) Use zod to define and validate schemas 3) Removes [intermediary config objects](6c42a6458d/typescript/cli/src/deploy/warp.ts (L176-L214)), and completely rely on warp config file ### Drive-by changes - Updates dry run to allow a user to specify what chain to do a dry run on: `hyperlane deploy warp -d sepolia` ### Related issues - Fixes #3479 - Fixes #3135 - Fixes #3188 ### Backward compatibility **Not backwards compatible, warp route schema has changed** ### Testing Manual - used `sh ci-test.sh pi_with_core_chain` to test out create ERC20, ERC721, CollateralVault, Native warp configs - used `sh ci-test.sh pi_with_core_chain` to test out deploy ERC20, ERC721, CollateralVault, Native warp configs Unit Tests - Unit tests added to test out some business logic related to the schema fields	7 months ago
Lee	811ecfbbaf	Derive CoreConfig from Mailbox address (#3657) ... ### Description Creates a new class to derive CoreConfig from Mailbox and their respective hooks and isms ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Fixes #3578 ### Backward compatibility Yes ### Testing Unit Tests through CoreDeployer.hardhat-test.ts	7 months ago
Trevor Porter	6f35e4ce58	Ancient8 key funder; add inevm claim threshold (#3619) ... ### 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	f2cb6ebc1b	refactor: organize files in `hyperlane-ethereum` (#3633) ... ### Description Some cleanup along my way to integrating with `Multicall3` in hyp-ethereum. - Categorizes most files from `src` into `ism`, `contracts`, `signer` modules - Renames the previous `contracts` dir (that held the abi interfaces) to `interfaces`, so we can use `contracts` for the actual contracts (e.g. mailbox, igp)	8 months ago
Nam Chu Hoai	2e439423e7	Allow gasLimit overrides in the SDK/CLI for deploy txs (#3622) ... ### Description Small PR to actually allow overrides of gasLimit --------- Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>	8 months ago
Noah Bayindirli 🥂	450e8e0d55	migrate fork util to SDK (#3625) ... ### Description * Migrates fork util to SDK ### Drive-by changes * None ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3624 ### Backward compatibility * Yes ### Testing * Manual on core & warp	8 months ago
Yorke Rhodes	e10735a718	Fix solidity coverage (#3640)	8 months ago
Lee	a91677a3da	Return entire deployedContracts object (#3617) ... ### Description Returns the deployedContracts object in token deployer ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Fixes #3585 ### 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 --> ### Testing None --------- Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>	8 months ago
Trevor Porter	6c42a6458d	Deploy RC relayer for extra throughput (#3620) ... ### Description See https://discord.com/channels/935678348330434570/1230452070696484956 for context. General idea as a stopgap is to run a relayer concurrent with the Hyperlane one ### 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
Trevor Porter	700240eb8a	Ancient8 new ism, misc infra fixes (#3606) ... ### Description - Deploys ancient8 with a new ISM where we are not quorum - Pulls out warp config to live in a single file / function so that deploy.ts and check-deploy.ts are in sync. Otherwise fork.sh is broken for warp routes - Shuffles around the aw multisig serialization stuff - now they're segmented by environment and context and are written to `config/{env}/aw-validators/{context}.json`. This was in response to some confusing merging logic, see https://discord.com/channels/935678348330434570/1228377321082327141/1229464197297868910 ### Drive-by changes Needed to specify pino to work in pretty mode for warp monitoring :/ this is necessary because pino doesn't work otherwise. After #3582 we should change this ### 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	f4626eb4fe	Allow protocol-specific indexing (#3544) ... ### Description - Generalizes contract syncer hashmaps to store trait objects instead of concrete structs, since both `SequencedDataContractSync` and `WatermarkContractSync` implement `ContractSyncer` - The nice thing this enables is being able to instantiate a different type of syncer for the same contract, for different chain protocols (e.g. for IGP, we can use a sequenced syncer on sealevel and cosmwasm, and a watermark syncer on EVM). - The problem is that `ContractSyncer` is implemented on different trait bounds on `SequencedDataContractSync` and `WatermarkContractSync`. Most notably, the `SequencedDataContractSync` impl bounds the indexed type by the `Sequenced` trait. This means that if a type is to be indexed by more than one syncer strategy, it needs to implement the union of bounds of those strategies - **Blocker:** In the IGP, this means that `InterchainGasPayment` needs to implement `Sequenced` and we have no obvious way of getting that just from the type. Even if the sequence is derived from the type, it has to be a sensible value, since indexing reliability depends on it. - Similar to the point above, we now have `contract_syncs`, a single function that instantiates contract syncs for all chains. Since `contract_syncs` must be able to build a `ContractSyncer` trait obj for all syncer types, it bounds both `T` (the indexed type) and `D` (the log store type) with a union of bounds, so it may be too strict for some types in the future. - The scraper now uses forward-backward indexing instead of just forward indexing, because that simplified the refactor - there's now a convenience trait called `TryFromWithMetrics` that allows adding this bound: `SequenceIndexer<T>: TryFromWithMetrics<ChainConf>,`. This isn't really extendable if we use non-sequence indexers, but it's fine for now since this is used everywhere - replaces the macro-based contract syncer builder with generic fns Still todo: - add new `IndexingDecorator<T>` struct that can wrap `InterchainGasPayment`, so we can use sequence-aware indexing for the IGP - remove sequence logic from the watermark cursor ### 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
Noah Bayindirli 🥂	aea79c686e	feat: add dry-run support for warp deploy + gas stats (#3586) ... ### Description * New feature to allow users to dry-run the warp deploy script against a forked (base/origin) network of their choice * To run: `yarn build && yarn hyperlane deploy warp --dry-run` || `yarn build && yarn hyperlane deploy warp -d` * Externally enables: `hyperlane deploy warp --dry-run` || `hyperlane deploy warp -d` * Also adds gas usage util for both warp & core deployments in all contexts, e.g. * When running a vanilla core deploy, for example, between alfajores and fuji, you will now see: ``` ⛽️ Gas Usage Statistics - Gas required for core deploy on alfajores: 0.0058686745 CELO - Gas required for core deploy on fuji: 0.0239308515 AVAX ``` ### Drive-by changes * None ### Related issues * Fixes https://github.com/hyperlane-xyz/issues/issues/819 ### Backward compatibility * Yes ### Testing * Note: `hl` == `yarn build && yarn hyperlane`. The below tests are only a sample and are not inclusive. #### Manual Testing * With `anvil` NOT running in separate instance: * `hl deploy warp -d` * Throws: ``` Error: No active anvil node detected. Please run `anvil` in a separate instance. ``` * With `anvil` running in separate instance: * `hl deploy warp -d -k c0052e22df5d1f4ae7c51e254Xx00Xx0eb833453eaed6301xXxxx8a30d92d10a` (any private key) * Throws `Error: Invalid address length. Please ensure you are passing an address and not a private key.` * `hl deploy warp -d -k 0x16F4898F47c085C41d7Cc6b1dc0xX0xXX017dcBb` (any public address) * Output: ``` 🔎 Verifying anvil node is running... ✅ Successfully verified anvil node is running Using warp route deployment config at ./configs/warp-route-deployment.yaml No chain config file provided ? Do you want to use some core deployment address artifacts? This is required for PI chains (non-core chains). no Forking alfajores for dry-run... ✅ Successfully forked alfajores for dry-run Impersonating account (0x16F4898F47c085C41d7Cc6b1dc72B91EA617dcBb)... ✅ Successfully impersonated account (0x16F4898F47c085C41d7Cc6b1dc72B91EA617dcBb) ... ✅ Hyp token deployments complete Writing deployment artifacts Deployment is complete! Contract address artifacts are in artifacts/dry-run_warp-route-deployment-2024-04-16-12-27-02.json Warp config is in artifacts/dry-run_warp-config-2024-04-16-12-27-02.json ⛽️ Gas Usage Statistics - Gas required for warp dry-run on alfajores: 0.013310162514578124 CELO Resetting forked network... ✅ Successfully reset forked network ✅ Warp dry-run completed successfully ``` #### CI Testing * Successful CI-backed integration/regression testing via `ci-test.sh`	8 months ago
J M Rossy	2b3f75836a	Add objLength and isObjEmpty util fns (#3605) ... ### Description Add `objLength` and `isObjEmpty` utils ### Related issues Fixes https://github.com/hyperlane-xyz/issues/issues/1199 ### Backward compatibility Yes	8 months ago
Yorke Rhodes	9a32971050	Remove accidental .only and update lint rules (#3614) ... ### Description Removal accidental .only ### Drive-by Update lint rules	8 months ago
Yorke Rhodes	917266dce1	Implement NULL metadata relaying in the SDK/CLI (#3604) ... ### Description - Add NULL self relay to core app - Add self relay to send message command ### Drive-by changes - Migrate to assert util in ISM Factory - Default to `HYP_KEY` in shared key option ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3608 - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3609 - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3452 ### Backward compatibility Yes ### Testing Manual https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/3020995/e44683c3-bca4-41d5-a4c7-45718f05edf4 https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/3020995/50565be1-d266-4d2d-ae27-5fbb5539b93f	8 months ago
Yorke Rhodes	c7007b0561	Implement trusted relayer ISM (#3363) ... ### Description - Adds an ISM that verifies whether the configured trusted relayer is the relayer of the message ### Related issues - Touches https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3371 ### Testing Unit Tests	8 months ago
Paul Balaji	2c3faf778c	feat: derive `IsmConfig` given an ism address (#3580)	8 months ago
Trevor Porter	d3aa3f5cc9	Set prio fee override for moonbeam (#3587) ... ### 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 -->	8 months ago
Trevor Porter	64c8c8ad6d	Update key funder deployments w/ RpcConsensusType.Fallback, fix with ESM (#3583) ... ### Description Making testnet4 and mainnet3 key funder use fallback for consistency & robustness ### Drive-by changes Updated the deployed key funder images	8 months ago
Trevor Porter	26a26f4073	Agent transaction overrides, ensure agent configs are updated in CI (#3563) ... ### Description - Adds some basic transaction overrides for Ethereum chains to be used by the agents. This follows the existing config schema in chain metadata that we have been using on the TS side for a while. The overrides are as follows: - `transactionOverrides.gasPrice` - if specified, non EIP-1559 txs are used, and they use this gasPrice - `transactionOverrides.gasLimit` - if specified, this takes precedence over any gas estimation that's done and is the gas limit that's used for txs. (This is pretty niche and I don't imagine we'll ever wanna use this internally, but happens to cover the use case described [here](https://discord.com/channels/935678348330434570/984123861144600587/1224617234580766741), which is nice to cover) - `transactionOverrides.maxFeePerGas` - if specified and if the chain supports EIP 1559 txs, is used for the `maxFeePerGas` - `transactionOverrides.maxPriorityFeePerGas` - if specified and if the chain supports EIP 1559 txs, is used for the `maxPriorityFeePerGas` - Updates some of the transaction overrides in mainnet3 / testnet4 to be more reasonable now that we'll be using them to submit transactions pretty frequently - Note that atm the transaction overrides are most easily applied to the agents via the config JSONs, and not via our K8s configuration. The upshot of this is if we wanna change a transaction override right now, the easiest way to do it will be to run `update-agent-config.ts` and then build a new image. Created https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3565 to track making this experience better - Part of this change means that it's more important to keep the `transactionOverrides` specified in the SDK / infra up to date with the agent config. So I ended up doing https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3325 along the way, which also required doing https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3311. - To fix the issue with arbitrum blocks, we now require the index.from to be specified in the chain metadata if the chain's technical stack is arbitrum nitro - A new script, `update-agent-config.ts` is added, and it's ran for mainnet3 and testnet4 in CI to make sure there's no diff (similar idea to what we do with prettier) - Along the way I renamed mainnet3_config.json and testnet4_config.json to mainnet_config.json and testnet_config.json. This has been a source of confusion with ppl in the past - in v2 we named them without any numeric suffixes, so we now just do that again ### Drive-by changes - There's a drive-by to poll more frequently for pending transactions (2 seconds). The default is 7 seconds in Ethers, and for many chains that have really quick block times, this may be a way for us to speed up us learning that a transaction is included - Don't enforce gas on the inevm routes, looks like there's some weirdness there that was reported by Nam ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3562 - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3325 - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3311 ### 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
Paul Balaji	e3bf744f4b	feat: derive `HookConfig` given a hook address (#3543)	8 months ago
Noah Bayindirli 🥂	17e48945a1	feat: add dry-run support for core deploy (#3558) ... **Original PR: https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3305** ### Description * New feature to allow users to dry-run the core deploy script against a forked network of their choice * To run: `yarn build && yarn hyperlane deploy core --dry-run` || `yarn build && yarn hyperlane deploy core -d` * Externally enables: `hyperlane deploy core --dry-run` || `hyperlane deploy core -d` ### Drive-by changes * For all touched paths: * Code cleanliness + reuse * Method docs * Minor changes for increased symmetry ### Related issues * Fixes https://github.com/hyperlane-xyz/issues/issues/819 ### Backward compatibility * Yes ### Testing * Note: `hl` == `yarn build && yarn hyperlane`. The below tests are only a sample and are not inclusive. #### Manual Testing * With `anvil` NOT running in separate instance: * `hl deploy core -d` * Throws: ``` Error: No active anvil node detected. Please run `anvil` in a separate instance. ``` * With `anvil` running in separate instance: * `hl deploy core -d --targets alfajores -k c0052e22df5d1f4ae7c51e254Xx00Xx0eb833453eaed6301xXxxx8a30d92d10a` (any private key) * Throws `Error: Invalid address length. Please ensure you are passing an address and not a private key.` * `hl deploy core -d --targets bsctestnet -k 0x16F4898F47c085C41d7Cc6b1dc0xX0xXX017dcBb` (any public address; BSC public RPC endpoint does not support forking) * Output: `⛔️ [dry-run] The current RPC may not support forking. Please consider using a different RPC provider.` * `hl deploy core -d --targets alfajores -k 0x16F4898F47c085C41d7Cc6b1dc0xX0xXX017dcBb` (any public address) * Output: ``` Verifying anvil node is running... Successfully verified anvil node is running ✅ No chain config file provided Forking alfajores for dry-run... Successfully forked alfajores for dry-run ✅ Impersonating account (0x16F4898F47c085C41d7Cc6b1dc72B91EA617dcBb)... Successfully impersonated account (0x16F4898F47c085C41d7Cc6b1dc72B91EA617dcBb) ✅ ... Core contracts deployed Writing agent configs Agent configs written Deployment is complete! Contract address artifacts are in artifacts/dry-run_core-deployment-2024-02-23-15-51-45.json Agent configs are in artifacts/dry-run_agent-config-2024-02-23-15-51-45.json Resetting forked network... Successfully reset forked network ✅ ``` #### CI Testing * Successful CI-backed integration/regression testing via `ci-test.sh` (includes script refactor)	8 months ago
Lee	0090f19e78	Support self-relay with IGP enforced on warp routes (#3566) ... ### Description Adds transferRemote overload ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Fixes #3525 ### Backward compatibility Yes ### Testing Unit Tests	8 months ago
J M Rossy	b63714ede8	Convert packages from CJS to ESM (#3531) ... ### Description - Reconfigure tsconfig and package.json for the utils, core, sdk, and helloworld packages - Update imports to use ESM syntax - Add patch for typechain to address [issue 898](https://github.com/dethcrypto/TypeChain/pull/898) ### Drive-by changes Improve package Readme content ### Related issues Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/1354 ### Backward compatibility No: package consumers using CJS will need to modify their imports or update to ESM. See [this popular gist](https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c#pure-esm-package) for details. ### Testing - [x] CI test coverage which invokes a lot of code via the CLI e2e - [x] Manually test in Warp UI by copying packages - [x] Publish beta packages and test in a few popular bundlers	8 months ago
Daniel Savu	040641bf42	chore: rust ci tests with full backtraces enabled (#3564) ... ### Description Currently there's no way to know exactly where a panic occurred in rust e2e. This adds full backtraces to show where the task `.join` that caused the panic was. For example, this line isn't visible in the regular backtrace and it shows that the panic happened when spawning the anvil task (if you check out commit `0cc48e164379d08a8f4c3703eaab79bb86e271d6`): ``` at [...]/hyperlane-monorepo/rust/utils/run-locally/src/main.rs:321:22 ``` ### 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
Paul Balaji	0cc48e1643	fix: typo in RateLimited.sol (#3561) ... make codespell happy again	8 months ago
Trevor Porter	526d27db04	Ancient8 deploy (#3472) ... ### Description - Deploys ancient8 core - Deploys a USDC warp route from Ethereum to ancient8 - Some changes to the key generation step - specifically: - `scripts/create-keys.ts` now expects `--newChainValidators chainname=1` instead of the flag `--newChains` - fixed the logic around adding new validators, which previously was broken - Adds a hook module to deploy.ts - this is meant to be used in a similar fashion to the warp module, where configs are built ad-hoc - changes `aw-multisig.json` to be `aw-multisig-${context}.json`, as previously the entire aw-multisig.json would be overridden no matter what the current context was	8 months ago
Lee	24e1f86d25	Warp Route rate limiter hook & ISM (#3527) ... ### Description Adds rate limiting hook and ism to limit warp route transfers ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Fixes #2697 ### Backward compatibility Yes ### Testing Unit Tests --------- Signed-off-by: Paul Balaji <paul@hyperlane.xyz> Co-authored-by: Noah Bayindirli 🥂 <noah@primeprotocol.xyz> Co-authored-by: Kunal Arora <55632507+aroralanuk@users.noreply.github.com> 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>	8 months ago
Kunal Arora	37d49ec581	feat: add HypERC20 checker (#3517) ... ### Description - Added HypERC20App (extends GasRouterApp) and HypERC20Checker (extends RouterChecker bc there's no GasRouterChecker - link to issue) - remoteChains fetches the remote chains from the local router address is it given. This means, the abstract routerAddress in multiGeneric had to be made and this call had to awaited in a few places where it's used. **Why?** previously we assumed that the routers will be fully-connected and will match 1:1 with the config. This is too strong of an assumption for ICAs given we inherit the config through `getRouterConfig` and the ICA accounts will only need to exist on chains which don't have safes. Plus, in some cases, the chains implied by the app factories vs checker config don't match and this leads to further issues down the line while checking for mailbox client properties or in the govern. Checking the onchain enrollments is the most safe and resilient approach we can take especially given that having a checker for every RouterApp isn't feasible. ### Drive-by changes - adding native keys to warp artifacts for the appHelper to work in App.fromAddressMap. Note: if there's something using the router key, this isn't breaking unless you expect only one key. ### Related issues - fixes https://github.com/hyperlane-xyz/issues/issues/1191 ### Backward compatibility Yes ### Testing Manual --------- 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>	8 months ago
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	8 months ago