# Why #BuildonTitanX? (#BoT)

<figure><img src="/files/ff9ZRsDTTL3YTI6RjwP7" alt=""><figcaption><p>AwesomeX is Built to Lead the Bull Market - Burning gives him a good PUMP!</p></figcaption></figure>

## Hyper Deflationary Mechanism

TitanX's deflationary model is designed to reduce the circulating supply over time, while simultaneously increasing the cost to mine over time, inherently increasing the value of each token:

### \*\*Burning and Locking\*\*&#x20;

#### All protocols within the BoT framework are required to either burn, lock, or stake TitanX. This mechanism reduces the available supply on the market, creating scarcity.

### \*\*Buy Pressure\*\*&#x20;

#### By reducing supply while maintaining or increasing demand, these actions create natural buy pressure, which supports price growth.

## Leveraging the Flywheel Effect

The TitanX ecosystem operates on a principle that can be likened to a flywheel, where initial efforts create momentum that, with continuous effort, becomes self-sustaining and can grow exponentially.&#x20;

***Here's how it works:***

## Initial Main Liquidity Pair with Ethereum\*\*

TitanX is paired with Ethereum (ETH), making it inherently a leveraged play on Ethereum's value. As ETH grows, so does the potential for TitanX.

## Built on TitanX (BoT) Protocols\*\*

These protocols, which include AwesomeX, have their main liquidity pool (LP) paired with TitanX (or another BoT Protocol.) This structure means that any growth in these protocols indirectly supports TitanX's value, creating a feedback loop or flywheel effect for the entire ecosystem.

All of these tokens also focus on either Burning, Staking or Locking TitanX off the market indefinitely thus reducing supply and increasing demand.

## Exponential Growth Potential\*\*

With each new BoT protocol built on TitanX, the ecosystem's value proposition increases, attracting more users, developers, and investors, further fueling growth.


---

# 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.awesomex.win/why-buildontitanx-bot.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.
