a16z/jolt

Potential Bug: timestamp_range_check commitments length does not match openings length

Closed this issue · 1 comments

sragss commented

For fib_e2e (and presumably elsewhere), timestamp_range_check passes 35 openings and 38 commitments to Hyrax.

Relevant snippet here.

sragss commented

After fixing lets add an assert to the batched hyrax opening proof to avoid in the future.