# The HYPER Vortex

**10% of all the TITANX bought with ETH** via WETH/TITANX pool gets stored inside of **"The Vortex"**

**8% of all ETH used to start HYPER miners** also gets stored inside of **"The Vortex"**

**This Vortex triggers every 98 days** together with the 98-day cycle payout.

The TITANX in the Vortex (100% used to buy & burn HYPER via TITANX/HYPER) gets released every 98 days.

The ETH in the Vortex (100% used to buy TITANX via WETH/TITANX & then buy and burn HYPER with the TITANX it just bought) gets released every 98 *starting for the first time at day 196.*

<figure><img src="https://media1.giphy.com/media/v1.Y2lkPTc5MGI3NjExZXZraHFwZHNtODA5Z25hcm5iOXNuOXF3ZGlia2ZlOHRhb3Y4ZzczeCZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw/1Bh4tbocQf9X8aO25E/giphy.gif" alt=""><figcaption><p>HYPER Vortex</p></figcaption></figure>

*"The Vortex" is not a wallet, it's stored within the fully decentralised HYPER smart contract and gets triggered via users all around the world calling the functions within the contract using their own private keys, the vortex is never touched and/or passed through a person or entity or central authority.*

*All of this happens through smart contracts that users call & interact with using their own private keys, there is no central actor, authority, individual, group or company doing any critical work whatsoever. It's completely decentralized, owned & ran by the users interacting with the smart contracts deployed on the globally decentralized network called Ethereum.*


---

# Agent Instructions: 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:

```
GET https://docs.hyper.win/the-hyper-vortex.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.