hyperlane-monorepo

Commit Graph

Author	SHA1	Message	Date
Paul Balaji	0dedbf5a02	feat: deploy to new chains (endurance, fuse, zora) (#4148 ) - feat: deploy to new chains (endurance, fuse, zora) - https://github.com/hyperlane-xyz/issues/issues/1308 - also includes https://github.com/hyperlane-xyz/issues/issues/1305 - registry PR https://github.com/hyperlane-xyz/hyperlane-registry/pull/104	4 months ago
Yorke Rhodes	388d255171	feat: typescript relayer MVP (#3693 ) ### Description - implement `HyperlaneRelayer` as a wrapper around `HyperlaneCore` - add relaying to CLI status command - add infra script relay for an environment ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Touches https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3448 ### 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 Manual --------- Co-authored-by: -f <kunalarora1729@gmail.com> Co-authored-by: Noah Bayindirli 🥂 <noah@primeprotocol.xyz>	4 months ago
Noah Bayindirli 🥂	e5807d4801	feat(cli,sdk): ensure consistency while passing ContractVerifier from CLI (#4151 ) ### Description - ensures consistency while passing ContractVerifier from CLI ### Drive-by changes - logging ### Related issues - https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4130 ### Backward compatibility - some breaking sdk-side changes ### Testing - manual	4 months ago
Noah Bayindirli 🥂	40255575c0	feat(cli): add blockExplorers option on registry init (#4149 ) ### Description - adds blockExplorers option on registry init ### Drive-by changes - none ### Related issues - none ### Backward compatibility - yes ### Testing - manual	4 months ago
Trevor Porter	74cd350db1	chore: update neutron relayer (#4154 ) ### Description updates relayer version, sets gas payment enforcement policy back to normal ### 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 -->	4 months ago
Trevor Porter	857338e2af	chore: update app contexts (#4136 ) ### Description - updating the ezETH metric app context on the relayer - adding merkly addresses to the app contexts - temporarily changing the gas payment enforcement for merkly ETH contracts to just require that some payment was made, this way we won't run into issues with https://github.com/hyperlane-xyz/issues/issues/1294 over the weekend. In practice it's just been the merkly eth contracts that cause this problem when they run out of liquidity - removed some warp route gas payment non-enforcement after we have hook indexing ### 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 -->	4 months ago
Trevor Porter	dcd6dc502e	chore: remove static plumetestnet gas price (#4135 ) ### 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 -->	4 months ago
Paul Balaji	2c0ae3cf37	feat: deploy to new testnets (connextsepolia, superpositiontestnet) (#4150 ) - feat: deploy to new testnets (connextsepolia, superpositiontestnet) - https://github.com/hyperlane-xyz/issues/issues/1308 - also includes https://github.com/hyperlane-xyz/issues/issues/1305 - registry pr https://github.com/hyperlane-xyz/hyperlane-registry/pull/105	4 months ago
Paul Balaji	4f1ea15e28	chore: set env-test timeout (#4120 ) - chore: set env-test timeout - to avoid machines spinning idly for hours/days in jobs like this https://github.com/hyperlane-xyz/hyperlane-monorepo/actions/runs/9872063807/job/27261501530?pr=3888#step:6:44 --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	4 months ago
Paul Balaji	b9e8e049bb	chore(infra): strongly type `AgentChainConfig` (#4102 ) - follow on from https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4093 - ts errors in editor if a chain is missing from the config - makes it easier to update `ValidatorBaseChainConfigMap` in future one chain missing: <img width="298" alt="image" src="https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/10051819/0e3c6247-3967-4caa-afad-f7a16234a029"> multiple chains missing: <img width="310" alt="image" src="https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/10051819/241782ca-16a4-4b17-9873-706485e26649">	4 months ago
Mohammed Hussan	dc15860894	feat(infra): Add new warp monitor image tag (#4147 ) ### Description <!-- What's included in this PR? --> - Add new warp monitor image tag ### 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 -->	4 months ago
Mohammed Hussan	ef89a59b00	feat(infra): update ezeth warp monitor config (#4126 ) ### Description <!-- What's included in this PR? --> - update ezeth warp monitor config ### 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 -->	4 months ago
Paul Balaji	f83b492deb	feat: implement `update()` for `EvmHookModule` (#3888 ) resolves https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3577 - enables updates of hooks - includes functionality for updating IGP hook and gas oracles - drive-by fix to ism module TODO: - [x] tests (non-igp) - [x] tests (igp) --------- Signed-off-by: Paul Balaji <paul@hyperlane.xyz> Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com> Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	4 months ago
J M Rossy	9b7de9ebe8	chore: Add some more useful vscode extensions (#4113 )	4 months ago
Paul Balaji	0a40dcb8b1	fix(sdk): update cosmos chain schema (#4142 ) - update cosmos chain schema to match latest spec `c6cfe11be2/chain.schema.json (L451-L460)` - drive-by fixing of agg test --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	4 months ago
Noah Bayindirli 🥂	d00f2ffc00	feat(cli): display formatted deployment plan to confirm warp deploy (#4053 ) ### Description - adds formatted deployment plan to confirm warp deploy on `hyperlane warp deploy` ### Drive-by changes - none ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4129 ### Backward compatibility - yes ### Testing - manual - ci-test Example display: ``` ➜ cli git:(06-25-feat_cli_display_formatted_deployment_plan_to_confirm_warp_deploy) ✗ hl warp deploy --registry /Users/nbayindirli/workplace/Hyperlane/hyperlane-registry --verbosity trace Hyperlane CLI Hyperlane Warp Route Deployment ------------------------------------------------ Using warp route deployment config at ./configs/warp-route-deployment.yaml Warp Route Deployment Plan ========================== 📋 Token Standard: ERC20 📋 Warp Route Config: ┌─────────┬───────┬─────────────┬──────────────────────────────────────────────┬──────────────────────────────────────────────┬───────────────────────┐ │ (index) │ NFT? │ Type │ Owner │ Mailbox │ ISM Config(s) │ ├─────────┼───────┼─────────────┼──────────────────────────────────────────────┼──────────────────────────────────────────────┼───────────────────────┤ │ alpha │ false │ 'native' │ '0x16F4898F47c085C41d7Cc6b1dc72B91EA617dcBb' │ '0xf87B1E8fb8ee9F12bB0C0c77ac19C28773fdbff3' │ 'See table(s) below.' │ │ beta │ false │ 'synthetic' │ '0x16F4898F47c085C41d7Cc6b1dc72B91EA617dcBb' │ '0x0b1D3Dd7162101Ad0c9A9Fe91c40CDE3410DaAFC' │ 'See table(s) below.' │ └─────────┴───────┴─────────────┴──────────────────────────────────────────────┴──────────────────────────────────────────────┴───────────────────────┘ 📋 alpha ISM Config(s): ┌───────────┬────────────────────────┐ │ (index) │ Values │ ├───────────┼────────────────────────┤ │ Type │ 'staticAggregationIsm' │ │ Threshold │ 1 │ │ Modules │ 'See table(s) below.' │ └───────────┴────────────────────────┘ ┌─────────┬──────────────────────────────────────────────┐ │ (index) │ Values │ ├─────────┼──────────────────────────────────────────────┤ │ Type │ 'trustedRelayerIsm' │ │ Relayer │ '0x16F4898F47c085C41d7Cc6b1dc72B91EA617dcBb' │ └─────────┴──────────────────────────────────────────────┘ ┌─────────────────┬──────────────────────────────────────────────┐ │ (index) │ Values │ ├─────────────────┼──────────────────────────────────────────────┤ │ Type │ 'defaultFallbackRoutingIsm' │ │ Owner │ '0x16F4898F47c085C41d7Cc6b1dc72B91EA617dcBb' │ │ Owner Overrides │ 'Undefined' │ │ Domains │ 'See warp config for domain specification.' │ └─────────────────┴──────────────────────────────────────────────┘ 📋 beta ISM Config(s): ┌───────────┬────────────────────────┐ │ (index) │ Values │ ├───────────┼────────────────────────┤ │ Type │ 'staticAggregationIsm' │ │ Threshold │ 1 │ │ Modules │ 'See table(s) below.' │ └───────────┴────────────────────────┘ ┌─────────┬──────────────────────────────────────────────┐ │ (index) │ Values │ ├─────────┼──────────────────────────────────────────────┤ │ Type │ 'trustedRelayerIsm' │ │ Relayer │ '0x16F4898F47c085C41d7Cc6b1dc72B91EA617dcBb' │ └─────────┴──────────────────────────────────────────────┘ ┌─────────────────┬──────────────────────────────────────────────┐ │ (index) │ Values │ ├─────────────────┼──────────────────────────────────────────────┤ │ Type │ 'defaultFallbackRoutingIsm' │ │ Owner │ '0x16F4898F47c085C41d7Cc6b1dc72B91EA617dcBb' │ │ Owner Overrides │ 'Undefined' │ │ Domains │ 'See warp config for domain specification.' │ └─────────────────┴──────────────────────────────────────────────┘ ? Is this deployment plan correct? (Y/n) ```	5 months ago
Lee	49986aa929	fix(cli): Add collateralAddressOrDenom for collateralVault (#4133 ) ### Description - Use the vault's underlying asset metadata for `collateralAddressOrDenom` to fix send issue reported by Cheesechain - This issue arose when the underlying asset (USDC) has a decimal of 6. This is due to `collateralAddressOrDenom` being missing in the warp artifacts for `collateralVault` causing a fee to be assessed in a decimal (18) much greater than the underlying (6). ### Backward compatibility Yes ### Testing Manual	5 months ago
Noah Bayindirli 🥂	5e5a568cb9	chore(sdk): update hookType error log level (#4132 ) ### Description - updates hookType error log level ### Drive-by changes - none ### Backward compatibility - yes ### Testing - none	5 months ago
Mohammed Hussan	dfa9087960	feat(utils): Set errorMessage argument for assert to required (#4121 ) ### Description <!-- What's included in this PR? --> - Set errorMessage argument for assert to required ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->	5 months ago
Nam Chu Hoai	5aa24611b3	fix(sdk): Renzo Fraxtal Deploy Fixes (#4115 ) ### Description - Initialized check before initializing implementation contract (for contracts that disableInitializers in constructors) - set gas overrides for renzo warp route deploys - check that validators are set - add TODOs for verifying routing ISMs (probably should be removed @ltyu ) --------- Co-authored-by: Noah Bayindirli 🥂 <15343884+nbayindirli@users.noreply.github.com> Co-authored-by: Noah Bayindirli 🥂 <noah@primeprotocol.xyz>	5 months ago
Noah Bayindirli 🥂	bb470aec25	feat(cli): add submit command (#3818 ) ### Description * adds `hyperlane submit -t ./transactions.json -s ./strategy.json` * given a set of `transactions` and a submission `strategy`, submit those transactions according to that strategy * example strategies provided under `/cli/examples/submit/` * detailed design: https://www.notion.so/hyperlanexyz/CLI-Submitter-Integration-8a14486803ca4ab18f229e8e7f89b57a?pvs=4 ### Drive-by changes * none ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3740 ### Backward compatibility - yes ### Testing #### Nice to have: - [ ] ci-test #### Manual: - [x] `hl submit -t ./examples/submit/transactions/transactions.json -s ./examples/submit/strategy/json-rpc-strategy.yaml` ``` Hyperlane Submit ---------------- Submitting 1 transactions to the jsonRpc submitter... Sent tx 0x7158756345a913630497dac948a98b1c73921626f9c17cc936994ff22dcd908f Pending https://alfajores.celoscan.io/tx/0x7158756345a913630497dac948a98b1c73921626f9c17cc936994ff22dcd908f (waiting 1 blocks for confirmation) ✅ Successfully submitted 1 transactions to the jsonRpc submitter. 🧾 Transaction receipts: [ { to: '0x9a4a3124F2a86bB5BE46267De85D31762b7a05Fd', from: '0x16F4898F47c085C41d7Cc6b1dc72B91EA617dcBb', contractAddress: null, transactionIndex: 4, gasUsed: BigNumber { _hex: '0x53b8', _isBigNumber: true }, logsBloom: '0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000', blockHash: '0x174c3355800d73e3ab9643257bf49a60fc539a6961fc6cc8adcfb27d84ab6347', transactionHash: '0x7158756345a913630497dac948a98b1c73921626f9c17cc936994ff22dcd908f', logs: [], blockNumber: 24221122, confirmations: 1, cumulativeGasUsed: BigNumber { _hex: '0x072f3f', _isBigNumber: true }, effectiveGasPrice: BigNumber { _hex: '0x01836e2100', _isBigNumber: true }, status: 1, type: 2, byzantium: true } ] ✅ Hyperlane submission complete ``` - [x] `hl submit -t ./examples/submit/transactions/transactions.json -s ./examples/submit/strategy/json-rpc-strategy.yaml --dry-run` ``` ... Dry-running against chain: alfajores 🔎 Verifying anvil node is running... ✅ Successfully verified anvil node is running Forking alfajores for dry-run... ✅ Successfully forked alfajores for dry-run Impersonating account (0x16F4898F47c085C41d7Cc6b1dc72B91EA617dcBb)... ✅ Successfully impersonated account (0x16F4898F47c085C41d7Cc6b1dc72B91EA617dcBb) Hyperlane Submit ---------------- Submitting 1 transactions to the jsonRpc submitter... Sent tx 0x89fbd7d38d6fc19df0ef24f844756153dece1e0f179b76b036c50596356dc5ce Pending https://alfajores.celoscan.io/tx/0x89fbd7d38d6fc19df0ef24f844756153dece1e0f179b76b036c50596356dc5ce (waiting 1 blocks for confirmation) ✅ Successfully submitted 1 transactions to the jsonRpc submitter. 🧾 Transaction receipts: [ { to: '0x9a4a3124F2a86bB5BE46267De85D31762b7a05Fd', from: '0x16F4898F47c085C41d7Cc6b1dc72B91EA617dcBb', contractAddress: null, transactionIndex: 0, gasUsed: BigNumber { _hex: '0x53b8', _isBigNumber: true }, logsBloom: '0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000', blockHash: '0x5a5379771a3a6d173a8dcbfc189e24f288c30abcd0a754f1df4734f465917cc7', transactionHash: '0x89fbd7d38d6fc19df0ef24f844756153dece1e0f179b76b036c50596356dc5ce', logs: [], blockNumber: 24221165, confirmations: 1, cumulativeGasUsed: BigNumber { _hex: '0x53b8', _isBigNumber: true }, effectiveGasPrice: BigNumber { _hex: '0x0104fd914d', _isBigNumber: true }, status: 1, type: 2, byzantium: true } ] ✅ Hyperlane submission complete ``` - [x] `hl submit -t ./examples/submit/transactions/transactions.json -s ./examples/submit/strategy/impersonated-account-strategy.yaml` - [x] `hl submit -t ./examples/submit/transactions/transactions.json -s ./examples/submit/strategy/impersonated-account-strategy.yaml --dry-run` - `Error: Impersonated account submitters may only be used during dry-runs.` - [x] `hl submit -t ./examples/submit/transactions/transactions.json -s ./examples/submit/strategy/gnosis-strategy.yaml` - Successfully generated proposal: https://app.safe.global/transactions/queue?safe=avax:0x7fd32493Ca3A38cDf78A4cb74F32f6292f822aBe - [ ] `hl submit -t ./examples/submit/transactions/transactions.json -s ./examples/submit/strategy/gnosis-ica-strategy.yaml` - [ ] `hl submit -t ./examples/submit/transactions/transactions.json -s ./examples/submit/strategy/gnosis-ica-strategy.yaml --dry-run`	5 months ago
Tien Dao	80ac5d28e5	chore: add symbol text when insuficient balance for pay gas (#4124 ) ### Description Update text symbol when warning insuficient balance ```diff - `WARNING: ${address} has low balance on ${chain}. At least ${minBalance} recommended but found ${balance} ${symbol}` + `WARNING: ${address} has low balance on ${chain}. At least ${minBalance} ${symbol} recommended but found ${balance} ${symbol}` ``` --------- Co-authored-by: J M Rossy <jm.rossy@gmail.com>	5 months ago
J M Rossy	0e1a80e6e0	chore: Bump registry version to 2.3.0 (#4114 ) ### Description Update to latest registry for faster and more efficient chain metadata/address fetching ### Related issues https://github.com/hyperlane-xyz/hyperlane-registry/issues/29 ### Backward compatibility Yes ### Testing Ran CLI registry commands locally	5 months ago
Mohammed Hussan	c5ab4425a7	chore(infra): Update warp monitor docker image (#4119 ) ### Description <!-- What's included in this PR? --> Update script to use the latest docker image ### 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
Mohammed Hussan	6cf3982589	feat(infra): Add xERC20 limits monitoring capabilities (#4071 ) ### Description <!-- What's included in this PR? --> - Add support for pushing limits metrics for xERC20 wrap routes - For now only push limits metrics for xERC20 wrap routes, not yet supporting warp route balances ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> - Fixes #4047 ### 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 --> Manual	5 months ago
Mohammed Hussan	be4617b18b	feat(sdk): Handle subdirectories for the folder in S3Validator (#4101 ) ### Description <!-- What's included in this PR? --> - Set the folder in the `S3Config` to include any subdirectories and not just the first folder - This brings the SDK inline with current behavior in the agents ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> - Fixes #4100 ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> Yes ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> Manual	5 months ago
Lee	7089994334	feat(cli): Add hyperlane warp apply (#4094 ) ### Description - Adds `hyperlane warp apply` ### Related issues - Fixes https://github.com/hyperlane-xyz/issues/issues/1190 ### Backward compatibility Yes ### Testing Manual To test: `yarn hyperlane warp apply --warp` --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Mohammed Hussan	cb225b824e	feat(cli): Support agent config generation for all chains (#3985 ) ### Description <!-- What's included in this PR? --> - Support generating agent config for all supported chains - Add user prompts: prompt user whether they want to zero the IGP addresses if not provided, prompt user whether they want to generate agent config anyway when schema validation fails - Support skipping prompts, useful for CI Example usage: Specific chains ``` $yarn hyperlane registry agent-config --chains anvil8545 Hyperlane CLI Creating agent config... interchainGasPaymaster address is missing for anvil8545 ? Would you like to set the interchainGasPaymaster address to 0x0 for anvil8545? yes Agent config is invalid, this is possibly due to required contracts not being deployed. See details below: Validation error: Required at "chains.anvil8545.merkleTreeHook" ? Would you like to continue anyway? yes Writing agent config to file ./configs/agent-config.json ✅ Agent config successfully written to ./configs/agent-config.json ``` All chains ``` $yarn hyperlane registry agent-config Hyperlane CLI Creating agent config... ? No chains provided, would you like to generate the agent config for all supported chains? yes interchainGasPaymaster address is missing for sketchpad ? Would you like to set the interchainGasPaymaster address to 0x0 for sketchpad? yes interchainGasPaymaster address is missing for anvil8545 ? Would you like to set the interchainGasPaymaster address to 0x0 for anvil8545? yes Agent config is invalid, this is possibly due to required contracts not being deployed. See details below: Validation error: Required at "chains.anvil8545.merkleTreeHook"; Invalid at "chains.sketchpad.interchainSecurityModule" ? Would you like to continue anyway? yes Writing agent config to file ./configs/agent-config.json ✅ Agent config successfully written to ./configs/agent-config.json ``` Skip prompts: ``` $yarn hyperlane registry agent-config --skipPrompts Hyperlane CLI Creating agent config... No chains provided, generating agent config for all supported chains Agent config is invalid, this is possibly due to required contracts not being deployed. See details below: Validation error: Required at "chains.anvil8545.merkleTreeHook"; Required at "chains.anvil8545.interchainGasPaymaster"; Invalid at "chains.sketchpad.interchainGasPaymaster"; Invalid at "chains.sketchpad.interchainSecurityModule" Creating agent config anyway... Writing agent config to file ./configs/agent-config.json ✅ Agent config successfully written to ./configs/agent-config.json ``` ### 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 --> Manual	5 months ago
Caio	4ec872c573	chore: Reorder variants of `KnownHyperlaneDomain` (#4083 ) ## Description Fix #3961	5 months ago
Daniel Savu	2f7f714c5b	feat: validator dashboard template (#4097 ) ### Description Replaces the old (and probably deprecated) validator dashboard template with a new one that shows metrics that can be alerted on: ![Screenshot 2024-07-04 at 14 25 53](https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/23065004/08ba370d-154a-4c45-91f7-2f6c9167f5a9) ### Drive-by changes Uses the "External Sharing" grafana feature to generate a json that removes AW-specific data from the relayer template	5 months ago
Daniel Savu	a5e5f70610	chore: Revert "feat(hyp-ethereum): gas escalator middleware (#3852 )" (#4098 ) This reverts commit `c3c002a8fe`. ### Description The gas escalator took up to 28gb of memory, and even though it was only ever released on RC, it must have taken up too many cluster resources, ending up starving the `hyperlane` relayer. Reverting for now until we have a better idea ### 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	8c8f39abfe	feat(relayer): ListOperations api endpoint (#4089 ) ### Description Adds a `list_operations` API endpoint to the relayer, which returns all operations in its prepare queue. Example output from `GET http://0.0.0.0:9092/list_operations?destination_domain=13371` ``` [ { "app_context": null, "message": { "body": [ 18, 52 ], "destination": 13371, "nonce": 1, "origin": 13373, "recipient": "0x000000000000000000000000927b167526babb9be047421db732c663a0b77b11", "sender": "0x000000000000000000000000927b167526babb9be047421db732c663a0b77b11", "version": 3 }, "num_retries": 13, "status": { "Retry": "CouldNotFetchMetadata" }, "submitted": false, "type": "PendingMessage" }, { "app_context": null, "message": { "body": [ 18, 52 ], "destination": 13371, "nonce": 2, "origin": 13372, "recipient": "0x000000000000000000000000927b167526babb9be047421db732c663a0b77b11", "sender": "0x000000000000000000000000927b167526babb9be047421db732c663a0b77b11", "version": 3 }, "num_retries": 13, "status": { "Retry": "CouldNotFetchMetadata" }, "submitted": false, "type": "PendingMessage" } ] ``` ### Drive-by changes Makes `PendingOperation` serializable, which means switching from JSON format to e.g. CSV (for easily filtering / aggregating in excel) should be very easy. ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility Yes ### Testing Manual and Unit Tests	5 months ago
Assaf Morami	1022e3858e	chore: add shebang to build.sh to specify bash as the interpreter (#4066 ) the `[[` command isn't available on e.g. zsh Co-authored-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	5 months ago
github-actions[bot]	29050d262a	Version Packages (#4077 ) This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @hyperlane-xyz/cli@4.1.0 ### Minor Changes - 4cc9327e5: Update warp deploy to handle xerc20, initializerArgs to be the signer, update deploy gas constants ### Patch Changes - 46652c62a: Fix the missing sorting in the YAML file generated - 56be527d6: Fix typo in core read command - 378a5b79f: Remove extra fields from warp core config - Updated dependencies [`36e75af4e`] - Updated dependencies [`d31677224`] - Updated dependencies [`4cc9327e5`] - Updated dependencies [`1687fca93`] - @hyperlane-xyz/sdk@4.1.0 - @hyperlane-xyz/utils@4.1.0 ## @hyperlane-xyz/sdk@4.1.0 ### Minor Changes - 36e75af4e: Add optional deployer field to ChainMetadata schema - d31677224: Deploy to bob, mantle, taiko - 4cc9327e5: Update warp deploy to handle xerc20, initializerArgs to be the signer, update deploy gas constants - 1687fca93: Add EvmWarpModule with update() for ISM ### Patch Changes - @hyperlane-xyz/core@4.1.0 - @hyperlane-xyz/utils@4.1.0 ## @hyperlane-xyz/core@4.1.0 ### Patch Changes - @hyperlane-xyz/utils@4.1.0 ## @hyperlane-xyz/helloworld@4.1.0 ### Patch Changes - Updated dependencies [`36e75af4e`] - Updated dependencies [`d31677224`] - Updated dependencies [`4cc9327e5`] - Updated dependencies [`1687fca93`] - @hyperlane-xyz/sdk@4.1.0 - @hyperlane-xyz/core@4.1.0 ## @hyperlane-xyz/utils@4.1.0 ## @hyperlane-xyz/infra@4.1.0 ### Minor Changes - d31677224: Deploy to bob, mantle, taiko ### Patch Changes - Updated dependencies [`36e75af4e`] - Updated dependencies [`d31677224`] - Updated dependencies [`4cc9327e5`] - Updated dependencies [`1687fca93`] - @hyperlane-xyz/sdk@4.1.0 - @hyperlane-xyz/helloworld@4.1.0 - @hyperlane-xyz/utils@4.1.0 ## @hyperlane-xyz/ccip-server@4.1.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	5 months ago
Paul Balaji	56be527d69	fix(cli): typo in core read command (#4095 ) fix(cli): typo in core read command --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Paul Balaji	94e6ca21ee	feat(infra): strongly type keyfunder config (#4093 ) resolves https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3732 - strongly type the keyfunder config - new chains added to an environment's supported chains list must be configured - opens up the path to strongly type more of the env config down the line missing 1 chain: <img width="336" alt="image" src="https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/10051819/698ef9db-c50a-4a49-bc11-d33a44f186bf"> missing multiple chains: <img width="350" alt="image" src="https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/10051819/2f9e4e6c-5c36-4239-9c00-5951eca91589">	5 months ago
Bertrand Juglas	46652c62a8	fix: use sortMapEntries in writeYaml (#4091 ) ### Description It includes usage of sortMapEntries option in yamlStringify function called in writeYaml function. ### Drive-by changes None ### Related issues - Fixes #4057 ### Backward compatibility Yes Because I've converted the argument 2 into the indent option as documented in yaml library. ### Testing Manual by trying to reproduce the issue in the same way.	5 months ago
Lee	1687fca93c	feat: WarpModule with update() IsmConfig (#3678 ) ### Description Implement WarpModule update() with IsmConfig ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Fixes https://github.com/hyperlane-xyz/issues/issues/1156 ### 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: Yorke Rhodes <yorke@hyperlane.xyz> Co-authored-by: J M Rossy <jm.rossy@gmail.com> Co-authored-by: Noah Bayindirli 🥂 <noah@primeprotocol.xyz> Co-authored-by: Noah Bayindirli 🥂 <noah@hyperlane.xyz>	5 months ago
Kunal Arora	f733379488	feat: support Arbitrum L2->L1 post dispatch hook (#3853 ) ### Description - Contract support for the enabling postDispatch hook with the Arbitrum nitro bridge from L2 to L1 - asynchronously via executeTransaction call to verifyMessageId first and then the relayer calling the verify message with no metadata (note: this supports msg.value) - synchronously via a single verify call which in turn calls executeTransaction on outbox to gets the message verified in the verifyMessageId (note: this doesn't support msg.value as ism.verify isn't payable) - Added a script for deploying the hook and ISM since the sdk doesn't support it yet. ### Drive-by changes - changing the type from "rate_limited_hook" to "RATE_LIMITED" to maintain consistency ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2846 ### Backward compatibility Yes ### Testing Unit and e2e with arbitrumsepolia->sepolia	5 months ago
steven	9cff8c2d3c	fix: index for getOperatorRestakeableStrategies (#4090 ) ### Description Creates a fix for a view function an indexer on the EigenLayer side calls into for UI display ### Drive-by changes None ### Related issues N/A ### Backward compatibility Yes ### Testing Regression test added in the Eigenlayer repo	5 months ago
Paul Balaji	d316772243	feat: deploy to BOB, Mantle, Taiko (#4051 ) resolves https://github.com/hyperlane-xyz/issues/issues/1289 - feat: deploy to BOB, Mantle, Taiko - drive-by: fix deploying to specific chain - drive-by: adding AVS operators for eth - drive-by: support non-evm remotes in mainnet3 core config --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Daniel Savu	c3c002a8fe	feat(hyp-ethereum): gas escalator middleware (#3852 ) ### Description Wraps evm providers in a gas escalator middleware as part of the `build_with_signer` step, so signed txs can have their gas price bumped if stuck in the mempool. Gas price is increased every 60s by 12.5%, and is capped at the `max_fee_per_gas` set in tx overrides. ### Drive-by changes - changes to our fork of `ethers`: - removes the `M: Clone` bound, since it's not actually required and conflicts with the middleware we use - increases the level of the `escalated` log in the middleware to `debug` (so we can see it working in prod without enabling `trace`) ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2959 ### Backward compatibility Yes ### Testing e2e --------- Co-authored-by: Trevor Porter <tkporter4@gmail.com>	5 months ago
Daniel Savu	d90d8f86b4	chore: reduce op-queue verbosity (#4092 ) ### Description The gcp bill has been shooting up, and it's most likely due to the increased number of undeliverable messages being added to and removed from the queue, causing lots of `debug` level logs on `push` and `pop_many` to be emitted. This PR changes the verbosity to `trace` - we'll have lower visibility over the lifetime of a message, but there should be sufficient logs remaining to tell us what's going on (such as [operation prepared](`30630c4fa6/rust/agents/relayer/src/msg/op_submitter.rs (L240)`), [confirming a pre-submitted one](`30630c4fa6/rust/agents/relayer/src/msg/op_submitter.rs (L260)`), [submitting single op](`30630c4fa6/rust/agents/relayer/src/msg/op_submitter.rs (L313)`), [submitting batch](`30630c4fa6/rust/agents/relayer/src/msg/op_submitter.rs (L456)`), and [op confirmed](`30630c4fa6/rust/agents/relayer/src/msg/op_submitter.rs (L386)`)). @paulbalaji suggested measuring log counts, so here they are: - in the last 6h, we had 42M `hyperlane` relayer logs, of which 22M where `push` logs and 1.1M were `pop_many` (no `pop`s) - if we make push ones trace, 5.5% of the remaining logs would be pop_many ### 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	f8b33d1270	chore: update deployed relayer image (#4088 ) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->	5 months ago
Nam Chu Hoai	4cc9327e52	fix(cli): ezETH deploy fixes (#4009 ) ### Description some minor fixes to make the ezEth deploy work. Does not include the modifications to contract verification retries that I made. --------- Co-authored-by: Lee <6251863+ltyu@users.noreply.github.com>	5 months ago
Paul Balaji	d35b54670d	feat(keyfunder): make IGP claim thresholds configurable via command line args (#4074 ) hit successor to https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3284 resolves https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4049 - igp claim thresholds are moved to command line args instead, like desired balances - making it easier to tweak IGP claim thresholds - default claim threshold is 20% of desired balance for that chain - roughly follows what I've seen with the other balance vs igp claim thresholds - adding thresholds for all chains we've configured a desired relayer balance for - drive-by fixing keyfunder logging to include the relevant metadata testing: - ran locally and successfully performed igp claims on [blast](https://blastscan.io/tx/0x314d83d16e0406f77731befc7e8387dc946af01f7dc2200a426ff9748ad76d27), [linea](https://lineascan.build/tx/0xa5f4731ebcff073dacc6c15326196002bafd9578059688fd2f29db1a2742cb14), [viction](https://www.vicscan.xyz/tx/0x39921d3018a7b019518aa7a55a45ff29cce379bb9aabf0910c14423bd88689d5) & more --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Trevor Porter	6f4ef05d41	feat: faster way of figuring out how many new scraper rows were inserted (#4073 ) ### Description ### Context Full context / thread: https://discord.com/channels/935678348330434570/1254871503825141923 Copied here: so this is kinda interesting basically the gas payment indexing in the scraper task is consistently prioritizing hook-based indexing work over block range indexing work this only manifests in the scraper and for arbitrum because: there are a lot of arbitrum origin messages on the scraper, each gas payment indexing tick takes a very long time because of some very suboptimal queries. store_payments can take like 10-15 seconds! You can see batches of logs Found log(s) in index range https://cloudlogging.app.goo.gl/Bo9Q7YwyziSqjsEu7 that correspond with the gas payment contract sync block height (green line) advancing https://abacusworks.grafana.net/goto/poW4KOQIg?orgId=1 ![image](https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/20362969/65da2e44-5728-4ecc-9c1f-52741805eb5b) but we're still indexing gas payments bc of hook indexing - there are tons of Found log(s) for tx id https://cloudlogging.app.goo.gl/QvDaBuf67SjjKviw6 In the scraper's store_payments we bizarrely end up performing 2 very expensive queries with the calls to payments_count - it gets the count of gas payments for the provided domain so it can figure out how many new gas payments were actually inserted https://github.com/hyperlane-xyz/hyperlane-monorepo/blob/main/rust/agents/scraper/src/db/payment.rs#L27-L64 These queries vary a bunch in how expensive they can be - sometimes each one is like 1-2 seconds, sometimes it gets up to 10 seconds each though https://cloudlogging.app.goo.gl/cDFNH3oxh6WWV3Go8 ![image](https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/20362969/612c7999-21b2-43f4-861f-8b42580e4cb7) easiest fix is probably to figure out how to make store_payments less expensive - we probably don't need to be making these calls to payments_count to figure out which ones are new which ill do atm there's maybe a decent argument to having hook indexing and range indexing not contend with one another but we should be able to kick that can also an annoying thing is https://github.com/hyperlane-xyz/hyperlane-monorepo/blob/main/rust/hyperlane-base/src/contract_sync/mod.rs#L155 this log not showing up, probably some weird instrumentation setup or something makes debugging harder ### The fix We want to keep supporting the possibility that we've double-indexed a data type, and to only return the number of new rows inserted. We want to keep each indexing task as non-conflicting as possible - we know that only one scraper is running at a time, but that a task for each chain and data type is executing concurrently. It's possible for e.g. two gas payment indexing tasks to try to insert into the same table concurrently, but it'll be for different domains. Insert statement concurrency issues aren't an issue because the only chance for conflict is the auto-incrementing primary key id, but this is all handled properly by database internals. Insert results only give the latest ID resulting from the insertion. E.g. if no matter how many rows were inserted, it gives the latest ID from that batch, but no info about how many were in the batch. We could do something like get the latest id in the table for all domains (this is cheap) before, then do the insert, and then get the latest id again, but this is susceptible to race conditions if concurrent tasks get an insertion in during that time as well. Shoving all these into a transaction doesn't seem to solve the problem either unless there's a lock on the table. However, sea-orm doesn't support table level locks, just select locks. We could also use a CTE to perform as a way to perform the select & insertion atomically and return the value of the select - but again sea-orm doesn't seem to provide a nice way of doing this from what I could tell. Instead, my suggested fix is: 1. Get the latest id in the table relating to the specific domain (this is cheap, < 100ms) 2. Perform the insertion 3. Count how many new rows for the specific domain now exist whose id is > the id from (1). This is also cheap, < 100ms. If there is a very long time since the last insertion for the domain, this could take longer, but in practice this doesn't seem to be the case. If this couple order of magnitude improvement still poses issues in the future, we can consider other alternatives, probably involving locking or fancier CTE queries. Some example queries and how long they take: Before (2x of these would occur!): <img width="477" alt="Screen Shot 2024-06-28 at 12 36 41 PM" src="https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/20362969/5cc8ac35-74fb-4847-9c6f-448deb253a0c"> Now: 1. Max id for a given domain <img width="494" alt="Screen Shot 2024-06-28 at 12 37 00 PM" src="https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/20362969/56dbb3ff-b540-458c-809c-56ebfbfd3b0f"> 2. Subsequent count but with an ID filter - note I actually changed this query to look for IDs > 3600000, which includes 55300 rows and it's still just 102ms! <img width="632" alt="Screen Shot 2024-06-28 at 12 37 49 PM" src="https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/20362969/11593180-682f-4867-9867-97fd93512802"> ### Drive-by changes - Updated the neutron image along with a deploy there ### Related issues ### Backward compatibility ### Testing Ran some sorta ad-hoc unit tests to test my new query by running against the prod db with a tokio::task. Tested for a new domain and an existing one	5 months ago
J M Rossy	36e75af4ed	feat: Add deployer to ChainMetadata schema (#3987 ) ### Description - Add optional deployer field to ChainMetadata schema ### Drive-by changes - Order ChainMetadata zod schema fields alphabetically ### Related issues Required for https://github.com/hyperlane-xyz/hyperlane-registry/issues/42 ### Backward compatibility Yes	5 months ago
J M Rossy	378a5b79f7	fix: Remove extra fields in warp core config (#4072 ) ### Description Remove extra fields in warp core configs. Context: https://github.com/hyperlane-xyz/hyperlane-registry/pull/73 Discussion: https://discord.com/channels/935678348330434570/1255901895503908934 ### Drive-by changes Improve type assertion of `assert` util ### Backward compatibility Yes ### Testing Took configs from CLI e2e test artifact and tested it in registry CI.	5 months ago
Noah Bayindirli 🥂	56f5d88e96	fix(cli): gracefully handle RPC failures on hook derivation (#4062 ) ### Description - gracefully handles RPC failures on hook derivation - TODO: - ISM derivation ### Drive-by changes - none ### Related issues - P1 ### Testing - manual	5 months ago

1 2 3 4 5 ...

2445 Commits (d0f7f21fd49b9be818167feddffe7cc1c35dae8f) All Branches Search

2445 Commits (d0f7f21fd49b9be818167feddffe7cc1c35dae8f)

All Branches