-
Related to https://github.com/clearmatics/zecale/pull/89#discussion_r742720040
Despite being mere wrappers around the libzeth functions, some functions in the `prover_server` (Zeth) and `aggregator…
-
Recently, Zeth has been updated to support hashing the instance - which allows to break the linear complexity of the Snark verifier, which is ultimately required to improve the "generic" aspect of Zec…
-
Most of the test files are named `test_.cpp`, nevertheless https://github.com/clearmatics/libsnark/blob/develop/libsnark/gadgetlib1/tests/gadgetlib1_test.cpp is named `_test.cpp` which contrasts with …
-
We currently have:
- `member_variable` in most old code
- `member_variable_` in a few bits of old code
- `_member_variable` used in most new code
Determine a policy (e.g. `_member_variable` for …
-
As mentioned in https://github.com/clearmatics/zecale/pull/19#discussion_r460721638 let's be consistent with how nested gadgets are instantiated.
-
In general, application protocols such as Zeth will want to prevent:
1) tx malleability by observers (msg.sender + ETH signature, ciphertexts)
2) front-running (msg.sender)
3) malleability by the s…
-
Nothing prevents the nested and wrapping SNARKs to be different (see: https://github.com/clearmatics/zecale/pull/16#discussion_r462962318). Let's make the configuration generic to support that.
-
This issue is not directly related to Zeth, but rather concerns:
- Zecale
- Libsnark/ff
- Zeth
These projects use cmake and hold rather similar versions of files in the `cmake` directory. While …
-
Currently, and across most our projects , we have lots of redundancy in our file names. In may cases, we have things like:
`gadgetlib1//pairing/mnt/mnt_pairing_params.hpp`. The `mnt` emphasized here:…
-