PANews reported on October 18 that Ethereum co-founder Vitalik tweeted that he hopes more ZK and FHE developers can give their overhead in the form of a ratio (the time to calculate encryption to the time to calculate the original data) instead of just saying "we can perform N operations per second." “This is more hardware-independent and gives a very indicative number: how much efficiency will I lose if my application adopts a cryptographic approach instead of a trust-reliant approach? This is also usually easier to estimate because as a developer I ‘already know’ how long my computation will take, so I can just multiply by that number. (I know this is difficult because the operations required for execution and proof are heterogeneous, especially in terms of SIMD/parallelization and memory access patterns, and the ratio is also somewhat hardware-dependent, but even so, the overhead factor is still a good number)”PANews reported on October 18 that Ethereum co-founder Vitalik tweeted that he hopes more ZK and FHE developers can give their overhead in the form of a ratio (the time to calculate encryption to the time to calculate the original data) instead of just saying "we can perform N operations per second." “This is more hardware-independent and gives a very indicative number: how much efficiency will I lose if my application adopts a cryptographic approach instead of a trust-reliant approach? This is also usually easier to estimate because as a developer I ‘already know’ how long my computation will take, so I can just multiply by that number. (I know this is difficult because the operations required for execution and proof are heterogeneous, especially in terms of SIMD/parallelization and memory access patterns, and the ratio is also somewhat hardware-dependent, but even so, the overhead factor is still a good number)”