Ivo Kubjas

Suggested edit: ```diff diff --git a/internal/backend/circuits/iszero.go b/internal/backend/circuits/iszero.go index 91f0d4fc..d38d157b 100644 --- a/internal/backend/circuits/iszero.go +++ b/internal/backend/circuits/iszero.go @@ -13,8 +13,12 @@ func (circuit *isZero) Define(api frontend.API) error { a := api.IsZero(circuit.X) b :=...

> @ivokub can you merge in another temporary branch and add your edit to close this issue? The incoming branch is external and couldn't add commits. Created new PR #367....

Yup, removing fuzz testing in `ProverSucceeded` and then fuzzing separately in integration tests makes sense. On a similar note -- maybe also remove marshalling tests from `ProverSucceeded` and move them...

(converted to draft until figuring what direction to take)

@gbotrel, do you have suggestion what to do with this PR? Someone stumbled against a similar problem why this PR was created (#336).

Hi @ZhAnGeek - can you give a full compilable circuit which causes the error? Particularly, what is the implementation of the function `f` you are using?

There is also a bit newer issue #243, which considers when two constraints can be merged in plonk (for example, can merge addition and multiplication). It seems that this issue...

These papers are using either gnark or gnark-crypto: * https://eprint.iacr.org/2021/100.pdf * https://eprint.iacr.org/2021/1443.pdf * https://eprint.iacr.org/2021/1359.pdf * https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=9300214 * - [x] add a bibtex citation reference to gnark so that we could...

> That is; **compiling** the same circuit in parallel is an issue, but I think mostly for internal testing. In a normal workflow, I don't see why a circuit developer...

Hi @zilin-zhou, have you updated the dependencies? More specifically, when using gnark v0.7.0, then you should be using gnark-crypto v0.7.0 as a dependency. Can you show the lines in `go.mod`...