feat: remove legacy type proofs #1316
Merged
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.
This removes the use of legacy type proofs which we implemented using an inefficient horizontal byte decomposition.
Note
Removes the legacy horizontal byte-decomposition type proofs and the “limitless” flag, always using recursive bitwidth proofs with a default max range constraint of 16, and updates sorting/lowering and tests accordingly.
limitlessmode and horizontal byte-decomposition path; always use recursive proof for widths >maxRangeConstraint; set defaultmaxRangeConstraintto16; minor panic message tweak.WithLimitless; ensure selector-bit binarity usesWithMaxRangeConstraint.LimitlessTypeProofsfromOptimisationConfigand usages; defaults updated (MaxRangeConstraint: 16).WithLimitless.asm/bench/shfandasm/bench/stptoCheckWithFields(..., field.BLS12_377).Written by Cursor Bugbot for commit f853bcb. This will update automatically on new commits. Configure here.