-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Use remote chain id in fork metadata #5114
Conversation
🦋 Changeset detectedLatest commit: 3d7f13e The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
let fixture = ProviderTestFixture::new_forked(None)?; | ||
|
||
let fork_metadata = fixture.provider_data.fork_metadata().unwrap(); | ||
assert_eq!(fork_metadata.chain_id, 1); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it ok to assume that we are forking mainnet here? I think it is, but would like to get confirmation.
If it's not ok, is there an example of a test where we are doing this "correctly"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We assume this everywhere else in the code, so I think it's fine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing a changelog
Closes NomicFoundation/edr#366