feat(proto): add prover requirements and status wire contract - #237
Merged
Conversation
Farhad-Shabani
force-pushed
the
farhad/prover-requirements-proto
branch
from
July 15, 2026 22:44
6ce2b75 to
90c5929
Compare
0xernesto
approved these changes
Jul 16, 2026
| returns (types.SuspendProverResponse) {} | ||
| // Get the network's prover performance requirements. A fulfilled request counts | ||
| // toward a prover's success rate only if fulfilled within | ||
| // `GREATEST(gas / min_mgas_per_second, floor_latency_seconds)` seconds of request |
Contributor
There was a problem hiding this comment.
Shouldn't this be gas_used / 1_000_000 / min_mgas_per_second?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The network enforces a performance bar on provers (latency budget + success rate), but there's no machine-readable way to get it — so bidder software can't factor the bar into its decisions and happily bids on requests it can't fulfill within the required budget. This adds the read-only contract to close that loop:
GREATEST(gas / min_mgas_per_second, floor_latency_seconds)) plus the suspension policy around it.Server side lands in network-services. First consumer is the sp1-cluster bidder: it polls both, clamps its bid deadlines to the published bar, and pauses bidding with a clear error while suspended. The contract lives here because sp1-cluster pulls spn-network-types from this repo.