> For the complete documentation index, see [llms.txt](https://docs.foreprotocol.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.foreprotocol.io/documentation/protocol/protocol-roles/analysts.md). # Analysts **Market analysts are the protocol participants responsible for validating a market's outcome based on a reputable source of results.** If a market depends on the result of a sports game, the result source may be the final score of that game as reported by a verified news outlet. Via this model, FORE indexes real-world outcomes via real-world people, creating a prediction protocol that is infinitely scalable and able to offer markets on any real world event. Analysts collectively act as a decentralized oracle by confirming outcomes on the protocol. This role is critical to FORE Protocol (and its expansion into other solutions) because they act as the 'architects'; they are responsible for verifying a given outcome is accurate, reporting their findings to the blockchain, and ensuring that all payouts are correctly executed. Validators are given a trust score which indicates their ability to validate and allows them to earn greater protocol validation rewards. In order to maintain the healthy homeostasis of the protocol, analysts are incentivized with both positive and negative incentives to ensure that market results are validated accurately and in a timely manner. **VALIDATION PROCESS** In order for a user to verify the outcome of a market, the user must hold or mint an Analyst NFT. To validate a market, the Analyst will ‘vote’ their NFT on an outcome, at which point the NFT is sent to the market contract address and the NFT will be locked until the reward phase. The user's verification power is determined by the value of the NFT power and is limited by the value of the required power for the market validation (e.g. if the user has a power of 3000, and the required power to validate is 1000, the verification force will be 1000). 3.7.2. **REWARDS AND POWER** Rewards are provided for correct verification of markets. The reward is provided as additional power. Additional power cannot be bought, it can only be earned. Additional power can be withdrawn in the form of FORE tokens (which will reduce the power). The user cannot pay for the original power (power at mint). Analysts are rewarded in proportion to the power provided within their respective NFTs. The power of full-side verification is determined by the value of the size of the opposite side of the predictions. Penalties for inaccurate validations also exist asymmetrically to guide user behavior. If the analyst makes an incorrect verification, their NFT is burned and all the accumulated FORE is released and divided between the dispute creator and high guard as a negative incentive for faulty validation is created as a result of inaccurate validation. {% hint style="info" %} Learn how analysts earn rewards [**here**](/documentation/protocol/protocol-rewards/infrastructure-rewards.md). {% endhint %} --- # 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.foreprotocol.io/documentation/protocol/protocol-roles/analysts.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.