-
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
Negative block number queried when forked network block number is near zero #4131
Negative block number queried when forked network block number is near zero #4131
Conversation
…o bug/1568-negative-block-number-queried-when-forked-network-block-number-is-near-zero
🦋 Changeset detectedLatest commit: 092b771 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 ↗︎
|
@ChristopherDedominici can you add a changeset? |
latestBlock: bigint, | ||
maxReorg: bigint | ||
): bigint { | ||
// Design choice: if latestBlock - maxReorg gives a negative number than the newest block will be used |
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.
Let's explain that we do this because the forked network is almost surely a devnet
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.
Done
The code line:
const lastSafeBlock = latestBlock - maxReorg;
could result in a negative value when maxReorg > latestBlock.Fix: add check, when the difference is a negative number then use latestBlock.