Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@Schaeff
Copy link
Owner

@Schaeff Schaeff commented Feb 22, 2022

No description provided.

daira and others added 21 commits February 3, 2022 22:06
* use biimplication in the correctness argument to ensure both soundness and completeness;
* avoid introducing lambda at all; it's unnecessary and omitting it shortens the explanation.

Co-authored-by: Jack Grigg <[email protected]>
Signed-off-by: Daira Hopwood <[email protected]>
This changes variable names in the multiopen and commitment opening implementations
and the book's protocol description to keep names and indicies consistent with one
another.

Co-Authored-By: Jack Grigg <[email protected]>
Add hardcoded proof to plonk_api test
halo2_proofs: rename variables for consistency
The verifier's check in the inner product argument used to assume that the
G'_0 value had an additional (trivial) blinding factor term, which makes
it slightly easier to reason that it never is the point at infinity.
However, we never sample challenges that are zeroes (both for security
and completeness reasons) so this element would never be the point at
infinity anyway. Thus, we can simplify the check with the added benefit of
matching the book's description of the protocol.
halo2_proofs: change IPA check equation to match the book
Improve the explanation of incomplete addition
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants