Skip to content

Divergence between kzg and ipa interface #236

@arijitdutta67

Description

@arijitdutta67

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)

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions