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

# Understanding $SPLASH

The SPLASH token's main purpose is to attract liquidity providers and rule the protocol. It is also a crucial part of the Splash Protocol distributed business model.

Here are the utilities:

* Earning protocol fees
* Controlling SPLASH emission
* Voting for protocol changes

## Utility

To get the utilities above, users must lock SPLASH tokens for up to 1 year in the `VotingEscrowLock` smart contract. The minimal locking time is 1 week. The longer the lock the more voting power and share a user gets.

[$veSPLASH](/splash-token/ve-splash.md)

## Earning protocol fees

100% of all Protocol Fees can be claimed by `veSPLASH` holders every week.

## Controlling SPLASH emission

SPLASH inflation takes place via gauges and liquidity providers can claim the newly issued tokens every week.

[Understanding gauges](/gauges/understanding-gauges.md)

## Voting for protocol changes

{% hint style="info" %}
The voting utility is a subject of the V2 protocol release. More information about Voting will be released in Q2 2024.
{% endhint %}

There are two types of governance proposals:

* Proposals for changing protocol parameters
* Proposals to manage DAO treasury


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.splash.trade/splash-token/understanding-splash.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.