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

Scrutinize public inputs offset #1028

Open
ledwards2225 opened this issue Jun 7, 2024 · 0 comments
Open

Scrutinize public inputs offset #1028

ledwards2225 opened this issue Jun 7, 2024 · 0 comments

Comments

@ledwards2225
Copy link
Collaborator

Does the public inputs offset leak information? Definitely not if we use a structured trace, but otherwise yes.

Historically the public inputs were placed at the top of the wires. However, for Mega it is convenient to have the goblin ecc op gates at the top of the wires instead, which pushes the PI down by the number of goblin ecc op rows, or equivalently, the length of the transcript contributions from the circuit. We send this public_inputs_offset as part of the proof so that the verifier can compute the public input delta. But this is equivalent to sending the number of goblin ecc op gates. Is that an unacceptable information leak?

When we use a structured trace there is no problem since the number of ecc op gates (and thus the PI offset) is some fixed constant.

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

1 participant