# Token Use Cases

As the Heart of Sentre’s ecosyste&#x6D;*<mark style="color:purple;">\[12]</mark>*, SEN possesses some of the most beneficial use cases for long holders, namely:

![As the Heart of Sentre’s ecosystem, SEN possesses some of the most beneficial use cases for long holders.](/files/xwTVliTXP9NUTjMHKn7w)

## Governance Rights

To propose an on-chain improvement, participants need to stake SEN in order to vote and reach a consensus. The ratified proposals will be implemented and deployed by the foundation team. For example, as Sentre is an open liquidity protocol, if any new project wants to inherit liquidity from Sentre then SEN holders can vote to choose whether or not this dApp project is worth it.

## Fee Reduction

SEN helps reduce and maintain an upper bound of the exchange fee. When swapping, with SEN as the “bridge” between any pair of tokens, users can reduce the exchange rate from 0.3% to only 0.25%.

## Buyback and Make

SEN is designed as a fee collector. With any swapped pair, the fee can be easily transformed into SEN. Then, instead of burning them away, these fees are collected and automatically transmitted to other SEN-based services.

## Protocol Entrepôt

SEN connects all pools in the ecosystem and makes sure any pair of tokens can be swapped. Putting SEN into all existing two-token pools on SenSwap helps users focus all liquidity into one pool instead of having to deposit into three different pools. This increases liquidity effectiveness and reduces the hassle of having to balance between three pairs of tokens when depositing.

As SEN is present in any and every pool, there is no token that can’t be converted into SEN. Therefore, any pair of tokens, no matter how exotic and rare, can be swapped by simply converting both into SEN. Other tokens can also be evaluated via SEN for the same technique.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

*<mark style="color:purple;">\[12]</mark> In cases where SEN is enabled to be active in triad pools.*


---

# 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.sentre.io/litepaper/sen-as-the-heart-of-the-ecosystem/token-use-cases.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.
