Repository navigation
Run EthProofs as a durable Fleet-managed local worker - #25
Merged
Merged
Conversation
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
1 participant
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 EthProofs client now runs as a machine-pinned Fleet app worker with HTTP head polling, a bounded preparation queue, serial local GPU proving, restart-safe state, and retryable completion reporting.
This is stacked on PR #23 (
chore/ziren-v2-stateless, e36e285). Its host and guest keep Ziren 0dd65a15; the guest lockfile and precompile pins are unchanged. The local worker shares its dedicated GPU server, commits proofs and public values before advancing its block cursor, wakes reporting immediately, and retains pending reports until HTTP success. Failed proofs retain prepared inputs for restart. The existing network mode remains available.Validation: the worker compiles on the PR #23 SDK; four recovery/reporting tests pass, including duplicate ownership, corrupted state, restart recovery, and immediate HTTP delivery with retries. The locked Ziren 2.0 guest and release package are being built for live GPU validation. Fleet integration is in ProjectZKM/zkm-fleet#11. GOAT is unchanged.
Initial scope: one machine and replica, preparation concurrency 1, at-least-once API reporting, explicit state transfer for host changes, and manual reconciliation of already reported proofs after deep reorgs.