-
Notifications
You must be signed in to change notification settings - Fork 395
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
Conversation
|
Codecov Report
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
|
FallbackRoutingHook
FallbackRoutingHook
) ### 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
Description
Drive-by changes
Related issues
None
Backward compatibility
Yes
Testing
Fork