EIP-7823: Set upper bounds for MODEXP --- HUB side
#815
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
Introduce explicit in-bounds signals and gate OOB/EXP/MMU and pricing logic on them, while adjusting leading-word and log computations for MODEXP.
bbs-within-bounds/bbs-out-of-bounds,ebs-within-bounds/ebs-out-of-bounds,mbs-within-bounds/mbs-out-of-bounds, and aggregateall-byte-sizes-are-in-bounds.mbsOOB instruction, replace constant1withbbs-within-boundsfor max selection gate.EXPandMMUflags tied toload-lead;OOBflag tied toall-byte-sizes-are-in-bounds; ensureMXP_FLAGandSTP_FLAGare zero.load-lead,cds-cutoff,ebs-cutoff,sub-ebs-32fromcall-OOB-module-for-modexp-lead; computeraw-lead-*undercall-MMU-module-for-modexp-lead.lead-logundercall-EXP-module-for-modexp-lead; updatemodexp-full-logfactor from8to16.all-byte-sizes-are-in-bounds.Written by Cursor Bugbot for commit 2e5118a. This will update automatically on new commits. Configure here.