Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connect subtable commitments between main protocol and merge #1270

Open
ledwards2225 opened this issue Feb 25, 2025 · 1 comment
Open

Connect subtable commitments between main protocol and merge #1270

ledwards2225 opened this issue Feb 25, 2025 · 1 comment

Comments

@ledwards2225
Copy link
Collaborator

The ultra ecc op subtable columns t_j, j = 1,2,3,4 are committed to by the PG prover in CIVC (Mega). These commitments (received by the PG recursive verifier) must be connected to those used in the merge recursive verifier at the same step. The easiest way to do this is just to store the commitments from the PG verifier to be reused in the merge.

@ledwards2225
Copy link
Collaborator Author

Another thing that comes to mind: Let k_j be the length of t_j. We likely need to establish a connection between k_j implicitly encoded in the selector lagrange_ecc_op and the k_j used in the merge. Otherwise I don't think there's anything stopping the prover from merging t_j with T_{j,prev} in an overlapping way. The way to do this might be to bake k_j into the VK and use it both locations. (Can the verifier efficiently evaluate lagrange_ecc_op from knowledge of k_j?)

@codygunton codygunton added prio Suggested to prioritized and removed prio Suggested to prioritized labels Mar 6, 2025
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

No branches or pull requests

2 participants