-
Notifications
You must be signed in to change notification settings - Fork 116
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
circuit compilation fail by some errors #1088
Comments
the wasm code compiled from kimchi is definitely not using 64-bit memory, so I wouldn't expect the flag |
We team are on a L2Rollup product, the circuits' dependency relationship: I could compile What we could do currently is to reduce the merkle-tree height to a really small value, to decrease memory( addressing spaces) occupy to make all circuits compiled and run. But this limit our product really much. Although our machine memory is 128GB, but due to the wasm code compiled from kimchi is using 32-bit memory, much of machine memory left could not be made usage of for circuits. Besides, any practices/suggestions for the cases like ours? |
Besides, how about the progress about 'Expose side loaded verification key to snarkyjs' at #673 ?? It would help much!! |
Unfortunately we haven't planned to do this in the next 2-4 weeks |
Background:
My Machine: 36c, 128GB.
My two circuits' size are not small. When I compile them (with
node --experimental-wasm-memory64
), got the errors respectively as blow:TypeError:The encoded data was not valid for encoding utf-8
Errors: curve point must not be the point at infinity
These error seems NOT from that the circuit size exceeds the upper limit (though, might be close).
Later, I tried to simplify the circuit by reducing some constraints or operations, like lower merkle-tree heights, rid some constraints, etc. Then they could smoothly be compiled.
My question: if my circuit size does not exceed, why I compiled them with
wasm-memory64
, but still got these errors?Furthermore, does snarkyJS support wasm64 currently??
The text was updated successfully, but these errors were encountered: