# Positive Flywheel

As we can see by employing the [Protocol Owned Liquidity](/whitepaper/white-paper/protocol-owned-liquidity-pol.md), [Protocol Bonding](/whitepaper/white-paper/protocol-bonding.md) and the [Service Fee Model](/whitepaper/white-paper/trading-fees-and-liquidity-as-a-service-payments.md) strategies, The Sweet Protocol will be able to create a positive flywheel effect. Flywheels occur when wins accumulate over time, creating momentum that can keep a business growing 

\
The Sweet Protocol will own 25% of all tokens which means that the protocol will own its own token, since the collection of fees is based on how many SWEET tokens an entity owns, the Sweet Protocol will be able to collect service fees for itself. This will result in creating a Positive Flywheel effect

1. The Sweet Protocol starts by collecting 25% of service fees for itself right away. 
2. Service fees collected automatically go into the Sweet Treasury as [Protocol Owned Liquidity(POL)](/whitepaper/white-paper/protocol-owned-liquidity-pol.md).
3. The Sweet Protocol will be able to mine more of its own SWEET token by liquidity mining
4. More mining increases how many SWEET tokens the Sweet Protocol owns
5. Increases how much of the service fees it can collect.

By implementing this strategy the Sweet Protocol can become a self sustaining decentralised business using Decentralised Liquidity!

\
\ <br>


---

# 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://sweetdao.gitbook.io/whitepaper/white-paper/positive-flywheel.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.