EIP-7823: Set upper bounds for MODEXP --- MMU side
#814
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.
Note
Increase MODEXP micro-row totals to 64 and use the EIP-7823 upper byte-size bound in MODEXP_DATA preprocessing, updating TOT/TOTNT handling.
NB_MICRO_ROWS_TOT_MODEXP_ZEROandNB_MICRO_ROWS_TOT_MODEXP_DATAfrom32to64inmmu/osaka/constants.lisp.mmu/osaka/instructions/modexp_data.lisp):EIP_7823_MODEXP_UPPER_BYTE_SIZE_BOUNDinstead of hardcoded512.NB_MICRO_ROWS_TOT_MODEXP_DATAwhen computingTOTNT(replaces hardcoded value) and rename the TOT-setting constraint for clarity.mmu/osaka/instructions/modexp_zero.lisp):TOTNTtied toNB_MICRO_ROWS_TOT_MODEXP_ZERO(no logic change).Written by Cursor Bugbot for commit a754581. This will update automatically on new commits. Configure here.