Fix Verifier Key deserialization. #1
Closed
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.
Description
The desiarlization of a VK involves recovering the circuit log size parameter
k. This value is read directly as au32without any checks. Its maximum allowed value is then~2^( 2^32), which can become an issue since it is used later in the desiarliazation to process the selector by initializing vectors of size2^k:https://github.com/input-output-hk/halo2/blob/b61d14bc15fd8692415f3dbbaa737a088ea57400/halo2_proofs/src/plonk.rs#L125C36-L125C36
There is a theoretic limitation of this value by the 2-adicity of the scalar field of the curves we use. All of the curves have a 2-adicity
<=32.Changes
Add a check that ensures
k <=32.