-
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Gnark currently doesn't have a clean wa…
-
-
Same IR as https://github.com/llvm/llvm-project/issues/103841 but applied to Aarch64 as an alternative to https://github.com/llvm/llvm-project/issues/103717
Unlike x86 there is always an extra inst…
-
Reading LegoSNARK:
**Additional properties to add to the LC paper** intro/related work for a more in-depth description regarding CP-SNARKs (commit-and-prove SNARKs) and cc-SNARKs (commit-carrying SN…
-
Maybe a silly question, I’ve just started learning about zk-SNARKs and noticed something in your hook implementation.
Isn't it problematic to require a commitment in the withdrawal function? This c…
-
In the existing rate-limiting functionality, keep a check on the number of snarks per statement from a peer. This would mitigate an attack where attackers could lower the fee and make honest nodes ver…
-
This is a memory use optimisation also implemented in OCaml nodes: https://github.com/MinaProtocol/mina/blob/develop/rfcs/0063-reducing-daemon-memory-usage.md.
The idea is that a node needs to keep…
-
See: https://github.com/clearmatics/libsnark/issues/35
An example in Zeth is: `libzeth/snarks/groth16/groth16_api_handler.hpp` that can be changed to `libzeth/snarks/groth16/api_handler.hpp` etc.
-
## Background
- **random oracle**: black-box that to every query gives a random response (uniform from its domain), same query == same response. (Note: church-turing thesis said computable functions …
-
The implementations of the batched SNARKs are should be equivalent to the non-batched versions. We can replace the direct implementation with the batched one using a number of instance = 1.
- [x] *…