# Delegator Nodes Depending on the types of tasks and requirements, delegator nodes help allocate tasks to worker nodes from the tasks pool. After a user submits a job, it will be added to the task pool. Delegators will then match worker nodes with the job based on node availability, machine type, credibility, and other factors if specified by users (such as location etc.). Alliance Games adopts a peer to pool model in terms of tasks allocation; users cannot choose worker nodes directly. It is to reduce idleness in the network - as long as the works are being done, there is not much difference between each worker node. Peer to pool design also reduces the friction in user experience. In the case when one worker node is offline, delegators could seamlessly allocate the task to other backup nodes, without interference from users. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://alliance-games.gitbook.io/alliance-games-litepaper/technical-structure/delegator-nodes.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.