> For the complete documentation index, see [llms.txt](https://dmssale.gitbook.io/dmssale/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dmssale.gitbook.io/dmssale/tokenomics.md).

# Tokenomics

The native token of DMS SALE is the foundation of our ecosystem, designed to be the driving force behind our platform.

It's built to empower, incentivize, and make user experiences smoother. 

This token is essential for navigating our dynamic environment seamlessly.

In the following sections, we provide important details about the DMS SALE token, explaining its crucial role in improving overall user engagement.

| Token Name           | DMS Coin                                   |
| -------------------- | ------------------------------------------ |
| Token Symbol         | DMS                                        |
| Token Decimals       | 18                                         |
| Token Address        | 0xD4121306B742E9d9623CB541CA5Bd5BF13F0E204 |
| Total Supply         | 10,000,000,000                             |
| Tokens For Presale   | 55%                                        |
| Tokens For Liquidity | 25%                                        |
| Marketing Funds      | 10%                                        |
| Development Funds    | 10%                                        |


---

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