Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat:update deployments to use FallbackRoutingHook #3179

Merged
merged 4 commits into from
Jan 29, 2024

Conversation

aroralanuk
Copy link
Contributor

@aroralanuk aroralanuk commented Jan 24, 2024

Description

  • mainnet3, testnet4 should be using fallback routing hooks because it's more "porous" for first-time deployers of hyperlane to have merkleTreeHook out of the box

Drive-by changes

  • added overrides to configureHook in basedeployer and setHook in hookdeployer
  • added fetching local rpc first logic in infra/chains and then secrets rpc if needed. This would mean the forking and live setup will be closer as the rpc urls will be the same between the two.

Related issues

None

Backward compatibility

Yes

Testing

Fork

Copy link

changeset-bot bot commented Jan 24, 2024

⚠️ No Changeset found

Latest commit: 2e0c51e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

codecov bot commented Jan 24, 2024

Codecov Report

Merging #3179 (2e0c51e) into main (3bb4d87) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3179   +/-   ##
=======================================
  Coverage   67.65%   67.65%           
=======================================
  Files          99       99           
  Lines        1014     1014           
  Branches      106      106           
=======================================
  Hits          686      686           
  Misses        284      284           
  Partials       44       44           
Components Coverage Δ
core 50.00% <ø> (ø)
hooks 68.79% <ø> (ø)
isms 65.94% <ø> (ø)
token 58.41% <ø> (ø)
middlewares 81.46% <ø> (ø)

@aroralanuk aroralanuk changed the title [WIP]feat:update deployments to use FallbackRoutingHook feat:update deployments to use FallbackRoutingHook Jan 24, 2024
@aroralanuk aroralanuk merged commit ff77135 into main Jan 29, 2024
27 of 28 checks passed
@aroralanuk aroralanuk deleted the kunal/config-fallback-hook branch January 29, 2024 18:39
ltyu pushed a commit to ltyu/hyperlane-monorepo that referenced this pull request Mar 13, 2024
)

### Description

- mainnet3, testnet4 should be using fallback routing hooks because it's
more "porous" for first-time deployers of hyperlane to have
merkleTreeHook out of the box

### Drive-by changes

- added overrides to configureHook in basedeployer and setHook in
hookdeployer
- added fetching local rpc first logic in infra/chains and then secrets
rpc if needed. This would mean the forking and live setup will be closer
as the rpc urls will be the same between the two.

### Related issues

None

### Backward compatibility

Yes

### Testing

Fork
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants