-
Notifications
You must be signed in to change notification settings - Fork 268
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
Mismatch between TS simulator and circuit for kernel value output SLOAD_WRITE_OFFSET #7143
Comments
Bug Investigation - bench_prover.test.ts Preserving working directory /tmp/bb-JvRWBw/tmp-nLDWjV Proof verified! VERIF: 112 0x0000000000000000000000000000000000000000000000000000000000000001 TRACE: 112 0x0000000000000000000000000000000000000000000000000000000000000001 Preserving working directory /tmp/bb-JvRWBw/tmp-Bx0hwU Proof verified! VERIF: 32 0x062eb873a378f1bb056ba1fc6c75ea6e1305477d332a581cd6d708cf779ec839 TRACE: 32 0x062eb873a378f1bb056ba1fc6c75ea6e1305477d332a581cd6d708cf779ec839 Preserving working directory /tmp/bb-JvRWBw/tmp-78ESvR Failing proof: VERIF: 32 0x12ca2328e76ab9996cb6a1a9b93c98e57828093a80c4bf14c7cb0c727cd0e3c7 TRACE: 32 0x12ca2328e76ab9996cb6a1a9b93c98e57828093a80c4bf14c7cb0c727cd0e3c7 Preserving working directory /tmp/bb-JvRWBw/tmp-cBIkhb Proof verified! VERIF: 145 0x0000000000000000000000000000000000000000000000000000000000000001 TRACE: 145 0x0000000000000000000000000000000000000000000000000000000000000001 Preserving working directory /tmp/bb-JvRWBw/tmp-CmpMWw Proof verified! VERIF: 32 0x12ca2328e76ab9996cb6a1a9b93c98e57828093a80c4bf14c7cb0c727cd0e3c7 TRACE: 32 0x12ca2328e76ab9996cb6a1a9b93c98e57828093a80c4bf14c7cb0c727cd0e3c7 Preserving working directory /tmp/bb-JvRWBw/tmp-Ve077U Proof verified! VERIF: 32 0x062eb873a378f1bb056ba1fc6c75ea6e1305477d332a581cd6d708cf779ec839 TRACE: 32 0x062eb873a378f1bb056ba1fc6c75ea6e1305477d332a581cd6d708cf779ec839 Preserving working directory /tmp/bb-JvRWBw/tmp-66uUCu Proof verified! VERIF: 32 0x12ca2328e76ab9996cb6a1a9b93c98e57828093a80c4bf14c7cb0c727cd0e3c7 TRACE: 32 0x12ca2328e76ab9996cb6a1a9b93c98e57828093a80c4bf14c7cb0c727cd0e3c7 Preserving working directory /tmp/bb-JvRWBw/tmp-yN1seO Failing proof: VERIF: 32 0x12ca2328e76ab9996cb6a1a9b93c98e57828093a80c4bf14c7cb0c727cd0e3c7 TRACE: 32 0x12ca2328e76ab9996cb6a1a9b93c98e57828093a80c4bf14c7cb0c727cd0e3c7 Preserving working directory /tmp/bb-JvRWBw/tmp-r9USr1 Failing proof: VERIF: 32 0x12ca2328e76ab9996cb6a1a9b93c98e57828093a80c4bf14c7cb0c727cd0e3c7 TRACE: 32 0x12ca2328e76ab9996cb6a1a9b93c98e57828093a80c4bf14c7cb0c727cd0e3c7 |
Attached all the proof artifacts in an archive. |
This is a follow-up of #7135.
After fixing the above bug pertaining the AVM circuit, a run of the end-to-end test bench_prover.test.ts shows that some AVM proofs are still failing in the verification step.
After some investigation, it was noticed that all the 3 failing proofs have a mismatch between the public inputs fed to the verifier (generated by TS simulator) vs. the public inputs produced in the AVM trace in the proving step.
All the AVM proofs generated in this e2e test were re-ran in a debugger and the full transcript is in comment below.
We observe that the mismatch is always at index 144 which corresponds to START_SLOAD_WRITE_OFFSET.
The simulator (VERIF in logs) has generated some entry at index 144 while the AVM circuit does not generate any.
The text was updated successfully, but these errors were encountered: