hyperlane-monorepo

Commit Graph

Author	SHA1	Message	Date
Trevor Porter	c4e7a4e5ee	fix: require thresholds to always be a set majority (#4314 ) ### Description - Thresholds must always be a set majority, enforced by a unit test - Updates thresholds for some chains that should've been updated as the set expanded ### 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 -->	3 months ago
Lee	4a1972903e	fix(cli): incorrect command for new chains (#4285 ) ### Description Fixes the new chain message to display the correct command	3 months ago
Yorke Rhodes	4425c69991	fix: solidity coverage failing due to fixture issue (#4304 ) ### Description Fixes solidity coverage reporting ### Testing CI Tests	3 months ago
Mohammed Hussan	ff0171677d	feat(governor): Support handling proxyAdmin violation in HyperlaneAppGovernor (#4311 ) ### Description - Support handling proxyAdmin violation, where the proxyAdmin of a proxy contract is not the expected proxyAdmin, `HyperlaneAppGovernor` - `HyperlaneCoreGovernor` and `ProxiedRouterGovernor` implementation will use it ### Testing Manual	3 months ago
Lee	d0ce06280f	feat(infra): Add Zircuit and Safes to Renzo deploy script (#4310 ) ### Description Adds Zircuit and Safes to Renzo deploy script ### Backward compatibility Yes ### Testing Manual	3 months ago
Paul Balaji	181259a8b0	fix: short-circuit known configs in legacy hook deployer (#4305 ) fix: short-circuit known configs in legacy hook deployer given we already do the process of recovering the same hooks for each domain, this short-circuits that even further to avoid the extra time taken to try, recover, move-on for each hook	3 months ago
Trevor Porter	9db5871f27	fix: use correct Neutron IGP (#4303 ) ### Description - We've been operating Neutron warp routes with a whitelist so far. It seems like in the initial shuffle of things, we configured the agents to index an IGP that was actually replaced 😬 by another one - This starts indexing the new one. Because of watermark indexing, we won't backfill old IGP payments, because from its perspective it thinks it's already indexed those. I wonder if we should tie watermark indexing cursors to the IGP address? Either way, this is probably fine as to date only a couple non-warp messages from Neutron have occurred ### 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 -->	3 months ago
Paul Balaji	d274c6b3f8	chore: update registry to v2.5.0 (#4302 ) chore: update registry to v2.5.0	3 months ago
Yorke Rhodes	76f7ecafff	feat: attributable fraud for signers (#4284 ) ### Description Implements fraud proof attributions for checkpoint signers (validators). It is important to have a record of attribution in storage for slashing replay protection. We also maintain a [whitelist of merkle tree hooks](`b14f997810/solidity/contracts/libs/CheckpointLib.sol (L50-L54)`) such that validators cannot simply lie about this part of the checkpoint and circumvent fraud proofs. ### Backward compatibility Yes ### Testing Unit Tests	3 months ago
Nam Chu Hoai	c2c5bb9bbc	feat: Add long-running CLI relayer (#4279 ) ### Description Adds the CLI equivalent of #3693. Should mostly be used only for demo purposes with reliable RPCs in the registry. Includes some drive-by changes to the existing single-message self-relay. ### Drive-by changes - Self-relay fixes ### Backward compatibility Yes ### Testing Manual --------- Co-authored-by: J M Rossy <jm.rossy@gmail.com>	3 months ago
Lee	9087bfcbb8	fix(cli): Remove getUri from core read logging (#4283 ) ### Description This removes the `getUri()` from a specific log because the function throws for MergeRegistry and ends up hiding the real error message. ### Backward compatibility Yes ### Testing Manual	3 months ago
Paul Balaji	8be75b6569	feat: core deploy to new chains (#4281 ) Deploy to new chains: 1. cyber 1. degenchain 1. kroma 1. lisk 1. lukso 1. merlin 1. metis 1. mint 1. proofofplay 1. real 1. sanko 1. tangle 1. xai drive-by: - fix bug in `set-rpc-urls-from-registry.ts` - add script to generate sql to add multiple chains to scraper db	3 months ago
Paul Balaji	2d922805c0	feat: add arbitrumsepolia, basesepolia, ecotestnet, optimismsepolia, polygonamoy to core chains (#4297 ) Deploy to arbitrumsepolia, basesepolia, ecotestnet, optimismsepolia, polygonamoy	3 months ago
Kunal Arora	63abe564d4	feat: implementation of yield rebasing warp route contracts (#4203 ) ### Description - To reflect the rebased underlying asset, `_transferRemote` is overridden because we need to pass in the ERC4626 vault shares which on the synthetic `HypERC4626VaultYield` which change in value as the underlying vault shares accrue yield or receive a drawdown. - The exchangeRate (i.e., assets/shares) is encoded as metadata and sent to the synthetic token to calculate the value of the synthetic token. - On synthetic transfers, the overridden `ERC20.transfer()` function calculates the needed shares for the amount and transfers them instead. Design decisions - Do we need to rebase frequently? Yes, otherwise the exchangeRate on the synthetic token will be stale compared to the the actual vault claimable yield, which means a user who deposits later and right before the infrequent rebase will get disproportionate share of the yield. You can rebase by calling `rebase()` on the collateral token which makes a transferRemote call with 0 amount. - Why exchangeRate and not underlyingDepositedAmount on the synthetic? If a user withdraws (ie calls transferRemote on the synthetic) while a rebase is inflight, the underlyingDepositedAmount will get an inaccurate update (will be overreported and hence will derive inaccurate balance amounts on the synthetic. The exchangeRate doesn't change if the user is depositing or withdrawing. - Why override the `transfer` on the synthetic? Otherwise if a user A sends 100 USDC worth of shares to user B which has a exchange rate of 1.05, user A would have unwittingly sent 105 #tokens (5 excess). - What happens in a drawdown of the value? Once the user calls withdraws the the withdrawal they get out is accordingly discounted. If a user transfers on the synthetic, it will still gets the stale exchangeRate until rebase. - What if the owner of the vault charges a fee on the yield? In that case, you need to override the totalAssets to reflect the assets - feesByOwner and the warp route implementation will stay the same. One example implementation is `MockERC4626YieldSharing` and we have adequate tests to cover the functionality. - Rounding error? We're rounding down the exchangeRate as per the general recommendation for ERC4626 vault math. - Why not make the synthetic token an ERC4626 itself, given that there's some overlapping functionality? Even though, the assetsToShares and assetsToShares functions are the same, the synthetic token itself doesn't have an underlying token so it doesn't confer to the 4626 interface. - What if there are multiple synthetic tokens for a single rebasing collateral contract and what happens is the exchange rate is not in sync between the synthetics? Things to keep in mind for - How do I keep the exchangeRate in sync with the underlying vault? Keep calling rebase as a cron job frequently, or make a hook call in deposit, redeem, and withdraw function to automatically resync the exchangeRate. - 4626 math pitfalls: https://www.zellic.io/blog/exploring-erc-4626/ ### Drive-by changes - Renaming `HypERC20CollateralVaultDeposit` -> `HypERC4626OwnerYieldCollateral` ### Related issues - fixes https://github.com/hyperlane-xyz/issues/issues/1334 ### Backward compatibility Yes ### Testing Unit tests	3 months ago
Yorke Rhodes	cb404cb85c	feat: implement checkpoint fraud proofs (#4277 ) ### Description Implements 4 categories of checkpoint fraud proofs for use in future validator slashing protocol: 1. premature: if a checkpoint index is greater than the corresponding mailbox count, it is fraudulent 2. non local: if a checkpoint origin does not match the checkpoint's mailbox domain, it is fraudulent 3. message id: if a checkpoint message ID differs from the actual message ID (verified by merkle proof) at the checkpoint index, it is fraudulent 4. root: if a checkpoint root differs from the actual root (verified by merkle proof + root reconstruction) at the checkpoint index, it is fraudulent Notably this is implemented independently from signature verification to allow for multiple checkpoint signing schemes to reuse the same checkpoint logic. ### Related issues - Touches https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3799 - See https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/2431 for previous discussions ### Backward compatibility Yes ### Testing Unit testing with fixtures in `vectors/merkle.json` that are generated by the rust merkle tree and proof code	3 months ago
Danil Nemirovsky	d1bf212bf7	feat: Report git commit hash as agent metadata (#4282 ) ### Description * We are storing git commit hash as an environment variable when we compile the source code of an agent. * Validator uses git commit hash as a agent version in `metadata_latest.json` file. * File `metadata_latest.json` is overwritten every time when validator is restarted. * Git commit hash is extracted by `git` util, so, it should be available during build time. * If the directory with the source code does not contain `.git` folder, git commit hash will be defaulted to `VERGEN_IDEMPOTENT_OUTPUT`. Agent Metadata is propagated to Relayer and Scraper, but is not used there. We can use it in the future, reporting git hash commit in the logs, for example. ### Backward compatibility Yes ### Testing * Tested locally with E2E Tests. * Tested against S3 by deploying docker image into k8s --------- Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>	3 months ago
Paul Balaji	7625bf8dce	fix: typo in trait builder log (#4292 ) - fix: typo in trait builder log - noticed while looking at scraper logs	3 months ago
Mohammed Hussan	b65141fa4f	feat(infra): Support checking proxyAdmin addresses in check-deploy (#4198 ) ### Description - Enable checking the proxyAdmin address for proxied contracts (Collateral, Synthetic) against what is set in config. This check assumes we use one proxyadmin contract per chain for (Mailbox, Collateral, Synthetic) Example usage: #### Ancient8 ``` $yarn tsx ./scripts/check-deploy.ts -e mainnet3 -m warp -c ancient8 Deploying staticAggregationIsm to ethereum Deploying messageIdMultisigIsm to ethereum Recovered 2 of 3 address set on ethereum: 0xD32513263Eb3190c4DA126fe418864904D9F4A32 Deploying merkleRootMultisigIsm to ethereum Recovered 2 of 3 address set on ethereum: 0x054B75b89DA7a428C2BF1f6b5df33944167B785C Recovered 1 of 2 address set on ethereum: 0x9c764dF6bdd6B716CfadEAa348E1dB146694F67F ┌─────────┬────────────┬────────┬─────────────┬─────────────────────────┬─────────┬──────────────────────────────────────────────┬──────────────────────────────────────────────┐ │ (index) │ chain │ remote │ name │ type │ subType │ actual │ expected │ ├─────────┼────────────┼────────┼─────────────┼─────────────────────────┼─────────┼──────────────────────────────────────────────┼──────────────────────────────────────────────┤ │ 0 │ 'ancient8' │ │ │ 'TokenSymbolMismatch' │ │ 'USDC' │ undefined │ │ 1 │ 'ancient8' │ │ │ 'TokenNameMismatch' │ │ 'USD Coin' │ undefined │ │ 2 │ 'ancient8' │ │ │ 'TokenDecimalsMismatch' │ │ 6 │ undefined │ │ 3 │ 'ancient8' │ │ 'synthetic' │ 'ProxyAdmin' │ │ '0xdB670e1a1e312BF17425b08cE55Bdf2cD8F8eD54' │ '0x0761b0827849abbf7b0cC09CE14e1C93D87f5004' │ └─────────┴────────────┴────────┴─────────────┴─────────────────────────┴─────────┴──────────────────────────────────────────────┴──────────────────────────────────────────────┘ ``` #### Ethereum ``` $yarn tsx ./scripts/check-deploy.ts -e mainnet3 -m warp -c ethereum Deploying staticAggregationIsm to ethereum Deploying messageIdMultisigIsm to ethereum Recovered 2 of 3 address set on ethereum: 0xD32513263Eb3190c4DA126fe418864904D9F4A32 Deploying merkleRootMultisigIsm to ethereum Recovered 2 of 3 address set on ethereum: 0x054B75b89DA7a428C2BF1f6b5df33944167B785C Recovered 1 of 2 address set on ethereum: 0x9c764dF6bdd6B716CfadEAa348E1dB146694F67F ┌─────────┬────────────┬────────┬──────────────┬──────────────┬─────────┬──────────────────────────────────────────────┬──────────────────────────────────────────────┐ │ (index) │ chain │ remote │ name │ type │ subType │ actual │ expected │ ├─────────┼────────────┼────────┼──────────────┼──────────────┼─────────┼──────────────────────────────────────────────┼──────────────────────────────────────────────┤ │ 0 │ 'ethereum' │ │ 'collateral' │ 'ProxyAdmin' │ │ '0xEd96482beA3C51a33b4c1aDa8b438e33A2367413' │ '0x75EE15Ee1B4A75Fa3e2fDF5DF3253c25599cc659' │ └─────────┴────────────┴────────┴──────────────┴──────────────┴─────────┴──────────────────────────────────────────────┴──────────────────────────────────────────────┘ ```	3 months ago
Mohammed Hussan	19f7d4fd90	feat(infra): Support warp config in infra from non-evm routes (#4291 ) ### Description - Add in code warp configs for non-evm chains ### Testing Manual	3 months ago
Mohammed Hussan	72aa438e27	feat(infra): supporting generating warp configs for EVM routes (#4248 ) ### Description - Add in code configs for EVM base warp routes - Allow checker tooling (check-deploy) to read and run against the config - Read Warp addresses from registry when run check-deploy for warp modules ### Drive-by changes - clean up ISM config comparison violation message to handle ISM addressed ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility Yes ### Testing Manual	4 months ago
Paul Balaji	021f4bf97d	fix: temporarily skip flaky MultisigMetadataBuilder test (#4290 ) example of test that flakes fairly regularly: https://github.com/hyperlane-xyz/hyperlane-monorepo/actions/runs/10316932362/job/28560341286#step:6:1022	4 months ago
Trevor Porter	957de25b6d	chore: bump validator resource requests (#4288 ) ### Description See thread https://discord.com/channels/935678348330434570/935679524534911007/1271367720797077548 for context. TLDR: - upon starting up, validators tend to use more CPU and memory, and this scales a bit with # of messages previously dispatched on that chain - nothing concerning, but we were exceeding the 75% usage / requests threshold on some of our alerts, so bumping to give some room ### 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
Kunal Arora	e151b5f9ac	feat: support Arbitrum L2->L1 message using CLI self-relay option (#3986 ) ### Description - trying for null metadata (in case where the L2->L1 call has been executed by a third party) otherwise waiting for the challenge period and then fetching the outbox proof using the `ArbL2ToL1MetadataBuilder` - deriving ArbL2ToL1 hook and ism - deriving custom hook from reciptISM when ismType == ARB_L2_TO_L1 ### Drive-by changes - modifying status command in CLI to write context for self-relaying messages ### Related issues - fixes https://github.com/hyperlane-xyz/issues/issues/1290 ### Backward compatibility Yes ### Testing Testnet from arbitrumsepolia -> sepolia - l2->l1 tx using selfrelay (if already preverified by 3rd party relayer) https://sepolia.etherscan.io/tx/0xa6af2355facedb102e1fb7275249ab714dadacd4264daa170801469cf22f2bc0 - l2->l1 tx using direct executeTransaction call https://sepolia.etherscan.io/tx/0x42bb0eefcbd0f78b5048052c911746d13da15a9fb9659775d5d9df1e116a2a3d --------- Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz> Co-authored-by: Yorke Rhodes <email@yorke.dev>	4 months ago
Trevor Porter	f70245cf26	feat: configure ICA owners (#4280 ) ### Description Successful ICA interactions here: https://www.notion.so/hyperlanexyz/Test-ICA-call-Ethereum-viction-inevm-f7bb4414554248cda038f19489267ec4?pvs=4#66c9651cda2a45b69c49533b24c06500 - Adds the viction ICA as the new owner - Doesn't yet set the inEVM owner - it's in there but commented out. If it's added now, we'll start to have new contracts be owned by it, but it'll also result in a lot of violations. Happy to uncomment it if that seems better. - Ideally the ICAs would be generated from the owner address on the ethereum chain, but atm the best way to do this is an eth_call, and we sadly can't do async calls. It's an option to write a non-async version that uses some fancy create2 logic in ts, but this felt like overkill. I can also write a test, but it feels a bit weird to have eth_calls to live networks on a test. For now I'm personally comfortable with us just taking on the maintenance burden of ensuring these are all correct. ### Drive-by changes - Redeployed testnet4 kathy - I think the version that was live prior to this may not have been using private URLs ### 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
Lee	d408b0d6f8	fix(cli): blockchain reason error handling (#4258 ) ### Description Ethersjs [parses](`0bfa7f497d/packages/providers/src.ts/etherscan-provider.ts (L129-L154)`) the [jsonrpc](https://www.jsonrpc.org/specification#response_object) responses into their own error codes and Error object. This is an attempt to add handling for blockchain specific errors such as: - `Error: execution reverted: MailboxClient: invalid mailbox` - `Error: insufficient funds for intrinsic transaction cost` Fixes Bug bash issues: - "Balance was not sufficient to deploy even though I was told it was" - “Replace RPC” error shown when mailbox is “invalid” ### Backward compatibility Yes ### Testing Manual --------- Co-authored-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	4 months ago
Lee	7d3b5ceac9	feat(cli): Add existing mailbox confirmation to core deploy (#4266 ) ### Description Add check & confirm for existing mailbox to core deploy to allow users to decide if they want to deploy a new mailbox ### Drive-by changes Add skip confirmation to core deploy ### Backward compatibility Yes ### Testing Manual --------- Co-authored-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	4 months ago
Paul Balaji	103e6b3e12	feat: deploy to `zircuit` (#4265 ) - feat: deploy to `zircuit` - update registry + agent config	4 months ago
Danil Nemirovsky	c176e16286	docs: Add jq as prerequisite since yarn install won't work without it (#4262 ) ### Description Adds `jq` as prerequisite in README.md since `yarn install` won't work without it. ### Testing Checked how README.md looks in GitHub. --------- Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>	4 months ago
Lee	dd12e93e01	feat(cli): Add output of hyperlane warp read to file (#4267 ) ### Description - Add output of `hyperlane warp read` to ./configs/warp-route-deployment.yaml, similar to `hyperlane core read` Fixes bug bash issue: "warp read gives you more info than the config/addresses file in .hyperlane" ### Backward compatibility Yes ### Testing Manual	4 months ago
Paul Balaji	cf6816be7f	feat: add script to set rpc secrets from registry (#4270 ) resolves https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4227 - add `set-rpc-urls-from-registry` script to set secrets by reading in contents of registry - example usage: `yarn tsx scripts/secret-rpc-urls/set-rpc-urls-from-registry.ts -e mainnet3 -c base zircuit arbitrum` - refactored `set-rpc-urls` to reuse logic across both scripts --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	4 months ago
Daniel Savu	a49f52cc9c	feat: deploy solana, eclipsemainnet (#4238 ) ### 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: pbio <10051819+paulbalaji@users.noreply.github.com>	4 months ago
Danil Nemirovsky	21da4861d0	docs: Add hyperlane registry as prerequisite for e2e tests (#4263 ) ### Description E2E tests will fail if `hyperlane-registry` repo is not cloned next to the monorepo. This change adds it to the `rust/README.md` file. ### Testing Checked how `rust/README.md` looks like in GitHub. --------- Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com> Co-authored-by: Trevor Porter <tkporter4@gmail.com>	4 months ago
Yorke Rhodes	2edfa40435	fix: only evaluate dynamic revert reasons in reverting branch (#4046 ) ### Description Optimize non-reverting branch gas usage caused by building dynamic revert reason strings ### Testing Unit Tests	4 months ago
Trevor Porter	69fba689b9	feat: new mainnet ICA deployment & tooling (#4264 ) ### Description - Corresponding registry PR: https://github.com/hyperlane-xyz/hyperlane-registry/pull/130 - Decided to deploy new ICA routers instead of going through the big hassle of using the existing one - Added a new script to make it easier to get / deploy an ICA ### 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	ff3c9897ea	chore: migrate `test1` from `13371` to `133711` (#4252 ) - chore: migrate `test1` from `13371` to `133711` - due to clash with immutablezkevm - drive-by registry update + agent config update --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	4 months ago
Yorke Rhodes	a7ab950246	fix: spelling mistake in sdk CHANGELOG (#4257 ) ### Description Fix codespell job on main https://github.com/hyperlane-xyz/hyperlane-monorepo/actions/runs/10256216777/job/28374837670?pr=4256	4 months ago
Yorke Rhodes	3d4e6436d5	fix: require multiple chains in warp init (#4256 ) ### Description Block on user selecting multiple chains in `hyperlane warp init` ### Drive-by Adjust incorrect requirement of multiple chain selection in routing ISM builder ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4255 ### Backward compatibility Yes ### Testing Manual --------- Co-authored-by: Lee <6251863+ltyu@users.noreply.github.com>	4 months ago
Kunal Arora	d396e2c553	feat: add `IStaticWeightedIsm` implementation (#4170 ) ### Description - Adding the static variation of the IWeightedIsm config where you configure validators with their corresponding weights and store it as bytecode. ### Drive-by changes None ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4160 ### Backward compatibility Yes ### Testing Fuzz tests	4 months ago
Paul Balaji	d6ede7816c	fix: widgets package.json (#4253 ) fix: widgets package.json	4 months ago
github-actions[bot]	ec447febc6	Version Packages (#4103 ) 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@5.0.0 ### Major Changes - f1d70a5e8: refactor: select chain now become 2 step, select mainnet/testnet type first, then select chain ### Minor Changes - 388d25517: Added HyperlaneRelayer for relaying messages from the CLI - d0f7f21fd: Fix logging for hyperlane core apply - d00f2ffc0: Displays formatted deployment plan to confirm warp deploy. - 40255575c: Adds blockExplorers option on registry init. - 708999433: Adds hyperlane warp apply - 0e1a80e6e: Improve chain metadata and address fetching from github registries - 5529d98d0: Add hyperlane core apply with update ownership - 62d71fad3: Add hyperlane warp update to extend a warp config - 49986aa92: Add collateralAddressOrDenom for collateralVault - ded5718a0: Update hyperlane core read to log the config terminal "preview", only if the number of lines is < 250 - 5125b798d: Prompt for chain testnet/mainnet during chain definition flow - bb470aec2: Add 'submit' command to CLI. ### Patch Changes - 80ac5d28e: Display token symbol when balance is insufficient for command - 6341edf2a: fix: use merkle tree hook address from registry for self relay hook derivations - c539775d7: Default to mailbox address in registry - c2a2897d7: Update CLI verbiage to ask for vault and not token when initiating collateralVault warp route. - Updated dependencies [`2c0ae3cf3`] - Updated dependencies [`0dedbf5a0`] - Updated dependencies [`388d25517`] - Updated dependencies [`69a39da1c`] - Updated dependencies [`4907b510c`] - Updated dependencies [`488f949ef`] - Updated dependencies [`c7f5a35e8`] - Updated dependencies [`7265a4087`] - Updated dependencies [`0a40dcb8b`] - Updated dependencies [`f83b492de`] - Updated dependencies [`79740755b`] - Updated dependencies [`8533f9e66`] - Updated dependencies [`ed65556aa`] - Updated dependencies [`ab827a3fa`] - Updated dependencies [`dfa908796`] - Updated dependencies [`ed63e04c4`] - Updated dependencies [`dfa908796`] - Updated dependencies [`5aa24611b`] - Updated dependencies [`cfb890dc6`] - Updated dependencies [`708999433`] - Updated dependencies [`5529d98d0`] - Updated dependencies [`62d71fad3`] - Updated dependencies [`49986aa92`] - Updated dependencies [`7fdd3958d`] - Updated dependencies [`8e942d3c6`] - Updated dependencies [`fef629673`] - Updated dependencies [`be4617b18`] - Updated dependencies [`1474865ae`] - @hyperlane-xyz/sdk@5.0.0 - @hyperlane-xyz/utils@5.0.0 ## @hyperlane-xyz/sdk@5.0.0 ### Major Changes - 488f949ef: Upgrade CosmJS libs to 0.32.4 ### Minor Changes - 2c0ae3cf3: Deploy to connextsepolia + superpositiontestnet - 0dedbf5a0: Deploy to endurance, fusemainnet, zoramainnet - 388d25517: Added HyperlaneRelayer for relaying messages from the CLI - 4907b510c: Add logic to parse SmartProvider errors to handle ethers and smart provider errors - c7f5a35e8: Add hyperlane core apply with update default Ism - f83b492de: - Enable updating of hooks through the `EvmHookModule`, including IGP and gas oracles. - Drive-by fixes to ISM module and tests. - 79740755b: Add enroll remote router to WarpModule - 8533f9e66: Adds transferOwnership to warp update to allow ownership to be transferred if the onchain owner differ - ed65556aa: Improve WarpCore validation error message for IGP fee checks - cfb890dc6: Remove outdated logos in SDK (now in registry) - 708999433: Adds hyperlane warp apply - 5529d98d0: Add hyperlane core apply with update ownership - 62d71fad3: Add hyperlane warp update to extend a warp config - 49986aa92: Add collateralAddressOrDenom for collateralVault - 8e942d3c6: Deploy to cheesechain, worldchain, xlayer ### Patch Changes - 69a39da1c: Fix issue with cosmos tx estimation - 7265a4087: Add rpcUrl, chainId, and method(params) to smart provider logging. - 0a40dcb8b: Update cosmos chain schema - ab827a3fa: Removes innacurate contract verification check, resulting in proxy contracts not being marked as proxies during contract verification. - dfa908796: add error message for all calls to assert util - ed63e04c4: Creates HyperlaneReader to re-use dyn provider log level & silences provider logs in deriveIsmConfig like deriveHookConfig. - 5aa24611b: Add 'isInitialized' check before initializing implementation contract (for contracts that disableInitializers in constructors). - 7fdd3958d: Adds logic to prune and minify build artifacts to address 'entity size too large' error thrown from explorers. Note that the only identified instance of this issue is on BSC mainnet. - fef629673: ContractVerifier now adjusts timeouts based on explorer family, which helps with many rate-limiting related contract verification issues. In addition, the ContractVerifier verify logic has been greatly simplified to allowing for a predictable callstack + easy debugging. - be4617b18: Handle subdirectories for the folder in S3Validator class - Updated dependencies [`388d25517`] - Updated dependencies [`488f949ef`] - Updated dependencies [`dfa908796`] - Updated dependencies [`90598ad44`] - Updated dependencies [`1474865ae`] - @hyperlane-xyz/utils@5.0.0 - @hyperlane-xyz/core@5.0.0 ## @hyperlane-xyz/utils@5.0.0 ### Major Changes - 488f949ef: Upgrade CosmJS libs to 0.32.4 ### Minor Changes - 388d25517: Added HyperlaneRelayer for relaying messages from the CLI - dfa908796: set the errorMessage argument as required for assert util function ### Patch Changes - 1474865ae: Replace `configDeepEquals` with improve `deepEquals` ## @hyperlane-xyz/widgets@5.0.0 ### Minor Changes - 98eb680ad: Migrate hyperlane widgets lib to monorepo ### Patch Changes - Updated dependencies [`2c0ae3cf3`] - Updated dependencies [`0dedbf5a0`] - Updated dependencies [`388d25517`] - Updated dependencies [`69a39da1c`] - Updated dependencies [`4907b510c`] - Updated dependencies [`488f949ef`] - Updated dependencies [`c7f5a35e8`] - Updated dependencies [`7265a4087`] - Updated dependencies [`0a40dcb8b`] - Updated dependencies [`f83b492de`] - Updated dependencies [`79740755b`] - Updated dependencies [`8533f9e66`] - Updated dependencies [`ed65556aa`] - Updated dependencies [`ab827a3fa`] - Updated dependencies [`dfa908796`] - Updated dependencies [`ed63e04c4`] - Updated dependencies [`5aa24611b`] - Updated dependencies [`cfb890dc6`] - Updated dependencies [`708999433`] - Updated dependencies [`5529d98d0`] - Updated dependencies [`62d71fad3`] - Updated dependencies [`49986aa92`] - Updated dependencies [`7fdd3958d`] - Updated dependencies [`8e942d3c6`] - Updated dependencies [`fef629673`] - Updated dependencies [`be4617b18`] - @hyperlane-xyz/sdk@5.0.0 ## @hyperlane-xyz/core@5.0.0 ### Patch Changes - 90598ad44: Removed outbox as param for ArbL2ToL1Ism - Updated dependencies [`388d25517`] - Updated dependencies [`488f949ef`] - Updated dependencies [`dfa908796`] - Updated dependencies [`1474865ae`] - @hyperlane-xyz/utils@5.0.0 ## @hyperlane-xyz/helloworld@5.0.0 ### Patch Changes - Updated dependencies [`2c0ae3cf3`] - Updated dependencies [`0dedbf5a0`] - Updated dependencies [`388d25517`] - Updated dependencies [`69a39da1c`] - Updated dependencies [`4907b510c`] - Updated dependencies [`488f949ef`] - Updated dependencies [`c7f5a35e8`] - Updated dependencies [`7265a4087`] - Updated dependencies [`0a40dcb8b`] - Updated dependencies [`f83b492de`] - Updated dependencies [`79740755b`] - Updated dependencies [`8533f9e66`] - Updated dependencies [`ed65556aa`] - Updated dependencies [`ab827a3fa`] - Updated dependencies [`dfa908796`] - Updated dependencies [`ed63e04c4`] - Updated dependencies [`5aa24611b`] - Updated dependencies [`cfb890dc6`] - Updated dependencies [`708999433`] - Updated dependencies [`5529d98d0`] - Updated dependencies [`62d71fad3`] - Updated dependencies [`49986aa92`] - Updated dependencies [`7fdd3958d`] - Updated dependencies [`8e942d3c6`] - Updated dependencies [`fef629673`] - Updated dependencies [`90598ad44`] - Updated dependencies [`be4617b18`] - @hyperlane-xyz/sdk@5.0.0 - @hyperlane-xyz/core@5.0.0 ## @hyperlane-xyz/infra@5.0.0 ### Minor Changes - 388d25517: Added HyperlaneRelayer for relaying messages from the CLI ### Patch Changes - Updated dependencies [`2c0ae3cf3`] - Updated dependencies [`0dedbf5a0`] - Updated dependencies [`388d25517`] - Updated dependencies [`69a39da1c`] - Updated dependencies [`4907b510c`] - Updated dependencies [`488f949ef`] - Updated dependencies [`c7f5a35e8`] - Updated dependencies [`7265a4087`] - Updated dependencies [`0a40dcb8b`] - Updated dependencies [`f83b492de`] - Updated dependencies [`79740755b`] - Updated dependencies [`8533f9e66`] - Updated dependencies [`ed65556aa`] - Updated dependencies [`ab827a3fa`] - Updated dependencies [`dfa908796`] - Updated dependencies [`ed63e04c4`] - Updated dependencies [`dfa908796`] - Updated dependencies [`5aa24611b`] - Updated dependencies [`cfb890dc6`] - Updated dependencies [`708999433`] - Updated dependencies [`5529d98d0`] - Updated dependencies [`62d71fad3`] - Updated dependencies [`49986aa92`] - Updated dependencies [`7fdd3958d`] - Updated dependencies [`8e942d3c6`] - Updated dependencies [`fef629673`] - Updated dependencies [`be4617b18`] - Updated dependencies [`1474865ae`] - @hyperlane-xyz/sdk@5.0.0 - @hyperlane-xyz/utils@5.0.0 - @hyperlane-xyz/helloworld@5.0.0 ## @hyperlane-xyz/ccip-server@5.0.0 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	4 months ago
Lee	d0f7f21fd4	fix(cli): hyperlane core apply logging fix (#4251 ) ### Description Fixes `hyperlane core apply` to say "Hyperlane Core Apply" ### Backward compatibility Yes ### Testing Manual	4 months ago
Trevor Porter	cffbfcac13	feat: fully testing ICA ownership with tooling (#4245 ) ### Description Some tweaks to get checker tooling working with ICA ownership: - changed the `inferCallSubmissionTypes` logic to no longer mutate `this.calls`. Some weird side effects were occurring, especially where the ICA logic would try to pop and push from `this.calls` while also looping over it. This is also why I made it serial again. I ended up moving away from mutating this.calls entirely during the iteration, so I guess moving back to doing it concurrently can be done again. Happy to do this if it feels good to - the only reason I haven't is this wasn't a place where we had huge inefficiencies and it'd complicate the code a little - Got it working where a Safe on chain A owns an ICA on chain B These are the flows I tested: - sepolia is the "owner chain" - deployed a warp route between sepolia and alfajores. Changed the alfajores owner to an ICA owned by the sepolia deployer key. Tested transferring ownership back from this to the deployer. - Did the exact same as above, but now with the ICA being owned by a Safe on sepolia - Transferred ownership of Alfajores core contracts to and from the sepolia-deployer-owned ICA These are some raw notes that may be of interest of what I did https://www.notion.so/hyperlanexyz/ICA-playground-996cf28aea1649a18051afb8bb82acb2 This doesn't auto-deploy ICAs. An ICA is expected to have been deployed already, and then just configured in `owners.ts`. Check-deploy figures out that it's an ICA and does all the rest. This is fine imo in the short term as I only imagine us using ICAs on two chains (inevm and viction) for the time being. ### 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
J M Rossy	69a39da1cf	fix(sdk): Access correct consensus client when estimating cosmwasm txs (#4249 ) ### Description `tmClient` (i.e. TendermintClient) is now `cometClient` ### Related issues Related to #4209 but not surfaced because of ts-ignore, which is necessary because the required data isn't surfaced properly by CosmJS ### Backward compatibility Yes ### Testing Tested in Warp UI	4 months ago
Paul Balaji	c6bf71d1b3	chore: update registry to v2.4.0 (#4247 ) chore: update registry to v2.4.0 - pinned CI version updated to `d9fea91f16949a51b2c8e776bac26712ba1fef3d`, which includes some testnet updates after 2.4.0 (https://github.com/hyperlane-xyz/hyperlane-registry/pull/126) --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	4 months ago
Yorke Rhodes	929760cf30	fix: revert "fix: enable metadata builder unit tests" (#4246 ) Reverts hyperlane-xyz/hyperlane-monorepo#4176 Fixes flakey metadata builder test	4 months ago
Mohammed Hussan	c21a99abf8	feat(infra): ensure check-deploy covers ownable ISMs (#4236 ) ### Description - check-deploy will surface violations when the on-chain ISM state differs from the config for core and warp modules Example of running check-deploy when the warp config includes a new validator Vs on-chain ISM state ``` ┌─────────┬────────────┬────────┬──────────────┬─────────────┬─────────┬──────────────────────────────────────────────┬──────────────────────────────────────────────┐ │ (index) │ chain │ remote │ name │ type │ subType │ actual │ expected │ ├─────────┼────────────┼────────┼──────────────┼─────────────┼─────────┼──────────────────────────────────────────────┼──────────────────────────────────────────────┤ │ 0 │ 'ethereum' │ │ │ 'ClientIsm' │ │ [Object] │ [Object] │ │ 1 │ 'ethereum' │ │ 'collateral' │ 'Owner' │ │ '0x3965AC3D295641E452E0ea896a086A9cD7C6C5b6' │ '0xa7ECcdb9Be08178f896c26b7BbD8C3D4E844d9Ba' │ └─────────┴────────────┴────────┴──────────────┴─────────────┴─────────┴──────────────────────────────────────────────┴──────────────────────────────────────────────┘ Connection client violation ClientIsm details: + Added to config staticAggregationIsm.modules.0.merkleRootMultisigIsm.validators.3: "0xbb5842ae0e05215b53df4787a29144efb7e67551" + Added to config staticAggregationIsm.modules.1.messageIdMultisigIsm.validators.3: "0xbb5842ae0e05215b53df4787a29144efb7e67551" ~ Updated config staticAggregationIsm.modules.0.merkleRootMultisigIsm.validators.0: "0x95c7bf235837cb5a609fe6c95870410b9f68bcff" -> "0x4d966438fe9e2b1e7124c87bbb90cb4f0f6c59a1" ~ Updated config staticAggregationIsm.modules.0.merkleRootMultisigIsm.validators.1: "0xa5a56e97fb46f0ac3a3d261e404acb998d9a6969" -> "0x95c7bf235837cb5a609fe6c95870410b9f68bcff" ~ Updated config staticAggregationIsm.modules.0.merkleRootMultisigIsm.validators.2: "0xbb5842ae0e05215b53df4787a29144efb7e67551" -> "0xa5a56e97fb46f0ac3a3d261e404acb998d9a6969" ~ Updated config staticAggregationIsm.modules.1.messageIdMultisigIsm.validators.0: "0x95c7bf235837cb5a609fe6c95870410b9f68bcff" -> "0x4d966438fe9e2b1e7124c87bbb90cb4f0f6c59a1" ~ Updated config staticAggregationIsm.modules.1.messageIdMultisigIsm.validators.1: "0xa5a56e97fb46f0ac3a3d261e404acb998d9a6969" -> "0x95c7bf235837cb5a609fe6c95870410b9f68bcff" ~ Updated config staticAggregationIsm.modules.1.messageIdMultisigIsm.validators.2: "0xbb5842ae0e05215b53df4787a29144efb7e67551" -> "0xa5a56e97fb46f0ac3a3d261e404acb998d9a6969" ``` ### Backward compatibility Yes ### Testing Manual	4 months ago
Trevor Porter	fe9365fdb3	chore: agent metric log tweaks (#4244 ) ### Description - some small tweaks as I looked into a recent issue with metrics ### 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
J M Rossy	5125b798df	feat(cli): Prompt for isTestnet when defining chain (#4240 ) ### Description Prompt for chain testnet/mainnet during chain definition flow <img width="893" alt="Screenshot 2024-08-01 at 2 13 48 PM" src="https://github.com/user-attachments/assets/b4e73e19-b1ab-4a01-a769-f9b1495457a9"> ### Testing Locally	4 months ago
Lee	c7f5a35e82	feat(sdk,cli): Add hyperlane core apply with update defaultIsm (#4224 ) ### Description - Adds update defaultIsm to CoreModule - - Create `hyperlane core apply --chain beta --config ./configs/core-config.yaml` - `--chain` is the only required arg - `--config` is the filepath to `core-config.yaml`, which defaults to `./configs/core-config.yaml` - This command relies on the registry artifacts (CHAIN/addresses.yaml), which is fetched by chainname ### Related issues https://github.com/hyperlane-xyz/issues/issues/1331 ### Backward compatibility Yes ### Testing Manual	4 months ago
Yorke Rhodes	6341edf2a2	fix: use merkle tree hook address from registry for self relay hook derivations (#4223 ) ### Description Circumvents bad hook derivation during self relay ### Related issues - Fixes https://github.com/hyperlane-xyz/issues/issues/1320 ### Backward compatibility Yes ### Testing manual warp send from sepolia origin --------- Co-authored-by: Noah Bayindirli 🥂 <15343884+nbayindirli@users.noreply.github.com>	4 months ago

... 3 4 5 6 7 ...

2685 Commits (70bb863e34f67c0e8de78fa33c938d80c9968364) All Branches Search

2685 Commits (70bb863e34f67c0e8de78fa33c938d80c9968364)

All Branches