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

# Token Dispersal

## How can I get SWEET tokens?

There are 3 ways of obtaining SWEET tokens

1\) Liquidity Mining

2\) Protocol Bonding

3\) Initial Stake Pool Offering

### 1) Liquidity Mining

Through liquidity mining individuals will be rewarded with SWEET tokens. By holding on to the token, the liquidity providers will be able to charge the Sweet Protocol for liquidity services provided. 

### 2) Protocol Bonding

The Sweet protocol will periodically sell a limited amount of SWEET tokens in exchange for LP tokens of specific paired crypto assets. 

### 3) Initial Stake Pool Offering(ISPO)

To kickstart the backing of each Sweet Token and to start the Sweet Protocol's [Protocol Owned Liquidity](/whitepaper/white-paper/protocol-owned-liquidity-pol.md) we will be conducting an ISPO. The funds raised during the ISPO will be used to start the backing of SWEET tokens and to also start the protocol owned liquidity. Individuals participating in the ISPO will receive SWEET tokens for participating in the ISPO.  

<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://sweetdao.gitbook.io/whitepaper/white-paper/token-dispersal.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.