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

# WeSendit Token Burn Strategy

**$WSI 206,192,138 WeSendit Tokens Burned**

WeSendit conducts token burns to decrease the overall supply of our native token, WSI. These burns may occur depending on the company's revenue and for potential marketing purposes.

**Last Burn: January 1, 2024**

* [**Amount Burned:** 206,192,138 WSI](https://bscscan.com/token/0x837a130aed114300bab4f9f1f4f500682f7efd48?a=0x000000000000000000000000000000000000dead)

**How are WeSendit Tokens Burned?**

WeSendit tokens are burned by transferring a predetermined quantity of tokens to a burn address, rendering them irretrievable and permanently removing them from circulation. WeSendit ensures transparency by providing the transaction ID for each burn, allowing the public to verify the transactions on the Binance Smart Chain.

**WeSendit Burning Mechanism**

WeSendit plans to allocate up to 10% of its quarterly revenues, derived from Web3 subscriptions, for the repurchase, holding, and burning of WeSendit tokens. The team intends to burn up to 500 million WeSendit tokens in conjunction with promotional activities and completed Web3 subscriptions, aiming to reduce the total supply to less than 1 billion WSI within five years.

**Previous WeSendit Burn Details can you find on:** [**https://wesendit.io/wesendit-token-burn/**](https://wesendit.io/wesendit-token-burn/)

By consistently burning tokens and transparently documenting these actions, WeSendit aims to enhance the value and stability of the WSI token. This strategic approach not only supports the token economy but also reinforces WeSendit's commitment to a decentralized and robust ecosystem.


---

# 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://docs.wesendit.io/de/tokenomics/wesendit-token-burn-strategy.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.