Circom/snarkjs TODOs

[StefanosChaliasos]

• Currently, we are benchmarking circom/snarkjs, using the time command. This way, the comparison is not equal to libraries as we have the nodejs overhead. However, this will most probably be negligible for large benchmarks.
• Add PLONK and FFLONK support
• Add support for C++ witness generation. In this case, should we also include the time for complying with the cpp code in the logs?
• Cores/Thread: Node uses one single thread in one core. Nevertheless, snarkjs (and the underlying library ffjavascript) use workers to perform operations; hence it isn't actually single-threaded. We could instrument snarkjs so it uses only a single worker. -- We decided yo use best available options
• Add proof size
• Use rapidsnark

[StefanosChaliasos]

We could potentially run circom and snarkjs through a node script directly

[StefanosChaliasos]

#32