fix: default hyperchain base address #284
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Vasyl Ivanchuk <[email protected]>
API E2E Test Results207 tests 207 ✅ 19s ⏱️ Results for commit 143b09f. |
Unit Test Results 4 files 263 suites 11m 40s ⏱️ Results for commit 143b09f. |
|
Visit the preview URL for this PR: |
Romsters
approved these changes
Aug 27, 2024
3 tasks
|
🎉 This PR is included in version 2.49.3 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What ❔
Fixing default base token address value in hyperchain setup script.
Why ❔
Base token address on L2 is always "800A". This script might not work for hyperchains with custom L1 base token.
Checklist