> For the complete documentation index, see [llms.txt](https://titano-protocol.gitbook.io/titano/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://titano-protocol.gitbook.io/titano/titano-token/tokenomics/protocol-fee-economy.md).

# PROTOCOL FEE ECONOMY

Titano may collect fees from:

* swaps,
* strategy performance,
* strategy subscriptions,
* vault management,
* premium analytics,
* execution services.

A conceptual allocation could be:

#### 40% — Protocol Treasury

Security, development and ecosystem operations.

#### 25% — $TITANO Ecosystem

Token utility and ecosystem incentives.

#### 20% — Liquidity

Protocol-owned liquidity and market infrastructure.

#### 10% — Strategy Creators

Creator and strategy-provider incentives.

#### 5% — Security

Audits, bug bounties and emergency reserves.

These percentages are illustrative and should be finalized only after economic modelling.


---

# 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://titano-protocol.gitbook.io/titano/titano-token/tokenomics/protocol-fee-economy.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.