# Tokenomics

**Token Name:** DOGITA\
**Token Symbol:** DOGA\
**Total Supply:** 100,000,000,000

**Presale + Liquidity Allocation:**

* **Presale:** 60% of the initial token supply is allocated to the presale event, ensuring a fair distribution of tokens to early investors.
* **Liquidity:** All funds raised from the presale are used to provide liquidity for DOGITA on decentralized exchanges, ensuring liquidity and stability for trading.

**Taxes Distribution:**

* **Marketing Tax (4%):** A 4% tax is levied on each transaction, with the proceeds allocated to marketing efforts aimed at promoting DOGITA, increasing its visibility, and attracting new investors and users to the ecosystem.

**Token Address BASE | ERC20:** x488542C2320F20D65405a1C03DA769Bc124F9A28

**Token Address BEP20:** 0x05311d9aA0E17D1071986146CeD510C85c71B52f

**Token Address SOL:** AYgw6k8ZzjkmTMAqrV8hbBe53uM8CrWwcbHuk5RMh6Qt

**Tokenomics Summary:**

DOGITA's tokenomics are designed to ensure fair distribution, liquidity provision, and sustainable growth of the ecosystem. With a total supply of 100 billion tokens, the project allocates all tokens initially to the presale, ensuring broad access for early investors. The taxes imposed on transactions, divided between liquidity and marketing, serve to maintain liquidity on exchanges and fund promotional activities, respectively. This balanced approach aims to foster a healthy and thriving ecosystem for DOGITA, driving its adoption and value appreciation over time.

<br>


---

# 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://dogita.gitbook.io/dogita-whitepaper/tokenomics.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.