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
I am developing a zero knowledge circuit for auditable private transactions (it is a new concept to make blockchain transactions private while blocking ill intended users).
My circuit compiles perfectly and looks to be correct. However, when testing it I am getting a very weird error when using plonk.fullProve.
It is throwing with Error: Assert Failed and printing a After adding signal 0 of outPubkey message to the console.
After looking through the code, the exception is being thrown when calling setInputSignal on the wasm binary. This can be found in main.cjs in line 485 in snarkjs v 0.7.0.
I had some guesses regarding what the error could be about:
Integers larger than field size
Incorrect number of parameters in input
Ill formatted circuit
I tested all of them exhaustively and was unable to make the error go away.
Does anyone know what this error refers to?
Is there any more proper way to debug errors coming from the wasm file? I currently have no access to informative error messages.
The text was updated successfully, but these errors were encountered:
I am developing a zero knowledge circuit for auditable private transactions (it is a new concept to make blockchain transactions private while blocking ill intended users).
My circuit compiles perfectly and looks to be correct. However, when testing it I am getting a very weird error when using
plonk.fullProve
.It is throwing with
Error: Assert Failed
and printing aAfter adding signal 0 of outPubkey
message to the console.After looking through the code, the exception is being thrown when calling
setInputSignal
on the wasm binary. This can be found in main.cjs in line 485 in snarkjs v 0.7.0.I had some guesses regarding what the error could be about:
I tested all of them exhaustively and was unable to make the error go away.
Does anyone know what this error refers to?
Is there any more proper way to debug errors coming from the wasm file? I currently have no access to informative error messages.
The text was updated successfully, but these errors were encountered: