Why do competing ZK provers waste most of their compute racing each other?
机会
In every decentralized ZK prover network today, multiple provers start generating the same proof simultaneously. Only one submission can land on-chain; the rest revert after spending 20 to 60 minutes of GPU time per collision. The effective utilization rate in a competitive pool is roughly one over the number of active provers, so adding more provers makes the waste worse. Commit-reveal schemes reduce collisions but add latency that erodes the benefit of decentralization; reputation-based pre-assignment reintroduces a trusted scheduler. No mechanism has solved task allocation without recreating the centralization it was meant to replace.
为什么重要
Until prover work can be assigned without a coordinator, decentralized ZK proving is economically self-defeating and proof generation stays structurally dependent on centralized infrastructure.
我如何评估机会
机会评分是我的个人判断，而非量化指标：痛苦程度、发生频率，以及当前解决方案的匮乏程度。分数越高，意味着我认为越值得去构建。
出现时造成的痛苦程度。
人们实际遇到它的频率。
当前针对它的优质工具有多匮乏。