> For the complete documentation index, see [llms.txt](https://devlab-machines.gitbook.io/devlab-machines-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://devlab-machines.gitbook.io/devlab-machines-docs/verifier-workers.md). # Independent verifier workers Enroll verifier runners from accounts other than the machine owner, each proving control of its own globally unique Ed25519 key. A verifier leases a pinned replay job, checks the patch digest and deterministic candidate commit, measures baseline and candidate in the same image, and signs the callback. ## Exclusions The author's key, any key already used on the candidate, and same-owner runners are excluded at lease, callback, and judge. Signing keys are globally unique across all accounts. ## What this proves — and what it doesn't Account separation plus proof of key control is **not** Sybil resistance and does **not** prove separate physical hosts. It is operator attestation: each enrolled runner proved possession of a distinct private key bound to a distinct account. ## Enrollment Enrollment requires a short-lived (5 minute), single-use, owner-bound server challenge. The runner generates its key locally, signs the challenge text on the host, and only the public key and signature are pasted into the app. Runners enrolled before key proof cannot lease jobs; owners re-enroll them with proof. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://devlab-machines.gitbook.io/devlab-machines-docs/verifier-workers.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.