cmd/utils: use maximum uint64 value for receipt chain insertion #32934
Conversation
This file contains hidden or 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
## Summary: Replace incorrect expression 2^64-1 (bitwise XOR, evaluates to 65) with the intended uint64 maximum. This was a logic bug that passes the wrong limit into InsertReceiptChain during Era import. ## Why: In Go ^ is bitwise XOR, not exponentiation. 2^64-1 does not produce max uint64 and causes incorrect behavior during import. Not an immediate remote-exec security vulnerability, but a correctness bug that can cause data/consensus problems when importing history. ## Fix: Use idiomatic ^uint64(0) to represent max uint64 without adding imports. ## Files changed: - cmd/utils/cmd.go
Contributor
Author
|
Fix 32935 |
jwasinger
reviewed
Oct 17, 2025
cmd/utils/cmd.go
Outdated
| } | ||
| encReceipts := types.EncodeBlockReceiptLists([]types.Receipts{receipts}) | ||
| if _, err := chain.InsertReceiptChain([]*types.Block{block}, encReceipts, 2^64-1); err != nil { | ||
| if _, err := chain.InsertReceiptChain([]*types.Block{block}, encReceipts, ^uint64(0)); err != nil { |
Contributor
There was a problem hiding this comment.
use math.MaxUint64 here.
Contributor
Author
There was a problem hiding this comment.
Ok, use math.MaxUint64 to improve readability.
rjl493456442
changed the title
rjl493456442
approved these changes
Oct 18, 2025
rjl493456442
pushed a commit
to rjl493456442/go-ethereum
that referenced
this pull request
Oct 28, 2025
This was referenced Nov 3, 2025
atkinsonholly
pushed a commit
to atkinsonholly/ephemery-geth
that referenced
this pull request
Nov 24, 2025
prestoalvarez
pushed a commit
to prestoalvarez/go-ethereum
that referenced
this pull request
Nov 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Summary:
Replace incorrect expression 2^64-1 (bitwise XOR, evaluates to 65) with the intended uint64 maximum. This was a logic bug that passes the wrong limit into InsertReceiptChain during Era import.
Why:
In Go ^ is bitwise XOR, not exponentiation. 2^64-1 does not produce max uint64 and causes incorrect behavior during import. Not an immediate remote-exec security vulnerability, but a correctness bug that can cause data/consensus problems when importing history.
Fix:
Use idiomatic ^uint64(0) to represent max uint64 without adding imports.
Files changed: