naure
naure
+1 I would even make it the default.
You may consider using this format instead, and hopefully support multiple frontends at once: [https://github.com/QED-it/gadget_standard](https://github.com/QED-it/gadget_standard)
This is indeed broken at the moment. Coming from the official javascript library and lured by the identical method names, you're almost guaranteed to erase the entire database or get...
With multi-phase support, lookups, permutations, and multiset equalities could actually be implemented as chips. These could be extracted out of the prover and verifier code entirely, which would be a...
This benefits all VMs (e.g., zkEVM) because this is used to implement random access memory.
Even if the context is less than 8K and less than 2K, answers look like proper English, but the model seems blind and confused with most of the input once...
Couldn’t instead q_step be constrained by q_usable? if q_usable == 0 then q_step = 0 Then q_usable won’t need to multiply all gates because q_step is already doing it.
(1) Clearly all rows should be constrained. There should not be a concept of _selector_, meaning a flag that disables rules. Instead, there can be case flags, meaning a flag...
I have started something to that effect in PR #863 There certainly are unused queries due to the rectangular shape of the cell manager. This PR focuses on analytics and...
Missing some context, which public key are you referring to?