Verification vectors are over-allocated #126
Comments
hansieodendaal
pushed a commit
that referenced
this issue
Mar 27, 2024
Batch verification vectors are allocated in part using the expected aggregation factor of each statement in the batch. However, this was being done using the aggregation factors corresponding to each statement's associated generators, which may exceed the aggregation factors actually used in the statements. The result was a possible over-allocation of these vectors. This PR changes the allocation to use the actual aggregation factors. Closes #126.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The dynamic scalar and point vectors used in batch verification are allocated in part based on the aggregation factor associated to each statement's parameters. This aggregation factor does not specify the number of commitments associated to the statement, but rather the maximum number of supported commitments, as specified by the number of associated generators.
As a result, it's possible for a statement to specify a larger aggregation factor than is actually used; this allows for more flexibility and efficiency when producing generators. The result is that the verification vectors may be over-allocated.
The fix is to use the number of commitments associated to a statement instead of the specified aggregation factor.
The text was updated successfully, but these errors were encountered: