> For the complete documentation index, see [llms.txt](https://gitbook-docs.coinmetrics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook-docs.coinmetrics.io/bittensor/precog-methodology/miner-shares-from-ranks.md). # Miner Shares from Ranks ### Share per Rank As mentioned on the previous pages, each miner receives a "share" or weight of that epoch's reward depending on their rank. The share is 1.0 for the best miner and is exponentially decreasing for worse ranks. In the simplest case, without ties, each miners point forecast share is calculated as: $$s\_i =(0.9)^{r\_i}$$ ### Separate shares per forecast Each forecast, point and interval, is evaluated separately, ranked separately, and assigned a share separately. The methodology below in other words is applied twice, once for each forecast ranking. After each miner is awarded their shares the two types are combined into a final share of the rewards which are written to the TAO Blockchain as Miner Weights. ### Ties Miners can tie for a given rank, in particular with newer Miners implementing the base class. When multiple miners produce the same forecast, the shares for the ranks they occupy are divided and distributed equally to each of them. Then the next miner after the tied group continues the pattern $$s\_i = 0.9^{r\_i}$$, independent of any ties before them. For example, in the case of 6 miners where 3x miners tie for 3rd, the shares would be $$\mathbf{s} = \[1.0, 0.9, 0.7317, 0.7317, 0.7317, 0.59049]$$, where $$ 0.7317 = (0.9^2 + 0.9^3 + 0.9^4) / 3 $$ --- # 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://gitbook-docs.coinmetrics.io/bittensor/precog-methodology/miner-shares-from-ranks.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.