-
Notifications
You must be signed in to change notification settings - Fork 49
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
How can I verify a proof which may have more than 2 steps inside its query_round_proofs #3
Comments
Did you use standard_recursion_config in Plonky2 circuit? It should use only 2 steps. |
Hi Saideng, Thank you for the response. Unfortunately, I did use the standard recursion config. To avoid anything being messed up with my code change, I did a quick test with the plonky2-sha256 sample. I added one line for logging. It turns out the length of steps is 4. Here is code snippet.
Here is the console log.
|
I suggest you recursively prove it in a new proof. like this one: https://github.com/polymerdao/plonky2-ed25519/blob/main/src/main.rs#L71 |
It works as expected, thank you |
After I replaced e2e testing
|
Do you have any public inputs in your proof? |
I don't think so |
Here is the full sample code
|
Currently the circuits require some public inputs. Try to add some public inputs in your code. builder.register_public_inputs() |
Thanks a lot. I missed some information inside the recursive proving logic. Right now, it works fine. One more thing to confirm is whether I can use some lower ptau to generate circuit's corresponding zkey. |
I haven't done this step. I think it needs 2**25 powers. |
Exactly, 2**25 is the minimum requirement for this circuit |
After running the e2e test successfully, I try to verify plonky2-sha256 proof through Circom way. Then, I add the following code to the plonky2-sha256 project. It compiles successfully and faces fatal error since the steps of query round proof is more than 2.
Is there a way to reduce the proof's query round step to pass this assertion?
Fatal error position
plonky2-circom/src/verifier.rs
Line 192 in ae53283
The text was updated successfully, but these errors were encountered: