fix: hyperchain base address #276
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
vasyl-ivanchuk
changed the title
API E2E Test Results207 tests 207 ✅ 20s ⏱️ Results for commit d5e95d8. ♻️ This comment has been updated with latest results. |
Unit Test Results 4 files 263 suites 11m 34s ⏱️ Results for commit d5e95d8. ♻️ This comment has been updated with latest results. |
|
Visit the preview URL for this PR: |
Romsters
approved these changes
Aug 22, 2024
Signed-off-by: Vasyl Ivanchuk <[email protected]>
Signed-off-by: Vasyl Ivanchuk <[email protected]>
Signed-off-by: Vasyl Ivanchuk <[email protected]>
vasyl-ivanchuk
force-pushed
the
fix-hyperchain-base-address
branch
from
0a8af9a to
d5e95d8
Compare
3 tasks
|
🎉 This PR is included in version 2.49.2 🎉 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 ❔
Adding missing baseTokenAddress to the hyperchain configuration.
Adding a fallback to use the default L2 base token address if it's not specified in the config.
Why ❔
When configuring the block explorer using npm run hyperchain:configure, the resulting configuration was missing the baseTokenAddress value. This absence was causing an error here. As a result of this error, the system was defaulting to Sepolia (which I assume is not the intended behavior for your hyperchain setup).
Checklist