fix: Always use maxUint256 instead of 2n ** 256n - 1n #2692
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.
Overview
This PR improves the readability of code that uses
2n ** 256n - 1n
. It also fixes a crash in JavaScript caused by using these big numbers directly insideif
statements.Summary
PR-Codex overview
This PR replaces hard-coded values with a
maxUint256
constant for fee calculations.Detailed summary
maxUint256
constant in fee calculations across multiple files.