pinkiebell

Some preliminary data, this was tested on a amd epyc machine (AWS r6a.48xlarge). I still have to figure out all the available performance event counters - most of them are...

Just a heads up, most of the low hanging improvements are now due to RLC in the zkevm-circuits configuration/synth step. After looking at profiling intervals it looks like that is...

At the moment, it's using the `evm-verifier-with-accumulator` example and only aggregates a single proof. Does it make sense to test a different setup where it aggregates all zkevm sub-circuits instead...

> So it seems that current `zkevm-chain` only implements the aggregation part, and the public input part passing is still WIP, and it kind of depends on [privacy-scaling-explorations/zkevm-chain#79](https://github.com/privacy-scaling-explorations/zkevm-chain/issues/79), right @pinkiebell?...

@ChengYueJia There seems to be a bus-mapping implementation but it's still named dummy. cc/ @z2trillion @lispc regarding status on this one. [1](https://github.com/privacy-scaling-explorations/zkevm-circuits/blob/main/bus-mapping/src/evm/opcodes.rs#L240) On the other hand these opcodes are not...

Looks like `EXTCODESIZE` has a wrong reference 😅

@ed255 I created this PR even if this conflicts with #730 just for tracking purposes. If the circuit optimizations gets merged, then I can reflect these changes for the evm...

@ed255 Now that zkevm-chain uses the latest Pi circuit, I rebased this pr and only added `rand_rpi` to the mix.

@HarryR A public verifiable supply chain. With information or conditions which must be me private to the public but verifiable to the public and the on-chain contract. If you get...