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.
機会をどう評価するか
Opportunity Scoreは測定値ではなく、私自身の見解です。どれほど痛みを伴うか、どれほど頻繁に影響を与えるか、そして今日時点で解決策がいかに少ないか。スコアが高いほど、構築する価値が高いと私は考えています。
それが現れたときにどれほどの痛みをもたらすか。
実際にどれほど頻繁に人々がそれに直面するか。
今日時点で、それに対する優れたツールがいかに少ないか。