> For the complete documentation index, see [llms.txt](https://docs.ont.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ont.io/decentralized-identity-and-data/ddxf/solutions/offline-judge.md). # Offline Judge An arbitration consists of the following: * Arbitrator * Arbitration scheme * Execution result/outcome * Arbitration contract The resource arbitrator proposes the arbitration of data. The arbitrator queries the required arbitration data according to the API provided by the Marketplace, and publishes the execution results as per the arbitration scheme in the signed arbitration contract. ### Arbitration Process The order data necessary for arbitration is fetched through the API provided by the marketplace, the arbitrator determines the success and failure of the arbitration according to the arbitration contract, and performs the contract on-chain operation. The required parameters are passed through the API provided by marketplace and return the QR code string. ![Sample QR Code](/files/-MAui9umwEK0szPtBUSC) After the arbitration is completed, the funds will be automatically sent to the wallets of both parties (demand and provider) according to the results. The two parties can also query the order status (including the arbitration result) using the marketplace API**.** --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ont.io/decentralized-identity-and-data/ddxf/solutions/offline-judge.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.