Ivo Kubjas

Just as a remark - I also encountered the same bug very recently. I checked very briefly and seems that this bug is propagated from gnark-crypto, but have to debug...

> I'm not particularly interested in PLONK+FRI, it's just that the tester by default will iterate through the various backends and will fail (because of PLONK+FRI), meaning that I have...

We have omitted PLONK+FRI backend by default: #1075

Fixed with https://github.com/Consensys/gnark/security/advisories/GHSA-498w-5j49-vqjg

Indeed we don't https://github.com/Consensys/gnark/discussions/991 for a bit more information on why we haven't done it yet. We don't currently have it on the roadmap either, but definitely would be a...

Yes, there are some cases where this happens. See also #242 and #243. We could try adding some specialised methods into API, but it is kind of suboptimal. Better option...

Like this: ```go ccs, err := frontend.Compile(ecc.BN254.ScalarField(), r1cs.NewBuilder, &circuit{}) if err != nil { panic(err) } ccst, ok := ccs.(constraint.R1CS) if !ok { panic("not R1CS") } constraints, resolver := ccst.GetConstraints()...

Thanks for the contribution! I also code generated the implementation for all curves. I'll merge to a branch which collects all documentation fixes which we merge before next release.

> [](https://cla-assistant.io/Consensys/gnark-crypto?pullRequest=546) Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our [Contributor License Agreement](https://cla-assistant.io/Consensys/gnark-crypto?pullRequest=546) before we can...

Good idea. We have for now postponed implementing such methods as in general the arithmetic in circuits are done on field elements and doing bit operations is quite expensive (as...