174 Commits (d224c060d41c6974a5611f554c8da280daf02d3a)

Author	SHA1	Message	Date
Kunal Arora	0e10306d4b	Adding Optimism Hook and dispatch with metadata (#2580) ... Use mailbox callback to authenticate messages in hooks where necessary (#2609) Co-authored-by: Kunal Arora <55632507+aroralanuk@users.noreply.github.com>	1 year ago
Yorke Rhodes	06124b441a	Add `receive` fn to `HypNative` and `Scaled` variant (#2671) ... Co-authored-by: Trevor Porter <trkporter@ucdavis.edu> Co-authored-by: Nam Chu Hoai <nambrot@googlemail.com>	1 year ago
Yorke Rhodes	d7da566e75	Update CODEOWNERS (#2715)	1 year ago
Mattie Conover	e4220f8412	Better node env testing (#2677) ... Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>	1 year ago
Mattie Conover	8cbfd3cbc0	Support 64-byte txn ids (attempt 2) (#2612) ... ### Description Adds support to TxOutcome for 512-bit ids and to log meta to support Solana. Now that we have primitive types in our crate we were able to create a better solution than before which just stores the EVM 256bit hashes inside of the 512bit one with leading zeros rather than needing to over engineer an enum container for it. ### Drive-by changes - Removed some dead code - Improved primitive type support for 512bit types - Improved serialization support for 512bit types ### Related issues - Fixes #2252 - Replaces #2256 ### Backward compatibility _Are these changes backward compatible?_ Yes-ish, changes one of the internal database key strings. At standup we discussed the possibility of migrating the data and concluded that was a can of worms we did not want to open. _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	9ed3a24902	Solana e2e tests (#2578) ... ### Description Adds support for testing solana with the e2e tests. This involves 1) Downloading the pre-built solana cli tools 2) Setting up the solana configuration 3) Downloading the pre-built solana programs we need (see https://github.com/hyperlane-xyz/solana-program-library/releases/) 4) The solana programs in the repo 5) Start the solana validator 6) Deploy the solana programs 7) Deploy a warp route 8) Initialize the multisig ism and validator announce 9) Initialize a transfer 10) Wait for the message to be delivered In addition these were "woven" in with the existing E2E test logic, so for instance we only run one new validator and the existing relayer was extended to support these additional chains. This will make it much easier later on to support testes between environments. ### Drive-by changes - Fix a bug in the relayer when trying to index the mailbox - Add support in the hyperlane sealevel CLI for custom solana config paths - Fix a linker error on linux causes by not specifying `no-entrypoint` - Cleaned up unnecessary `no-entrypoint` features in libraries - Minor refactor to how we run commands to avoid arg passing - Created an easy way to define tasks that run asyncly `as_task` - Split up main logic flow into a couple files for easier reading - Use mold linker to speed up builds (well, the linking part) - Removed support for `log_all` to simplify code pathways - Added context when a child process ends unexpectedly for easier debugging - Fixed a bug in the validator where it would infinitely retry to send an announcement on failure without waiting - Cleaned up solana configs - Fixed processes hanging on exit (very annoying when testing locally since you have to manually go kill them) - Added stderr logging to the hyperlane sealevel CLI subprocess calls ### Related issues Fixes #2415 ### Backward compatibility Yes ### Testing Manual	1 year ago
Trevor Porter	8c5983933b	Sealevel (#2404) ... ### Description Opening for that sweet sweet agent image ### Drive-by changes _Are there any minor or drive-by changes also included?_ ### Related issues - Fixes #[issue number here] ### Backward compatibility _Are these changes backward compatible?_ 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 --------- Co-authored-by: Steven Sloboda <steven@eclipse.builders> Co-authored-by: Nam Chu Hoai <nambrot@googlemail.com> Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz> Co-authored-by: J M Rossy <jm.rossy@gmail.com> Co-authored-by: Mattie Conover <git@mconover.dev> Co-authored-by: Asa Oines <asaoines@gmail.com> Co-authored-by: Sergei Patrikeev <serejke.best@gmail.com> Co-authored-by: Daniel Savu <23065004+daniel-savu@users.noreply.github.com> Co-authored-by: Kunal Arora <55632507+aroralanuk@users.noreply.github.com> Co-authored-by: yorhodes <yorkerhodesiv@gmail.com> Co-authored-by: Yorke Rhodes <yorke@useabacus.network> Co-authored-by: Yorke Rhodes <email@yorke.dev> Co-authored-by: Asa Oines <asaoines@Asas-MacBook-Pro.local> Co-authored-by: Kunal Arora <kuarora@ucsd.edu> Co-authored-by: Anett <44020788+anettrolikova@users.noreply.github.com> Co-authored-by: Yaqub Mahmoud <yaqub320@gmail.com> Co-authored-by: Alex <alex@alexbh.dev>	1 year ago
Kunal Arora	e91be529db	AggregationISM set for rc kathy (#2517) ... ### Description - Using a separate set of validators for RC deployments and tests - Defining a recursive AggregationISM config which aggregates over two RoutingISMs, one for a set of MerkleRootMultisigISMs and one for a set of MessageIdMultisigISMs for each origin domain. ### Drive-by changes - Dployed MerkleRootMultisigISMFactory and MessageIdMultisigISMFactory for testnet3 in hyperlane context ### Related issues - Fixes #2224 ### Backward compatibility Backward compatible? Yes Any infrastructure implications? HyperlaneRouterChecker will fail silently if you provide an IsmConfig - #2534 ### Testing Manual Testnet --------- Co-authored-by: Yorke Rhodes <email@yorke.dev> Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>	1 year ago
Alex	da25b06254	CCIP Read ISM (#2398) ... ### Description CCIP Read ISM implementation, - [x] Contracts - [x] Relayer - [x] Example HTTP backend ### Drive-by changes _Are there any minor or drive-by changes also included?_ ### Related issues - Fixes #[2211] ### Backward compatibility _Are these changes backward compatible?_ Yes, relayers will skip messages they can't handle. _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ Yes, relayers won't be able to submit messages that have a CCIP Read ISM. ### Testing _What kind of testing have these changes undergone?_ - [x] Manual - [x] Unit Tests ### General approach - [x] Get a basic [CCIP Read implementation working](https://github.com/AlexBHarley/permissionless-chainlink-feeds/tree/main/contracts) - [x] Build a [mock service that serves CCIP Read compatible data](https://github.com/AlexBHarley/permissionless-chainlink-feeds/tree/main/apps/api) - [x] Update the Relayer to support CCIP Read ISMs	1 year ago
Yorke Rhodes	f7e453a348	Update pull_request_template.md (#2490) ... Updates PR template to use markdown comments	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	aab8f19f8a	Add codecov github action (#2449) ... ### Description Adds simplest viable codecov setup	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
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	a147bdc620	Fix token CI	1 year ago
Yorke Rhodes	638b3f5474	Unify lint configs	1 year ago
Yorke Rhodes	ebaf652192	Fix builds and tests	1 year ago
Yorke Rhodes	d9cd552c62	Merge CI configs	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
Mattie Conover	efad4e1326	Omniscient relayer infra (#2299) ... ### Description - Adds support for omniscient relayers - Updates config formats to allow better overideability by agent role - Enables deploying selected agents rather than having to deploy them all at once - Merges scraper scripts and configuration ### Drive-by changes Lots of cleanup was made in the infrastructure scripts and source as it was already being touched by the above. While this PR touches a lot of files, many of the changes are just because we have so many scripts and a small change to something they all use instantly can lead to many files changed. ### Related issues - Fixes hyperlane-xyz/issues#438 - Fixes hyperlane-xyz/issues#447 - Fixes #1664 ### Backward compatibility _Are these changes backward compatible?_ No _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ Yes ### Testing _What kind of testing have these changes undergone?_ Manual Unit Tests	2 years ago
Yorke Rhodes	50f04db1fa	Make merkle proofs optional on multisig ISM (#2173) ... ### Description Validators currently sign `(root, index)` checkpoints and during verification, a `message` is passed as calldata, an `id()` is derived, and a `proof` of `id()` at `index` in `root` is verified This provides “all or nothing” censorship resistance guarantees because a validator can only sign roots to allow any contained messages to be processed. We have considered alternatives where validators sign `message` directly and we lose censorship resistance in exchange for eliminating merkle proof verification gas costs. However, if validators sign `(root, index, message)` tuples, we can skip merkle proof verification on the destination chain while still maintaining censorship resistance by providing two valid metadata formats: 1. existing validator signatures and merkle proof verification of inclusion 2. including merkle proof verification for pathway where validators are censoring `message` It’s worth noting the validator is required to index event data to produce this new signature format. However, this does not require historical indexing and new validators being spun up can simply begin indexing from tip. See https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/2187 for validator changes See https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/2248 for relayer and e2e test changes ### Drive-by changes Merkle index also optional ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2192 ### Backward compatibility - new ISM deployment is necessary (we could upgrade implementation in theory) - Validator and relayer upgrades ### Testing Unit (fuzz) Tests, E2E tests	2 years ago
Asa Oines	63562c7211	Refactor agent event indexing (#2246) ... ### Description This PR refactors event indexing in the agents, allowing similar logic to be shared across multiple event types (i.e. messages, deliveries, gas payments) and database types (i.e. the Relayer rocks DB and Scraper SQL DB). Furthermore, it adds new syncing modes by way of `MessageSyncCursors` that take advantage of the monotonically increasing dispatched message nonce to sync more intelligently. ### Drive-by changes - Fixes a bug in the existing cursor that caused the same block range to be indexed three times - Modifies kathy to get rid of the idea of "rounds", just sends messages with a sleep in between - Minor modifications to the e2e test for performance - Expand macros in settings - Add scraper to e2e test ### Opportunities for improvement - We can further reduce RPC usage (or improve latency) by sharing the view of the latest finalized block number between cursors - We can speed up the effective time for (a relayer to start deliving messages | the scraper to scraper recent events) by creating forward/backward cursors for gas payments and deliveries where the backwards cursor terminates at index_settings.from - We can remove the need for index_settings.from by terminating backwards cursors based on the block number that the first message was dispatched at ### Related issues - Fixes #[issue number here] ### 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?_ E2E tests --------- Co-authored-by: Mattie Conover <git@mconover.dev>	2 years ago
Mattie Conover	35bcd97805	Rust release artifacts (#2150) ... ### Description This adds a new pipeline to build binaries for multiple platforms that we can package with releases. Example run: https://github.com/hyperlane-xyz/hyperlane-monorepo/actions/runs/4852298633/jobs/8647117945 ### Drive-by changes No ### Related issues - Fixes #2147 ### 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	2 years ago
Asa Oines	5f72e7fd92	Use node 16 when compiling contract types (#2146) ... ### Description To address https://github.com/NomicFoundation/hardhat/issues/3877 Also reverts #2140	2 years ago
Mattie Conover	b56b022f88	Hyperlane-Core WASM support (#2110) ... ### Description This shuffles some code around and changes dependencies to make `hyperlane-core` WASM compatible and adds a check to the pipeline to ensure it stays that way. To do this it does refactor hyperlane db to the `base` crate, which makes more sense IMO anyway as that is an implementation detail of the agents and not part of the core protocol. ### Drive-by changes ### Related issues - Fixes #1977 ### Backward compatibility _Are these changes backward compatible?_ Yes-ish - It does change where things are but it does not change support. Should only impact people who directly use the libraries. _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 Unit Tests	2 years ago
Asa Oines	2900737c8f	Add HyperlaneIsmFactoryDeployer (#2068) ... ### Description This PR separates ISM deployment from HyperlaneCoreDeployer. Furthermore, it adds support for Routing and Aggregation ISM deployment via a recursive IsmConfig type. The MultisigIsm address is removed from the artifacts. Instead, the default ISM will be fetched at run time and compared against a provided IsmConfig. If there are *any* differences, a new defaultIsm will be deployed. ### Drive-by changes None ### Related issues None ### Backward compatibility _Are these changes backward compatible?_ No _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ Yes, the default LegacyMultisigIsms will no longer be supported by the checker. The governance script will instead deploy a routing ISM and set that as the default ISM. ### Testing _What kind of testing have these changes undergone?_ Unit Tests	2 years ago
Yorke Rhodes	6d40e193b1	Fix contracts test coverage instrumentation (#2089) ... ### Description - Fixes bugs in solidity test coverage ### Drive-by Changes - Removes check for minimum coverage ### Related issues - Touches https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/1841 - Touches https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/1840 ### Testing See `coverage-sol` job or try `yarn coverage` locally for HTML breakdown	2 years ago
Asa Oines	32407592e6	Redeploy Interchain Accounts (#2081) ... ### Description This PR contains the deployment artifacts from a fresh deploy of PI Interchain Account middleware to testnet and mainnet. The deployment hit some strange issues with polygon where it was complaining about underpriced txs. I was able to fix by submitting the failed transactions manually with cast. ### Drive-by changes - Changes the return type of HyperlaneDeployer.readCache, which was accidentally omitted from #2078 - Logs completion of HyperlaneConnectionClient initialization in deployer - Fixes proxy admin fetching in `changeAdmin` - Uses transaction overrides in `upgradeAndInitialize` - Allows for caching of `InterchainAccountRouter` if it has been deployed completely but adminship hasn't been changed - Submit initialization and ownership transfer txs sequentially in HyperlaneRouterDeployer, which hopefully fixes an issue in which logs were not showing up - Return early in governor if no violations ### Related issues - Fixes #2107 ### Backward compatibility _Are these changes backward compatible?_ No, the ICA docs need to be updated _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?_ Checker is passing	2 years ago
Yorke Rhodes	55f40ad760	Merge audit v2 remediation to main (#1727) ... ### Description Merge [`audit-v2`](https://github.com/hyperlane-xyz/hyperlane-monorepo/releases/tag/audit-v2) into `main` See [changelog](034e75b632...audit-v2)	2 years ago
Asa Oines	e403671ce1	Add asaj as codeowner (#60)	2 years ago
Asa Oines	5a6a753de6	Fix fork tests 2 (#2063) ... - Fix an issue where `pick` inserts a key into an object. - Skip fork testing ICAs/IQS due to the IGP mismatch error	2 years ago
Asa Oines	14fb247ea1	Temporarily disable gas ci job in CI (#2061) ... ### Description To get CI passing again	2 years ago
Asa Oines	17b400806e	Add checkers for middlewares (#2030) ... ### Description This PR adds apps and checkers for the ICA and IQS middlewares. ### Drive-by changes - Remove redundant lines from writeJSON - Automatically detect ownables in checkers - Automatically detect proxied contracts in checkers - Deploy ICA and IQS to testnet3 ### 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 --------- Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>	2 years ago
Asa Oines	97d17570cc	Refactor IGP related code out of HyperlaneCore (#1907) ... ### Description A number of changes intended to make the SDK more easily consumed by hyperlane-deploy - Splits the IGP related code out of HyperlaneCore* into HyperlaneIgp* - Moves agent config building from infra to SDK so that it can be accessed by hyperlane-deploy - Modifies CoreConfig to specify a ChainMap<MultisigIsmConfig> (i.e. specify everything that you need to know to deploy to a chain in that chain's CoreConfig) - Removes core.extendWithConnectionClientConfig - Moves common logic into HyperlaneAppGovernor to be shared between HyperlaneCoreGovernor and HyperlaneIgpGovernor - Adds TestRecipient contract addresses to the SDK addresses for consumption by hyperlane-deploy - Allow buildContracts to build when address keys are a superset of factory keys (via filterContracts). This is useful as it allows us to just throw all the addresses at a HyperlaneApp constructor without needing to remove the ones that aren't relevant - Removes InterchainGasCalculator, the logic we want to keep now lives in HyperlaneIgp - Allows chains to be added to a MultiProvider ### Drive-by changes - Merges the infra govern script into the check script (to dedupe) - Some minor renaming where "Core" was being used liberally - Default to using whatever is configured in `owners.ts` in the router configs for infra (for ICA, IQS, HelloWorld, and LL deployment) ### Related issues - Fixes #[issue number here] ### Backward compatibility _Are these changes backward compatible?_ No, existing consumers of the SDK may need to adjust. _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 / Unit Tests	2 years ago
Yorke Rhodes	fee3e253cc	Add first pass at code owners (#1958) ... ### Description Adds CODEOWNERS for more explicit ownership	2 years ago
Yorke Rhodes	5aac31651b	Add CODEOWNERS	2 years ago
Yorke Rhodes	b009989328	Add CODEOWNERS	2 years ago
Yorke Rhodes	5b021c6242	Add fork testing to CI (#1931) ... ### Description - Add fork tests to CI - [x] check - [x] deploy - [x] govern - [x] check (after govern) ### Related issues - Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/1653 ### Backward compatibility Yes ### Testing CI --------- Co-authored-by: nambrot <nambrot@googlemail.com>	2 years ago
Yorke Rhodes	19d9450031	Remove coverage-sol PR comments (#1939) ... ### Description Removes PR comments that do not work on external contributions	2 years ago
Nam Chu Hoai	97c7f52801	Remove GasPaymentEnforcementPolicy::MeetsEstimatedCost (#1910) ... ### Description As discussed offline, to establish the social contract of the relayer accepting the quotes of its associated IGP on the origin chain, this PR removes the GasPaymentEnforcementPolicy that was assessing gas payments at tx submission time via off-chain oracles.	2 years ago
Asa Oines	0ab0ed0331	Pin foundry version in CI (#1901) ... ### Description Pin the foundry version in CI to the nightly from a few days ago. Unfortunately the only releases are nightly. ### Drive-by changes None	2 years ago
Asa Oines	0274c4f5ea	Better sanitization of announced validator locations (#1844)	2 years ago
Yorke Rhodes	dc19aafdb7	Add slither static analysis to CI (#1622) ... * Add slither config * Target solidity dir in slither action * Update slither filter config * Exclude informational slither output	2 years ago
Mattie Conover	d3886ed4aa	Better image tags (#1733) ... * Better image tags * build image * try 2 * try 3 * try 4 * Fix deprecation * Include ref name * Revert "Include ref name" This reverts commit c9c0e7ee14. * Remove nightly tags	2 years ago
Asa Oines	0477ee11ef	Speed up CI (#1683)	2 years ago
Asa Oines	219e06d853	Clean up solidity test coverage (#1668)	2 years ago
Asa Oines	a573a099d0	Always run coverage against base (#1662)	2 years ago
Yorke Rhodes	1748b60f4b	Revert "Only run coverage when base snapshot has changed (#1568)" (#1581) ... This reverts commit 164203559d.	2 years ago
Yorke Rhodes	164203559d	Only run coverage when base snapshot has changed (#1568) ... * Only run coverage when base snapshot has changed	2 years ago
Yorke Rhodes	befc8d4cc8	Add coverage reports (#23) ... * Ensure yarn build exists for mono yarn workspaces * Fix command chaining * Use publish compatible tsconfig * Revert CI changes * Ignore test in eslint * Add coverage reports	2 years ago