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
Aztec backend has had a long standing bug in the serialization strategy that has reared it's head in two ways:
An error message from the proof system saying "linear eval != 0"
A proof being computed but then the proof verifies to be false.
The latter point is because when a proof is not satisifiable, the program will not try to compute a proof.
This bug has now been fixed as of noir-lang/acvm-backend-barretenberg@7f42535 and so this issue serves as a tracking issue to close all issues related to the bug. The fix is now contained within #1226 and will be released in 0.5.1
Proposed solution
Add all issues related to this. We should test that they now pass once that PR has been added before closing them.
Alternatives considered
No response
Additional context
No response
Submission Checklist
Once I hit submit, I will assign this issue to the Project Board with the appropriate tags.
The text was updated successfully, but these errors were encountered:
The referenced issues above are the ones that this issue is tracking. Now that we have merged in a fix, it would be great to check that those issues are now fixed
Problem
Aztec backend has had a long standing bug in the serialization strategy that has reared it's head in two ways:
The latter point is because when a proof is not satisifiable, the program will not try to compute a proof.
This bug has now been fixed as of noir-lang/acvm-backend-barretenberg@7f42535 and so this issue serves as a tracking issue to close all issues related to the bug. The fix is now contained within #1226 and will be released in 0.5.1
Proposed solution
Add all issues related to this. We should test that they now pass once that PR has been added before closing them.
Alternatives considered
No response
Additional context
No response
Submission Checklist
The text was updated successfully, but these errors were encountered: