Skip to content
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

ZkProgram proofs when proofsEnabled=false #2067

Open
kadirchan opened this issue Mar 3, 2025 · 4 comments
Open

ZkProgram proofs when proofsEnabled=false #2067

kadirchan opened this issue Mar 3, 2025 · 4 comments

Comments

@kadirchan
Copy link
Contributor

While testing with proofEnabled=false mode when I didn't compile my ZkProgram that I use in contract, it gives

Cannot prove execution of program.createGame(), no prover found.
Try calling `await program.compile()` first, this will cache provers in the background. 
If you compiled your zkProgram with proofs disabled (`proofsEnabled = false`), 
you have to compile it with proofs enabled first.

Then I compiled it and use with proofsEnabled=false everything is fine, but when try to use it after with

await StepProgram.compile({
     proofsEnabled: false
});

it throws with .greaterThanOrEqual is not a function error.

@Trivo25
Copy link
Member

Trivo25 commented Mar 5, 2025

Can you share a minimal reproducible example?

@kadirchan
Copy link
Contributor Author

After compiling it couple more times, compile({proofsEnabled: false}) working as intended. Maybe caching isn't working at the first time but I think that's another issue.

Here is the corresponding test file
Can be reproduced by comment out the line 546

@Trivo25
Copy link
Member

Trivo25 commented Mar 9, 2025

I can't reproduce the issue :/
I did notice some flakiness with Caching as well, we should look into it cc @45930

@45930
Copy link
Contributor

45930 commented Mar 9, 2025

Hey @kadirchan, it would be helpful if you can create a much smaller example that isolates the problem. Assuming that the issue occurs when compiling any zkprogram with proofs disabled, a minimum reproducible example should be a single scripts that compiles a dummy program and generates a proof.

The more you can scope down the exact context in which the bug appears, the easier it is for us to triage it. I'm actually not sure what the incorrect behavior is in this case. Is there more detail in the stack trace containing .greaterThanOrEqual is not a function?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants