> For the complete documentation index, see [llms.txt](https://edgeverse.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://edgeverse.gitbook.io/whitepaper/overview-of-edgeverse-dao/dao-plugins/court.md). # Court The Court Plugin serves as a solution for subjective disputes that cannot be resolved through smart contracts. It operates by utilizing jurors who must stake a token with the court in order to participate in adjudicating disputes and earning fees. The likelihood of being selected and earning higher fees is determined by the number of tokens activated by each juror. To determine the subjective truth, the DAO Court employs a Schelling game where jurors vote on the ruling they believe their fellow jurors are more likely to support. Incentives are provided for consensus, as jurors who do not vote in favor of the consensus ruling will have some tokens deducted from their stake. On the other hand, jurors who align with the consensus ruling are rewarded with ruling fees and receive juror tokens from those who voted against the majority ruling. The mechanism aims to minimize the number of jurors required to settle a dispute and deliver a ruling. Initially, only a small group of jurors are assigned to an ongoing dispute, and their decision can be appealed through multiple rounds of appeals. While the DAO Court has the potential to resolve any binary dispute, its initial deployment focuses on arbitrating proposal agreements. These agreements involve organizations or entities agreeing to specific rules regarding proposal creation, with collateral at stake that may be forfeited if the Court deems the proposal invalid. --- # 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://edgeverse.gitbook.io/whitepaper/overview-of-edgeverse-dao/dao-plugins/court.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.