hyperlane-monorepo

Commit Graph

Author	SHA1	Message	Date
Nam Chu Hoai	0779a23db6	refactor: Rename InterchainAccountRouter tests for easier reuse (#4336 ) ### Description Minor refactor of test	3 months ago
Mohammed Hussan	cab86f2f97	feat(sdk): Support proxyAdmin checks for admins not owned by AW (#4338 ) ### Description - Support checking proxyAdmin owners for non AW proxy admins - Stop assuming all proxyAdmins will be owned by AW - This change was motivated by the need to have our checker tooling check Renzo Wapr routes, where Renzo owns the proxy routers ### Drive-by changes - Clean up the interface for `ProxyAdminViolation` ### Testing Manual	3 months ago
Lee	da55df5b4a	fix(sdk): Update smart provider logging to debug (#4344 ) ### Description This stops deriving errors such as `hyperlane ism read --address 0xc6608b648111020719d85163017a0dd2c9943d69 --chain fraxtal` ### Testing Manual	3 months ago
Lee	a6d3d12ce2	fix: Update renzo zircuit validator set (#4343 ) Should match default Ism: `1abefa60e2/typescript/sdk/src/consts/multisigIsm.ts (L539-L542)`	3 months ago
Mohammed Hussan	1abefa60e2	feat(checkToken): Support checking token config for xERC20Lockbox type (#4339 ) ### Description - When setting up the warp configuration for an `xERC20Lockbox` contract, we pass the lockbox address in the token field for the config and we lookup the underlying ERC20 token in the smart contract constructor `1579ca221c/solidity/contracts/token/extensions/HypXERC20Lockbox.sol (L17)` - This change accounts for this setup when checking for `CollateralTokenMismatch` violations ### Testing Manual	3 months ago
Paul Balaji	4f19b9fae6	feat: add stride validators to default multisig (#4315 ) feat: add stride validators to default multisig	3 months ago
Trevor Porter	6c2f01f83a	chore: add back Osmosis relaying / validator (#4335 ) ### Description - seems I accidentally disabled optimism relaying before, yikes - adding back for Skip to play around with ### 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
Kunal Arora	6f377f1743	feat: implement `OPL2ToL1Ism` contracts (#4319 ) ### Description Implementing the `OPL2ToL1Hook` and OPL2ToL1Ism` contracts for using the Optimism native bridge for sending messages from the L2 to L1. - Optimism needs double call encoding for the direct portal call because the portal itself calls the l1Messenger which then directs it to the ism. ### Drive-by changes None ### Related issues - fixes https://github.com/hyperlane-xyz/issues/issues/1346 ### Backward compatibility Yes ### Testing Unit testing with mocks for OP contracts	3 months ago
Trevor Porter	cc8624d687	chore: fix key funder errors, lower some thresholds (#4333 ) ### Description - updated the image to include the sei gas price fix #4321 - lowered a bunch of thresholds for some newer chains that could be lower based off looking at the fees / available balances. Also bridged some funds over to them ### 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
J M Rossy	06180b060b	chore: Enable no-restricted-imports eslint rule (#4329 ) ### Description Incorrect imports from node-specific global libs, especially for `assert` are very common. This won't catch all possible mistakes but it will help avoid future problems like https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4327 ### Backward compatibility Yes	3 months ago
Lee	580f6c109e	fix(sdk): Remove console.assert (#4327 ) ### Description warp template UI throws ![image](https://github.com/user-attachments/assets/af854dee-ee0c-480c-b688-66f35642ba69) ### Backward compatibility Yes ### Testing Manual	3 months ago
Trevor Porter	57bbb16cc1	feat: panics upon startup when RPC issues occur include the offending chain (#4323 ) ### Description Some quick low hanging fruit to make debugging easier in the future. Today (https://discord.com/channels/935678348330434570/1273582453889699843) some chains were having RPC issues and it caused an agent deploy to panic upon startup. Debugging this was hard because the panic message just indicates an error is occurring, but doesn't say what the offending chain is! Examples: - https://cloudlogging.app.goo.gl/puQk7hm4fXyJhYKs8 - https://cloudlogging.app.goo.gl/5qZrbc2Ww4LWQXWC6 - https://cloudlogging.app.goo.gl/ZL7mKbBzzJaePtty9 All these panic happen when constructing the cursor, which isn't yet done in an indexing task. The quick and easy fix is to just use expect instead of unwrap We still unwrap in a few places, but mostly in places that aren't susceptible to flaky RPC issues, e.g. reading from a HashMap that we know should always have an entry, etc ### 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
Trevor Porter	ddf6834c7b	chore: drop some labels in remote writes to lower cardinality (#4326 ) - Labels chosen by looking at https://abacusworks.grafana.net/d/cardinality-management/cardinality-management-1-overview?var-datasource=grafanacloud-prom&from=2024-08-15T11:34:34.928Z&to=2024-08-16T11:34:34.929Z - Motivating case: a GKE rolling upgrade recently resulting in some issues with the remote write where it complained about too many series https://abacusworks.grafana.net/d/cdn9jukg55bswb/usage-insights-5-metrics-ingestion?var-instance=$__all&viewPanel=panel-9&from=2024-08-16T10:04:52.962Z&to=2024-08-16T11:04:52.962Z (thread https://discord.com/channels/935678348330434570/1273952173037715458) - Many of these labels would change whenever a pod would be restarted, a new deploy occurred, new nodes set up, etc - Deployed to testnet4 and mainnet3 and observed the labels were dropped ### 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 -->	3 months ago
Mohammed Hussan	9680efc3b1	feat(infra): Update warp configs in infra (#4299 ) ### Description - update the warp configs in infra to reflect expected behavior or change behavior ### Drive-by changes - allow fork script to support passing warp route id ### Testing Manual	3 months ago
Mohammed Hussan	1516e7f51b	feat(HypERC20App): Support proxiedFactories in HypERC20App, extend HypERC20Checker with ProxiedRouterChecker (#4312 ) ### Description - Extend `HypERC20Checker` with `ProxiedRouterChecker` so we can check for proxyAdmin violations (`checkProxiedContracts` is call in `checkChain`) - Support passing `proxiedFactories` to `HypERC20App` ### Fixes - #4325 ### Testing Manual	3 months ago
Lee	19ea053845	fix(sdk): Add collateralFiat support into Token.ts & TokenStandard.ts (#4308 ) ### Description Adds CollateralFiat to token mapping which will output the correct `standard` to the warp deploy artifact. ### Related issues https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4307 ### Backward compatibility Yes ### Testing Manually tested with Beta (collateral) -> Gamma (CollateralFiat) 1. Deploy an ERC20 to represent USDC on beta ``` forge create contracts/test/ERC20Test.sol:ERC20Test \ --constructor-args "Test" "TS" 10000000000000000000000000 6 \ --rpc-url https://beta-op.rpc.caldera.xyz/http \ --private-key $HYP_KEY ``` 2. Deploy a CollateralFiat on gamma ``` forge create contracts/test/ERC20Test.sol:FiatTokenTest \ --constructor-args "FiatTest" "FTS" 0 6 \ --rpc-url https://rpc-gamma-2bgo7wnh9d.t.conduit.xyz \ --private-key $HYP_KEY ``` 3. warp init and deploy 4. Start up the ts relayer `hyperlane relayer --chains beta,gamma` 5. Add the deploy artifacts to UI ``` # warpRoutes.yaml tokens: - chainName: beta standard: EvmHypCollateral decimals: 6 symbol: TS name: Test addressOrDenom: "0x56D13Eb21a625EdA8438F55DF2C31dC3632034f5" collateralAddressOrDenom: "0x9BcC604D4381C5b0Ad12Ff3Bf32bEdE063416BC7" connections: - token: ethereum\|gamma\|0xA7c59f010700930003b33aB25a7a0679C860f29c - chainName: gamma standard: EvmHypCollateralFiat decimals: 6 symbol: TS name: Test addressOrDenom: "0xA7c59f010700930003b33aB25a7a0679C860f29c" collateralAddressOrDenom: "0xD5ac451B0c50B9476107823Af206eD814a2e2580" connections: - token: ethereum\|beta\|0x56D13Eb21a625EdA8438F55DF2C31dC3632034f5 # chains.yaml beta: displayName: Beta chainId: 7097927 domainId: 7097927 protocol: ethereum name: beta isTestnet: true rpcUrls: - http: https://beta-op.rpc.caldera.xyz/http nativeToken: symbol: ETH name: Ether decimals: 18 gamma: blockExplorers: - apiUrl: https://explorer-gamma-2bgo7wnh9d.t.conduit.xyz family: blockscout name: gamma explorer url: https://explorer-gamma-2bgo7wnh9d.t.conduit.xyz chainId: 69995 displayName: Gamma domainId: 69995 isTestnet: true name: gamma nativeToken: decimals: 18 name: Ether symbol: ETH protocol: ethereum rpcUrls: - http: https://rpc-gamma-2bgo7wnh9d.t.conduit.xyz ``` 7. Start up UI	3 months ago
Trevor Porter	beab39c43c	chore: update sei gas price, temporarily stop deploying to osmosis (#4321 ) ### Description Following https://seitrace.com/proposal/83?chain=pacific-1, need a higher gas price ### 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	279516f280	chore: enroll worldchain, xlayer, cheesechain, zircuit validators (#4313 ) - chore: enroll worldchain, xlayer, cheesechain, zircuit validators - fix: update cosmos zod schema - drive-by: update core checker to check if the ism in registry matches the expected config	4 months ago
Yorke Rhodes	0d544d97e5	chore: use new forge feature for filtering coverage (#4318 ) ### Description - Remove lcov toolchain from coverage script in favor of new native forge features - Require strictly increasing project coverage ### Drive-by changes - Add coverage gutters to vscode recommendations for inline view ### Backward compatibility Yes ### Testing See codecov report comment	4 months ago
Lee	5dfa2d54e6	fix(infra): Sort Renzo validators (#4317 ) As requested by @Mo-Hussain to aid deploy checker	4 months ago
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 -->	4 months ago
Lee	4a1972903e	fix(cli): incorrect command for new chains (#4285 ) ### Description Fixes the new chain message to display the correct command	4 months ago
Yorke Rhodes	4425c69991	fix: solidity coverage failing due to fixture issue (#4304 ) ### Description Fixes solidity coverage reporting ### Testing CI Tests	4 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	4 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	4 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	4 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 -->	4 months ago
Paul Balaji	d274c6b3f8	chore: update registry to v2.5.0 (#4302 ) chore: update registry to v2.5.0	4 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	4 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>	4 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	4 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	4 months ago
Paul Balaji	2d922805c0	feat: add arbitrumsepolia, basesepolia, ecotestnet, optimismsepolia, polygonamoy to core chains (#4297 ) Deploy to arbitrumsepolia, basesepolia, ecotestnet, optimismsepolia, polygonamoy	4 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	4 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	4 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>	4 months ago
Paul Balaji	7625bf8dce	fix: typo in trait builder log (#4292 ) - fix: typo in trait builder log - noticed while looking at scraper logs	4 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' │ └─────────┴────────────┴────────┴──────────────┴──────────────┴─────────┴──────────────────────────────────────────────┴──────────────────────────────────────────────┘ ```	4 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	4 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

... 5 6 7 8 9 ...

2805 Commits (1574a3f2b4c1ec88378084e6e130360e8ba1036e) All Branches Search

2805 Commits (1574a3f2b4c1ec88378084e6e130360e8ba1036e)

All Branches