Issues with issues

[codygunton]

This is a meta-issue where I am trying to figure out which issues are real, which are not, which are duplicated, what undocumented issues mean, etc. Will put some here for me to try to figure out, and will tag others on those where I don't know what to do.

For the issues for which you're tagged, please elaborate on the description. If duplicated or deprecated, please close with an appropriate description

For me or tbd

• Try to track down what's up with Gate count jumps after finalization #875

[codygunton]

@ledwards2225

• TODO: Link to and/or create appropriate docs for generalized permutations #231 is an oldie which you refer to here:

  barretenberg/cpp/src/barretenberg/stdlib_circuit_builders/circuit_builder_base.hpp

  Line 38 in 2d53ed0

  // DOCTODO(#231): replace with the relevant wiki link.

  I think you mean that there should be a doxygen page?
• Maybe you have recently handled Op-queue aggregation: Prove shift #746?
• I apparently thought this could use a second look before Default value for databus column commitments #1138
• Ensure ECCVM polynomial commitments are never points at infinity #820 you're saying you think this function might have a bug?
• Trace sorting: Make q_arith boolean #915 still a thing in your opinion?
• feat: optimized client IVC fold function aztec-packages#11748 unclear whether this will/should be merged
• fix: add pg adjustments to databus relation aztec-packages#7155 should we call this dead?
• feat: start split aztec-packages#11730 @Thunkar requested we split the WASM and I looked into this a little bit but was not able to finish it before transitioning out. IIRC it started to get messy because of the dsl code being all mixed together. Still very worthwhile though IMO.
• Google Bench memory benchmarks #1132 do we still care about this? I suggest the answer should be Yes

[codygunton]

@Rumata888

• Optimising the number of RAM gates #522 this was a while ago, just asking you to double check this hasn't been handled yet.
• Fix random field/value generation speed #917 would say this is closed by feat: Faster random sampling aztec-packages#9655?

[codygunton]

@maramihali

• Clean boilerplate code in the PG recursive verifier tests #744 I think you just mean there's a lot of boilerplate in here?
• document concatenation trick in Translator #1030 You're looking at this stuff these days so you can assess better than I can whether what we have have is satisfactory (also maybe you can resolve if it's not, idk your scope).
• Update the active_ranges in the DeciderProvingKey construction to avoid the two falling out of sync #1160 Could you elaborate?
• Decrease the number of subrelations? #773 Do you think we should keep this issue around?
• optimise memory usage in perturbator computation #745 seem to recall you picking this up?
• Check if odd and even lagrange polynomials can be merged into 1 by shifting #758 just bringing this to your attention since likely you will have a perspective on this issue given your current task.
• Consider rewriting pippenger so it can be used in IPA verification #1019 I can't find a reference to to this issue or an explanation of it. Could you elaborate in the description to the best of your ability?
• Refine access specifiers of flavor members #989
• Translator Flavor cleanup #907 handled?
• Fix construction of points in Honk verifier contract #1234 Please elaborate
• skipping in Translator relations? #1251 lol

[codygunton]

@lucas

• more extensive poseidon2 native benchmarks, benchmarks for stdlib impl #778
• Sumcheck loop ordering #728 Luke tagged you on this before
• Consider optimizing memory so that it's based on the actual block sizes, etc... #1113 Please elaborate / split into specific issues / clarify? Also I think perhaps the link is not to the right place?
• BarycentricData: share compile time and run time logic #674 You raised a concerning comment here. Did you come to a conclusion? Could you make a separate issue if you think this is something to investigate?
• Merge ultra_recursive_verifier and ultra_verifier #809 good to close?
• try to get google bench working aztec-packages#11455 dead?
• Fix verify_honk_proof input generation #1279 Please add context so that if this goes stale someone will be able to pick it up

[codygunton]

@ludamad

• Make Ultra AllEntities use composition #812 do you think this is still something to look at?
• Use normal composition in flavor classes #788 ditto
• shared_ptr is overused in BB aztec-packages#4885 ditto
• Align objects in native and wasm targets #242
• honk e2e: Client IVC proof construction should retrieve its VKs independently from proving aztec-packages#7370 Could you confirm this is closed by the coming joint PR and close when appropriate?
• Use ASSERT builds #1199 this is handled adequately in CI3 in your opinion right?

[codygunton]

@iakovenkos

• Short scalars in recursive verifier #1134 You I think now the current state of affairs here, mind filling in?
• feat: UH ZK recursive verifier with short scalars aztec-packages#11510 dead?
• is Write VK functionality for tube #1201 resolved by chore: fixed VK in MegaZK/ECCVM/Translator/Tube Recursive Verifier circuits aztec-packages#11377?

[maramihali]

Suggestion: as we cleanup the issues highlighted here, it would be worth to label the ones that are "good first issues"

[ludamad]

Just a warning that good first issues have been swarmed by confusing bot PRs :)

[maramihali]

Ugh, I just wanted to help with stuff to do for potential new joiners 🥲

[ledwards2225]

All questions on issues have been addressed and anything relevant has been individually marked as prio