Eduard S.
Eduard S.
Hi @levs57 ! I think the biggest challenge for this feature is what you mention about an on-chain verifier; and more generally, any kind of verifier that is not rust...
After reviewing the proof chunking milestone progress and checking our priorities, we decided to unschedule this for now and leave it in the backlog. The reason is that we want...
> @ed255 do you know which FFT algo we are using? > > With Cooley–Tukey FFT algorithm, we pad the evaluations to the closest power of 2 before doing iFFTs...
> Look like this might be related to #1330 > Will retest once merged to main So the issue that #1330 was resolving had already been solved via another PR...
Reopening the issue to track the failure of the Super Circuit with aggregation.
The next step to continue debugging this issue is to update the zkevm-chain to use the latest release of halo2_proofs so that it can run with the current main of...
@hero78119 found the exact place where the SimpleFloorPlanner calls the assignment twice: https://github.com/privacy-scaling-explorations/halo2/blob/818febb61da16c76e43469f626e87d01e98db309/halo2_proofs/src/circuit/floor_planner/single_pass.rs#L93-L114
The word lo/hi refactor touches most of the Tables `tables.rs`. I suggest we block this issue until https://github.com/privacy-scaling-explorations/zkevm-circuits/issues/1221 is completed.
We also have the trait `ToWord` with the method `to_word`. If we remove `Word` we can rename the trait and method to `ToU256`, `to_u256`.
This issue has been resolved in the circuits via https://github.com/privacy-scaling-explorations/zkevm-circuits/pull/1030 and https://github.com/privacy-scaling-explorations/zkevm-circuits/pull/1177 but it's still missing in the specs.