> For the complete documentation index, see [llms.txt](https://docs.prosper-fi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prosper-fi.com/protocol-mechanics/hashrate-operation/monitoring-miners.md). # Monitoring Miners The amount of live hashrate is fundamental to the success of Prosper and PROS. Therefore, a core part of the protocol will be to monitor and ensure that the amount of live hashrate remains above the minimum peg relative to the total token supply. There are a number of mechanisms in place to ensure the protocol’s minimum peg will be properly maintained. These measures will be executed in the following order (the protocol will move to the next measure should the previous one fails to bring the peg in place): * **Hashrate buffer:** hashrate that’s not included in the total live hashrate amount as displayed on our v1 app dashboard * **Deploying new miners:** within the remediation period, launch partners who contributed miners in the first place are required to deploy additional hashrate * **Buy & burn PROS from supply:** within the remediation period, launch partners can also buyback & remove PROS permanently from supply until minimum peg is reached *** *More details around these protective mechanisms will be released as we get closer to go-live.* --- # 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.prosper-fi.com/protocol-mechanics/hashrate-operation/monitoring-miners.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.