pinkiebell

Also ~works with `slither --ignore-compile`, but you have run the compile task first. However, it only analyses 1 contract? ``` INFO:Slither:. analyzed (1 contracts with 72 detectors), 2 result(s) found...

Question is do wan't something like a debugging options-object for these calls or just expand the previous optional arguments?

ref: https://github.com/privacy-scaling-explorations/zkevm-circuits/pull/1253#issuecomment-1447785851 cc/ @CPerezz

> I have a PR for this here: [halo2-ce#13](https://github.com/halo2-ce/halo2/pull/13) > You can cherry-pick the last 2 commits and test it out. I've tested that and while it makes the synthesize...

It would be a great performance improvement for real & mock prover alike to improve halo2 to not calling these closures from `assign_region` etc. twice. Because changing all the circuits...

Given that the PoW era is gone and PoA consensus doesn't have block rewards, should we even consider supporting that?

Just stumbled into this one :) . Related to this is a feature I recently added to estimate K based on worst-case blocks. It doesn't show the real picture because...

@CPerezz Will do 👍

@AronisAt79 I just tested this and aborting a long running sync task isn't possible to do *cleanly* . Another solution is that we spawn a new process instead and piping...

If we really need this someday we can spawn dedicated prover processes from within the prover daemon. Given this has some real drawbacks mentioned above, I put it in the...