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

# Token Use Case

1. DFNDR token holders are entitled to receive revenue shares (In the form of buyback and burn) from all Defender Bot incomes.
2. DFNDR token holders benefit from special discounts on advertising rates within Defender Bot, creating a cost-effective advertising avenue for projects within the community. Opting for transactions in $DFNDR tokens rather than Ethereum (ETH) grants users an enticing 30% discount on service fees.
3. Regular rewards, airdrops and bonuses for long-term DFNDR holders, incentivizing loyalty and commitment to the Defender Bot ecosystem.

By facilitating seamless access to services, offering substantial discounts, and providing avenues for revenue sharing, the token empowers users to actively engage, secure, and contribute to the community. The combination of exclusive benefits, cost-effective advertising opportunities, and ongoing rewards for loyalty solidifies the DFNDR token's role not just as a digital asset but as a cornerstone for sustained growth and commitment within the Defender Bot ecosystem.

<br>


---

# 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://defender-bot.gitbook.io/defender-bot-whitepaper/token-use-case.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.