You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug report says that in ResultCommitmentVerifier, the verification of currentTallyCommitment is skipped when processing the first batch. Pull 277 also mentioned this bug.
So my question is: how to exploit this bug to forge a proof. Here are my failed attempts:
According to the bug report, 4bc21did not fix the bug, while 4892a did, which is why I chose these two versions of the files for comparison.
My goal is to find an input.json that causes script 4892a to fail (after the bug fix) and allows scrip 4bc21 to succeed (before the bug fix).
My input.json is as follows, but no matter how I change the input values, both scripts execute successfully. Therefore, I am unable to forge an input.json based on this bug, and I am seeking your help.
Bug report says that in ResultCommitmentVerifier, the verification of currentTallyCommitment is skipped when processing the first batch. Pull 277 also mentioned this bug.
So my question is: how to exploit this bug to forge a proof. Here are my failed attempts:
According to the bug report, 4bc21did not fix the bug, while 4892a did, which is why I chose these two versions of the files for comparison.
My test script are 4892a and 4bc21
My goal is to find an input.json that causes script 4892a to fail (after the bug fix) and allows scrip 4bc21 to succeed (before the bug fix).
My input.json is as follows, but no matter how I change the input values, both scripts execute successfully. Therefore, I am unable to forge an input.json based on this bug, and I am seeking your help.
input.json
The text was updated successfully, but these errors were encountered: