hyperlane-monorepo

Commit Graph

Author	SHA1	Message	Date
J M Rossy	395a069e0d	Refactor ChainMetadata types (#2491 ) ### Description - Refactor ChainMetadata types into new folder - Create metadata extensions for deployment artifacts, and agent config - Remove explicit ChainMetadata interface and infer from zod schema instead ### Related issues Implements new schema discussed in: - https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/1867 - https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/2203 - https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2214 Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2214 ### Backward compatibility No: users of chain metadata configs would need to slightly modify their shape (the `rpcUrl` field)	1 year ago
Yorke Rhodes	e3e7a0aeb9	deploy middlewares (#2496 ) ### Description - Fix middleware addresses - Deploy ICA on testnet - Deploy IQS on testnet - Deploy middlewares to mainnet ### Drive-by changes - Add more tx overrides fixes to deployer ### Related issues - Fixes #2455 ### Backward compatibility No, new addresses ### Testing Fork tests	1 year ago
Trevor Porter	d12e3b966f	Deploy to solanadevnet & zbctestnet on testnet3 (#2412 ) ### Description * solanadevnet is on Solana Devnet, and zbctestnet is on the Eclipse/Zebec rollup testnet found at https://api.zebec.eclipsenetwork.xyz:8899/ * Deploys validators to our infra on testnet3 for `solanadevnet` and `zbctestnet`. These run on the `hyperlane` context. * Added the ability to set the docker image / tag for specific chain deployments. This way we can run the sealevel validators with their own image without affecting the other deployments * Deployed a sealevel-supporting relayer to rc that relays messages for solanadevnet and zbctestnet * Some minor changes to key management - e.g. the recent change to `getCloudAgentKey` wasn't effective because relayer keys don't ever specify their own chain * Added a `--protocol` flag to the get-key-addresses command so we can view keys for different protocols Everything works really well! messages are being delivered Validator sets: ``` - solanadevnet: { - threshold: 2, - validators: [ - '0xec0f73dbc5b1962a20f7dcbe07c98414025b0c43', - '0x9c20a149dfa09ea9f77f5a7ca09ed44f9c025133', - '0x967c5ecdf2625ae86580bd203b630abaaf85cd62', - ], - }, - zbctestnet: { - threshold: 2, - validators: [ - '0xf33cca115fd1bc888b31f5ce96c0277e3af31120', - '0xc1a44a2ff3379e0dfa4ccf7e8b98bdc3012721be', - '0x1ec68fea9a0698a0d2b396770e7d2d61d9a3e654', - ], - }, ``` ### Drive-by changes n/a ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2288 - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2289 ### Backward compatibility _Are these changes backward compatible?_ Yes _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing _What kind of testing have these changes undergone?_ Deployed! --------- Co-authored-by: Asa Oines <asaoines@gmail.com>	1 year ago
Kunal Arora	7c872bc449	5164 hook support (#2471 ) ### Description - Adding support for any ERC-5164 compatible bridge adapter to be added as a hook. See https://eips.ethereum.org/EIPS/eip-5164 for more details on the EIP and https://github.com/MultiMessageAggregation/multibridge for adapter implementations for different vendors. ### Drive-by changes - Switched mapping(bytes32 => mapping(address => true) to mapping(bytes32 => bytes) for verifedMessageIds because the last boolean is redundant in the AbtrsactNativeISM contract. ### Related issues - Fixes #2417 ### Backward compatibility _Are these changes backward compatible?_ Yes _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing _What kind of testing have these changes undergone?_ Unit Tests	1 year ago
Daniel Savu	02b644d20f	fix(validator): make announce error msg more generic over chains (#2481 ) ### 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?_ Yes No _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None Yes ### Testing _What kind of testing have these changes undergone?_ None Manual Unit Tests	1 year ago
Yorke Rhodes	60f321f452	docs: elaborate on censorship resistance of two ISMs. (#2474 ) ### Description Changes from https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/2425 --------- Co-authored-by: serejke <serejke.best@gmail.com>	1 year ago
Yorke Rhodes	e92d3410fc	Add markdown docs generation (#2437 ) ### Description Adds markdown doc generation to solidity and token package May be preferable to our gitbook contract API docs	1 year ago
J M Rossy	7ff83bbd0b	Fix checkConfig in HyperlaneRouterDeployer (#2469 ) - Fix checkConfig in HyperlaneRouterDeployer - Bump packages to 1.3.7	1 year ago
Daniel Savu	6ee5868353	fix(validator): announce directly if no gas estimate (#2454 ) ### Description It has been reported that `contract_call.tx.max_cost()` can fail / not exist on some networks. When that's the case, default to assuming no additional validator gas is required and just send the tx. If the tx fails, report the failure and suggest that gas may be insufficient in the logged error. ### Drive-by changes None ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2426 ### Backward compatibility _Are these changes backward compatible?_ Yes _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing _What kind of testing have these changes undergone?_ None --------- Co-authored-by: Nam Chu Hoai <nambrot@googlemail.com>	1 year ago
Daniel Savu	7889385501	Relayer aggregation ism (#2411 ) ### Description Adds AggregationISM support to the relayer, by adding the scaffolding, sub-ism metadata fetching, and custom metadata encoding. ### Drive-by changes - adds `dry_run_verify(...)` to the `InterchainSecurityModule` trait and implements it for `EthereumInterchainSecurityModule` - changes the default ISM in the test environment from `routingIsm(multisigIsm)` to `routingIsm(aggregationIsm([multisigIsm, messageIdIsm], threshold = 1))` ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/1757 ### Backward compatibility _Are these changes backward compatible?_ Yes _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing The AggregationISM metadata encoding is tested using unit tests whose input was taken from the tests in `AggregationIsm.t.sol`, by printing the individual ISM metadatas and the final metadata. The overall AggregationISM is tested with the `run-locally` script.	1 year ago
Mattie Conover	16a29edb00	Dedup chain parsing (#2464 ) ### Description Missed this by accident from #2249 ### Drive-by changes None ### Related issues ### Backward compatibility _Are these changes backward compatible?_ Yes _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing _What kind of testing have these changes undergone?_ Unit Tests	1 year ago
Mattie Conover	420383eb54	Treat chain names as lowercase (#2249 ) ### Description Had to do a little digging but I think this should fix not only the issue that was encountered but fully add support for whatever case they want, it will just treat it as lowercase but still display it correctly for their config paths. The problem was that `HyperlaneDomain` was already lowercasing the name but we didn't lowercase the key that we used in `from_config_filtered` for the base `RawSettings` to look it up during parsing so we couldn't find the values. ### Drive-by changes None ### Related issues - Fixes #2103 ### Backward compatibility _Are these changes backward compatible?_ Yes _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing _What kind of testing have these changes undergone?_ None	1 year ago
Trevor Porter	35332f464c	Release 1.3.6 (#2451 ) ### Description Released 1.3.6, mostly to include #2445 and #2402 ### Drive-by changes n/a ### Related issues In the name of https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2366 ### Backward compatibility _Are these changes backward compatible?_ Yes _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing _What kind of testing have these changes undergone?_ None	1 year ago
Yorke Rhodes	2e2e0ffadb	Add proxy upgrade timelocks to deployer and checker (#2151 ) ### Description Adds `TimelockController` deployment code to `CoreDeployer`. If a `upgradeTimelockDelay` is configured on `CoreConfig`, this contract will be deployed. The `ProxyAdmin` will be owned by this contract, and the configured `owner` will have proposer, executor, and canceller roles on the timelock. ### Drive-by changes Configures `arbitrum` with `upgradeTimelockDelay: 7 days`. ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/1717 - Fixes https://github.com/hyperlane-xyz/issues/issues/503 ### Backward compatibility Yes ### Testing SDK unit tests and fork tests against arbitrum	1 year ago
Yorke Rhodes	b1a924d5b8	Remove submodule references from README.md (#2436 )	1 year ago
Daniel Savu	5d05e58470	fix(contract_sync): saturating math in eta calculator (#2453 ) ### Description It was observed that this function can be called with a `last_block` that is greater than the `currenct_block`, which results in an underflow. Use saturating math to prevent this. ### Drive-by changes ### Related issues ### Backward compatibility _Are these changes backward compatible?_ Yes _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing _What kind of testing have these changes undergone?_ None	1 year ago
Yorke Rhodes	fc5698d7af	Fix compiler warning on token contracts (#2447 ) ### Description Fixes `Warning: This declaration shadows an existing declaration.` on token `yarn build`	1 year ago
Yorke Rhodes	aab8f19f8a	Add codecov github action (#2449 ) ### Description Adds simplest viable codecov setup	1 year ago
Trevor Porter	b98d882efe	Use configured collateral token metadata (#2445 ) ### Description Just copying the changes from https://github.com/hyperlane-xyz/hyperlane-token/pull/73, which I unfortunately didn't get in before the absorption ### Drive-by changes _Are there any minor or drive-by changes also included?_ ### Related issues In the name of #2366 ### Backward compatibility _Are these changes backward compatible?_ Yes _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing _What kind of testing have these changes undergone?_ Unit Tests, used it in hyperlane-deploy when deploying synthetic tokens relating to a collateral warp route that lives on Solana	1 year ago
Trevor Porter	8e8e47236b	Fix misleading config error to do with connection configs (#2444 ) ### Description If you don't specify a connection config, atm the error message says you're missing the `domain`. I ran into this previously and found it hard to debug; a validator operator in discord also ran into this ### Drive-by changes n/a ### Related issues n/a ### Backward compatibility _Are these changes backward compatible?_ Yes _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing _What kind of testing have these changes undergone?_ None	1 year ago
Yorke Rhodes	fcb1bebb96	Bump hardhat and solidity-coverage versions (#2433 ) ### Description Bumps solidity coverage and hardhat versions to (hopefully) fix CI coverage flakiness Also bumps node version following https://github.com/NomicFoundation/hardhat/pull/4075	1 year ago
Daniel Savu	61892d1d5a	feat(fallback provider): re-prioritize providers on error (#2369 ) ### Description Closes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2189 Reprioritize providers in the `FallbackProvider` when they stop receiving new blocks (although a `max_block_time` has elapsed). The `JsonRpcClient::request(...)` implementation now takes a snapshot of the provider priority list and iterates on that. This is to minimize lock contention - no lock is held across an `await` so there is no deadlock risk. If one of the errors above occurs, the priority list is overwritten. Note this may cause a prior reprioritization to be lost, if the repriotization occured after the current tokio task's snapshot was taken. I'm not entirely sure whether a specific `FallbackProvider` is referenced by more than one task at a time though. ### Drive-by changes A `PrometheusJsonRpcClientConfigExt` trait is added, so the provider can be mocked. ### Testing Unit tests.	1 year ago
Daniel Savu	fdc86f687c	Reconstruct relayer `OpQueue` from HyperlaneDB (#2382 ) ### Description Stores the `num_retries` field of `PendingMessage` at its own prefix in HyperlaneDB, so that `PendingMessage` can be reconstructed with the same exponential backoff in the `next_attempt_after` field and avoid making unnecesary RPC calls on restart. To use persisted data, `PendingMessage` is constructed with `from_persisted_retries` instead of the default constructor. If reading from the db fails, the new constructor just defaults to the regular constructor, so it's worth considering replacing the regular constructor with this one entirely. ### Drive-by changes A new db prefix is added (`PENDING_MESSAGE_RETRY_COUNT_FOR_MESSAGE_ID `), as well as related getter / setter methods. Using the new prefix helps avoid a migration. I do see a `processed_by_nonce` prefix, which could be migrated to store data related to `PendingMessage` in general so let me know what you think. Could be a future improvement to merge its prefix with the prefix added in this PR. ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/1902 ### Backward compatibility _Are these changes backward compatible?_ Yes _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing _What kind of testing have these changes undergone?_ A processor is run on some dummy database entries. The `SerialSubmitter`'s end of the channel is used to ensure that the incoming `PendingMessage`s have the correct backoff in `_next_attempt_after`.	1 year ago
Mattie Conover	81ec08ffdc	Fix agent release pipeline (#2428 ) ### Description Fixes the agent artifact release pipeline's failing linux build. Created the branch `mattie/release-artifacts` to actually publish a version based on released version. ### Drive-by changes None ### Related issues - Fixes #2431 ### Backward compatibility _Are these changes backward compatible?_ Yes _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing _What kind of testing have these changes undergone?_ Manual	1 year ago
Yorke Rhodes	c12a896d50	Absorb token and helloworld submodules (#2435 ) It is very painful to update any dependencies across repos and publish new releases due to submodule juggling. Fresh clones are also broken. Removes token and helloworld submodules and merges in as regular version tracked packages to same path. Followed https://nuclearsquid.com/writings/subtree-merging-and-you/ for preserving history.	1 year ago
Yorke Rhodes	f235e4ce0f	Add solhint to helloworld and token	1 year ago
Yorke Rhodes	a147bdc620	Fix token CI	1 year ago
Yorke Rhodes	638b3f5474	Unify lint configs	1 year ago
Yorke Rhodes	d0b2a6a249	Fix sdk lint	1 year ago
Yorke Rhodes	ebaf652192	Fix builds and tests	1 year ago
Yorke Rhodes	d9cd552c62	Merge CI configs	1 year ago
Yorke Rhodes	16146f0f03	Absorb helloworld	1 year ago
Yorke Rhodes	11d9d0bf0d	Absorb token	1 year ago
Mattie Conover	0ed4e84406	Deployed scraper (#2432 ) ### Description Updated the scraper to fix a metric issue. ### Drive-by changes None ### Related issues ### Backward compatibility _Are these changes backward compatible?_ Yes _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing _What kind of testing have these changes undergone?_ Manual	1 year ago
Kunal Arora	445da4fb0d	Adding Optimism native bridge support (#2316 ) ### Description - Adds support for the native Optimism bridge (L1->L2) to send messageID to be verified by the custom ISM on the rollup. - Only the smart contract component. - Outside Mailbox and needs to be called separately. - Uses Openzeppelin's CrossChainEnabled pattern for ensuring the right cross chain sender address. ### Drive-by changes - None ### Related issues - Fixes https://github.com/hyperlane-xyz/issues/issues/379 - Opens https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2409 - Related to https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2381 ### Backward compatibility - Needs modifying the relayer to read OptimismISM's storage to wait for `receivedEmitters` mapping to get updated before retrying `process` on the mailbox. ### Testing - Unit Tests with Foundry forks and Optimism's L1-L2 messenger contracts. --------- Co-authored-by: Asa Oines <asaoines@gmail.com>	1 year ago
Nam Chu Hoai	73651d1e46	Scale down gnosis validators to 1 (#2407 ) Scale down gnosis validators to 1	1 year ago
Asa Oines	aaddba776b	Fix latest indexed block gauge (#2387 ) ### Description This PR fixes a bug that affected the latest indexed block gauge for message_dispatch. This allows the gauge to be updated to the "correct" value whether or not a getLogs query actually takes place. ### Drive-by changes None	1 year ago
Asa Oines	e317c6c85d	Sealevel chains should always use hex keys for relayers (#2402 ) ### Description This PR adds support for protocol-type awareness in infra. A new field `type` is added to chainMetadata. This field is inspected during key creation and relayer helm chart creation. Relayer keys for sealevel chains are set explicitly to always be hex keys. ### Drive-by changes None ### Related issues - https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2350 ### Backward compatibility _Are these changes backward compatible?_ Yes	1 year ago
Trevor Porter	4bf065548c	Bump to 1.3.5 (#2401 ) ### Description Releases 1.3.5, mostly to include #2392 ### Drive-by changes n/a ### Related issues - Part of #2366 ### Backward compatibility _Are these changes backward compatible?_ Yes _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing _What kind of testing have these changes undergone?_ None	1 year ago
Trevor Porter	6992a4cc1f	Bump to 1.3.5 (#72 ) * Bump @hyperlane-xyz/* dependencies to 1.3.5 * Bump to 1.3.5	1 year ago
Trevor Porter	a20d5f9b74	1.3.5 (#55 )	1 year ago
Daniel Savu	1921c45885	chore(relayer): improve ISM address error message (#2345 ) Closes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2090 Recent improvements from https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/2195 already catch the error in that user report. This PR just adds a hint as to why fetching may have failed; in that report, the user's `fallback` function was returning an empty value which caused casting to an `address` to fail and revert, so the error occurs because the returned value is malformed. Thanks to @tkporter for walking me through the contracts to better understand the scope of https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2090.	1 year ago
Trevor Porter	186fcdab36	Existing deployment support in Router tooling, small ISM factory fixes (#2392 ) ### Description To accommodate warp routes that exist on EVM chains and other execution environments, we need the ability to enroll remote routers on EVM-based routers that weren't deployed by the router deployer. This adds a new optional `existingDeployment` property to the `RouterConfig`, which means that deployment will not be attempted to this chain, but it will be enrolled as a remote router on any contracts that are deployed to. The general flow looks something like: * Deploy the warp route contracts on all EVM chains, enrolling each other as routers * Deploy the warp route contracts on the alt execution environment chains, also configuring the existing EVM contract deployments as `existingDeployment`s so that they are enrolled as routers on the alt execution environment contracts * Now equipped with all the router addresses, any new non-EVM router addresses are configured as `existingDeployment`s, which now enrolls these routers on the EVM chains Note there's still a lot left to be desired even with this change -- e.g. much of the tooling expects the MultiProvider to include metadata (& even providers) for each and every chain. Because the MultiProvider is of course EVM only, things get a bit weird. For now, I've been able to deploy warp routes with configs relating to a sealevel chain successfully by just running a local Anvil instance and setting the RPC URL of the sealevel config to that anvil instance. We'll want to readdress this at some point, but for now I'd prefer to have a flow that just works and we can be more intentional about bigger deploy / tooling changes to support alt execution environments in the future This also includes some small changes to the ISM factory - because we werent actually waiting for the `enrollValidators` tx to succeed before trying `setThreshold`, the gas estimation of `setThreshold` would fail because the threshold of 1 exceeded the current on-chain validator set size of 0. It also sometimes resulted in nonce contention I was able to get everything in hyperlane-deploy working locally by having dependencies be local filepaths The order of operations for things iiuc looks like: 1. Merge this 2. Ship new SDK version 3. Update hyperlane-token to use this new SDK version 4. Ship new hyperlane-token version 5. Update hyperlane-deploy to use the new SDK version and the new hyperlane-token ### Drive-by changes none ### Related issues - partially https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2366 ### Backward compatibility _Are these changes backward compatible?_ Yes _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing _What kind of testing have these changes undergone?_ unit tests, ran deploy tooling	1 year ago
Yorke Rhodes	feb6d2b4e9	Release new validators internally (#2390 ) ### Description Updates hyperlane context mainnet2 and testnet3 validator image tags (to whats already deployed)	1 year ago
Asa Oines	c445869793	Deploy scraper to testnet3 (#2351 ) ### Description With tag `2deb9b8-20230602-205342`	1 year ago
Asa Oines	663115d716	Deploy mainnet scraper (#2376 ) ### Description Updates the deployment to pick up #2375	1 year ago
Nam Chu Hoai	60ce3a5f4b	Deploy testnet3 key funder with quorum (#2307 ) Deploy testnet3 key funder with quorum	1 year ago
Yorke Rhodes	497db63f5b	Prevent AWS KMS throttling in validator (#2391 ) ### Description Observed in validator ``` Request ID: Some("c0cc123e-da52-47f4-a2d3-aeddd034a2f5") Body: {"__type":"ThrottlingException","message":"You have exceeded the rate at which you may call KMS. Reduce the frequency of your calls."} ``` - Add sleep and checkpoint sync cache for rate limit ### Drive-by changes - Skip tree in checkpoint submitter span ### Backward compatibility Yes ### Testing Local testing	1 year ago
Yorke Rhodes	1fff74ebd8	Reduce hyper client pool idle timeout to 20s (#2384 ) ### Description - configures hyper http client to close connections after 20s - makes singleton signer retry (5) times before bubbling error up ### Backward compatibility Yes ### Testing Local binary testing against cloud resources ![Screen Shot 2023-06-13 at 5 45 47 PM](https://github.com/hyperlane-xyz/hyperlane-monorepo/assets/3020995/de47a03c-b40f-49fd-a32d-c8da6ecffa6e)	1 year ago
Asa Oines	b75cfc4c6b	Start scraper message_dispatch sync from high watermark (#2377 ) ### Description This PR addresses an issue in which BSC RPC providers have a very hard time providing very old transactions. This caused BSC scraping to fail, since the scraper had never actually indexed very early BSC messages (e.g. nonce 0). By starting at the latest scraped nonce - 1, the scraper will bypass this issue. ### Drive-by changes None	1 year ago

1 2 3 4 5 ...

1621 Commits (395a069e0de7ec35118f6f65ef598e3b4026ece1) All Branches Search

1621 Commits (395a069e0de7ec35118f6f65ef598e3b4026ece1)

All Branches