-
Notifications
You must be signed in to change notification settings - Fork 136
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
Unable to verify a Cairo 1 proof #802
Comments
This must has been a change in the Cairo VM. I'll raise the issue to the VM team, and we'll pin the version here to use until it gets fixed. |
I have updated the docs here, until we get it fixed: |
Can you try with ?
There seems to be an issue of the VM not activating the output builtin correctly without small |
@MauroToscano Setting Thank you for your help! |
While working on cairo-hints, we’ve noticed that the latest lambdaworks prover for Cairo 1 is unable to verify a proof it successfully generated from
cairo1-run
’s trace and memory files (cairo1-run
is part ofcairo-vm
).Steps to reproduce
Sample program
I am using this example circuit:
Trace and memory files
Inside cairo-vm's cairo1-run script:
When I create the memory and trace files using the latest
cairo1-run
incairo-vm 1f98feff566dd2da016e439f5e8db912c6e39872
, the proof generated fails verification after the 2nd step. In this version ofcairo1-run
I tried generating memory and trace files with and without the flag--proof_mode
.This seems to be a recent regression. When I create the memory and trace files with
cairo1-run
incairo-vm v0.9.1
andcairo-vm v0.9.2
, the proof generated byprovers/cairo
is verified successfully.Proving and verification
I ran these commands in
lambdaworks/provers/cairo
(#212c040c5fa21fcb5095a0b1ac92501292517db0
)Additional context
I noticed that the latest version of
cairo-vm
updatedcairo-lang
dependencies fromv2.3.1
tov2.5.3
- maybe it is related?Is lambdaworks prover and verifier expected to work with
cairo-lang v2.5.3
? Either way, it probably shouldn’t generate proofs that cannot be verified later.The text was updated successfully, but these errors were encountered: