clearmatics / zeth-specifications Goto Github PK

We need to document the support for BLS12-377 and its implications:

• different paddings
• different nb of words to represent the objects on the EVM
• different parameters for MiMC
• etc.

In the Zeth code base (on the develop branch), elements of the verification key are negated to save point negation on the contracts. It is worth documenting such changes in the specs, maybe somewhere in the "implementation" section.

It would be ideal to add the latex compilation to the CI on this repository in order to make sure pushed latex code compiles correctly. This github action workflow: https://github.com/xu-cheng/latex-action seems to be doing exactly that. Consider using it for the CI of this repository.

See if/how this paper: https://eprint.iacr.org/2021/089 is relevant to Zeth and how this could be used to modify the Zeth Recipient algorithm. This looks very interesting in the context of computationally restricted (receiver) devices (that may not support the "download all Zeth Mix events and decrypt all" approach).