In an X post, Vitalik Buterin said, "I wish more ZK and FHE developers could express their performance as a ratio (crypto compute time vs. raw compute time), rather than just saying" we can do N operations per second ".
Because this approach is more hardware-agnostic, it can provide a very valuable metric: how much efficiency have I sacrificed in order to make the application have encryption/privacy features rather than relying on trust mechanisms?
This method is also usually more useful for estimating, because as a developer, I already know how long the original computation will take, so I can estimate the cost of encryption by simply multiplying this ratio.
(Yes, I know it's hard to do because the operations required between execution and proof are heterogeneous, especially when it comes to SIMD parallelization and memory access patterns, which makes even the ratio somewhat hardware-influenced. But even so, I still think the overhead factor is a valuable metric, although it's not perfect.)
Vitalik Buterin: Hopefully developers can express their performance in terms of ratios, rather than "N operations per second"
2025-10-19 22:36:01
Disclaimer:
1. The information provided does not constitute investment advice. Investors should make independent decisions and bear all risks themselves.
2. The copyright of this content belongs to the original author. The views expressed herein are solely those of the author and do not represent the stance or position of this website.
Previous article：
Vitalik Buterin：希望开发者能够以比率的形式表述他们的性能，而不是“每秒可以执行N次操作Next article：
埃隆·马斯克：“人工智能无法破解#Bitcoin 。”
