barretenberg
barretenberg copied to clipboard
AztecProtocol
Some affine element tests are defined just for one curve. Absolutely no reason for that
Affine and group elements in barretenberg have a special point at infinity member which can't just be encoded as fields, which is what we currently do with msgpack. Changing it...
It seems this flavor defines non-canonical getters? Also there are hard-coded indices eg in the prover.
Translator Composer uses a random challenge that is derived from Fiat-Shamir, while circuit builder fuzzer uses a configurable challenge. We need to reconcile the two, so they are the same...
As in the case of https://github.com/AztecProtocol/aztec-packages/pull/5174, we sometimes encounter issues relating to our inability to handle scalar multiplication of EC points in the case where the scalar is 0. I...
ClientIVC API does not properly encapsulate complexity. Rework for legibility, and make something robust that encompasses the Goblin-only ClientIVC and the RollupIVC
At least two major workstreams will affect this (execution trace sorting; biggroup handling of point at infinity), but after these are done we should be sure that it's straightforward to...