According to online reports, Vitalik posted on the X platform,"I hope that more developers who do ZK (zero-knowledge proof) and FHE (fully homomorphic encryption) can express performance in terms of ratios (such as" encryption calculation time/raw calculation time "), rather than just saying," We can do N operations per second." This approach is less hardware-dependent and provides a very useful indicator: How much efficiency do I sacrifice when I change my application from "relying on trust" to "relying on cryptography"? It is also usually more suitable for performance estimation, because as a developer, I already know how much time the raw calculation takes, and I can estimate performance by directly multiplying the cost ratio. (Yes, I know it's not easy because the types of operations between execution and proof are different, especially in terms of SIMD/parallelization and memory access methods, so even the overhead ratio is partially hardware dependent. But even so, I still think the "spending multiplier" is a very valuable indicator, even if it is not perfect.)"