In PR #205, we get a divergence in the way ipa and kzg works. In particular, the commit function in the commitment_key class for ipa is not used inside any ipa methods, instead we provide the commitment directly to reduce_prove and reduce_verify as a member of the public input. This is not how the kzg interface works.
Also the pairing_check method is absent in the verification_key class for ipa.
We need to resolve if any issue arises when we interchangeably use kzg and ipa for bn254 and grumpkin circuits respectively.
Originally posted by @codygunton in #205 (comment)
In PR #205, we get a divergence in the way
ipaandkzgworks. In particular, thecommitfunction in thecommitment_keyclass foripais not used inside anyipamethods, instead we provide the commitment directly toreduce_proveandreduce_verifyas a member of the public input. This is not how thekzginterface works.Also the
pairing_checkmethod is absent in theverification_keyclass foripa.We need to resolve if any issue arises when we interchangeably use
kzgandipafor bn254 and grumpkin circuits respectively.Originally posted by @codygunton in #205 (comment)