fix: base l1 contract addresses #571
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
✅ Deploy Preview for storybook-component-library canceled.
|
tremarkley
previously approved these changes
Nov 14, 2024
tremarkley
approved these changes
Nov 14, 2024
There was a problem hiding this comment.
the sdk will be officially deprecated in Q1 2025. See the docs on how to migrate away from it here: https://docs.optimism.io/builders/notices/sdk-deprecation
|
@TheArhaam before we merge this in could you add a changeset on the PR? you can run |
…rhaam/op-ecosystem into fix/base-contract-addresses
|
Hey @nitaliano, added the changeset, let me know if that's okay and if anything else is required. Thanks! |
nitaliano
approved these changes
Nov 18, 2024
|
yup all good thanks for the PR @TheArhaam |
Merged
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.
Description
This PR updates the Base L1 contract addresses which was causing errors while fetching message status from the CrossChainMessenger. The official base contract addresses can be found here