# Step 1 - Buy TITANX (ETH)

97% of the ETH that gets used to [create virtual miners](/hyper-virtual-mining.md) for HYPER gets sent to the Buy TITANX smart contract.

This contract can be used by any builder on top of HYPER (send ETH to the smart contract).

The HYPER Buy & Burn smart contract can receive ETH or WETH and/or TITANX.

* if it receives ETH, it will automatically wrap it to WETH for you and it becomes available for users to call the BuyAndBurn function on.
* if it receives WETH, it doesn't need to wrap it and can be used to buy and burn instantly.
* if it receives TITANX, it uses it to buy & burn HYPER

So, if you're a project building on top of HYPER and want to implement a buy and burn that buys TITANX off of the market & then uses that TITANX to buy HYPER & burn it, you can send a portion of the ETH protocol fee to our buy & burn contract and it will take care of everything else.

No need to build your own buy & burn smart contract.

More details on the steps & percentages here: [HYPER ETH Distribution](/hyper-eth-distribution.md)

**Notes on user incentives:**

Users get 0.33% of the ETH in "Distribute ETH" as an incentive for calling the smart contract function to distribute the ETH between payouts, buy and burn and burn pool.

Same 0.33% incentive reward applies to calling the buy & burn function that will buy TITANX off of the market through the uniswap v3 WETH/TITANX pair and use that TITANX to buy HYPER (via TITANX/HYPER) and burn it.

Both can be done inside of the Hyper dApp.


---

# 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/step-1-buy-titanx-eth.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.