> For the complete documentation index, see [llms.txt](https://docs.hyper.win/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyper.win/the-hyper-daily-update.md).

# The HYPER Daily Update

**For every new day that ticks over in the contract, these variables get updated:**

* **HYPER Mineable per Day of Mining goes down -0.08% every day** based on day before
  * this mimics the Bitcoin 4-year halving but does it every year, instead of every 4 year
* **hRank Bonus goes down -0.35% every day** based on day before
* **Share Rate goes down -0.22% for every day passed**
  * applied all at once after every staking payout

To make things simple to understand, here's how this works out:

* The "Cost to mine 1 HYPER" moves up 11,000x
  * (the HYPER per day per miner goes down 11,000x from 8.8M to 800)

*The above is not a price prediction of any kind, it's just a description of the math inside of the protocol describing the cost of production over time until the protocol hits its caps and should not be used and/or looked at as financial advice in any way shape or form.*


---

# 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.hyper.win/the-hyper-daily-update.md?ask=<question>&goal=<endgoal>
```

`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.