jolt
jolt copied to clipboard
Unit test parity between `R1CSInputs::clone_to_trace_len_chunks` and `R1CSProof::format_commitments`
As mentioned in #213 we have an implicit relationship in the R1CS between R1CSInputs::clone_to_trace_len_chunks
, R1CSProof::format_commitments
. Would be good to have a smaller test to confirm this relationship. Currently we depend on the integration tests fib_e2e
/ sha3_e2e
to catch these isssues.
I believe we'd want to match this up with the hard coded constants in r1cs.rs
as well.