Markulf Kohlweiss

There are several issues about gadget design now and I was wondering if we need something like https://blog.zenhub.com/working-with-epics-in-github/ to group them together, or we just emulate it by adding links...

Is this sill open? Could do with a better description. If it refers to this https://github.com/ZK-Garage/plonk/pull/61#discussion_r778763053 what is missing? All the `E::Fr` were renamed to `F`.

Your preferred style might seem more verbose as the traits are otherwise quite similar, but these seem to be different use-cases and it might make sense to treat them seperately....

Can some of this be done by implementing the [Hash](https://doc.rust-lang.org/std/hash/trait.Hash.html) trait for `StandardComposer`?

What are the per-gate separation challenges and what does it mean to remove them? My suspicion is that there is potentially a trade-off between optimal performance and modularity. I.e. while...

What is the PR referred to here, and is this still open? I am confused by the `if modulus.num_bits() >= scalar_repr.num_bits() {` and the same checks once being performed with...

A first step is to define a process for reviewing our code. We should eventually turn this into a wiki page. - test the verification, by writing adversarial code, malicious...

@vkanne-msft this is really more of a meta-issue or epic that should be split into separate tasks. For all code we write there should be some testing and review, especially...

As we are developing an idealization style some relevant issues are discussed on the F\* side, see https://github.com/FStarLang/FStar/issues/674 This was fixed.

The push on the record paper definitely helped our understanding of some modules. Ticked in the above list. Still lots of work to be done, on verification and review.