fix: update multicall with .env.bridge file #23
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR updates the scripts under
l2-bridge
to fix an issue:we removed
NEXT_PUBLIC_L1_MULTICALL3_ADDRESS
from the.env
file, so:l2-bridge-deploy-l1-multicall.sh
: for the multicall was deployed case, it should update.env.bridge
;l2-bridge-set-env.sh
: remove replacement line forNEXT_PUBLIC_L1_MULTICALL3_ADDRESS
Updates: Also, it will add two env vars for bridge ui.
Test Plan
To change the
L1_RPC_URL
with the Sepolia, run:it should update
NEXT_PUBLIC_L1_MULTICALL3_ADDRESS
in.env.bridge
with the value0xcA11bde05977b3631167028862bE2a173976CA11