serving: inference miners serve full systems, validators probe them on the trace, and systems are held to a measured latency ceiling - #135
Merged
Conversation
…n the trace, and systems are held to a measured latency ceiling
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
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.
Makes the posted framework true end to end: inference miners run full systems for customers, not just single models, and speed now costs rewards.
Serving systems
SystemEngineruns a certified full system (small model, harness, router, escalation) behind a catalogue model name.mt operator run --serve MODEL=DIGEST@system:/path --escalation-url URL --gpu-layers -1serves it through the normal agent path, so customer traffic through the gateway is unchanged.open_systemaccepts an archive record or an artifact directory, checked against its manifest. The small model can offload to the GPU for serving, while validators still replay on CPU.Probing system operators
judge_full_systemchecks that the trace is signed by the operator and names the certified system, and that the returned answer is the traced final answer. It then runs the step 5 checks on the certified archive: small model replay, router recompute, declared escalation, harness rerun.Latency counts
run_liverecords the validator's own round-trip time for every task. A full system whose end to end p95 is over the arena's latency ceiling scores zero for the round.Checked on a real Qwen3 0.6B: an operator served a certified system through
serve_taken(answer "blue", usage counted, signed trace attached), and the probe passed. The same operator running Qwen3.5 weights under the certified system's name was judged a cheat, with a worst margin of 22.45 logits.Docs:
miner_setup.mddescribes the full system miner,inference_miner.mdgains section 7a (serving full systems) and the trace based verification table, and the playbook adds the latency ceiling and serving.🤖 Generated with Claude Code