You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
halo2_proofs: Fix oversized initialization of commitment_data.evals
If `commitment_data.point_indices` contains duplicate indices, then
`point_index_set` will be shorter. The old code initialized
`commitment_data.evals` to be the same size as `point_indices`, which
then left entries near the end without evaluations.
Before the bugfix to reject two queries with the same point and
commitment but different evaluations, this would have resulted in
`commitment_data.evals` being returned with invalid "default" entries at
the end. Fortunately this was not an observable bug as the code using
`commitment_data.evals` does not index it using
`commitment_data.point_indices`.
After the bugfix (which changed the default `commitment_data.evals`
entries to `None` internally), this would have resulted in a panic at
the end of `construct_intermediate_sets` (which expects all evaluations
to be provided).
We now directly initialize `commitment_data.evals` to the correct
length.
0 commit comments