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

# FansHood Economic Model

In FansHood, a three-token system combined with platform points will be implemented to provide stakeholders with a clear incentive structure, fostering value creation and accumulation mechanisms for a sustainable ecosystem. Users engaging in content creation, transactions, or participating in crucial governance votes on FansHood will Fans or Points rewards. Fans and Points represent airdrop privileges within the FansHood project.

FansHood aims to coordinate incentives between users and developers in a novel and exciting manner. 

* Reward users and creators for engaging in FansHood interactions, encouraging them to hold tokens for additional rewards and sustained investment returns. 
* Decentralize ownership and governance of FansHood, making decentralization a practical reality in terms of tokens. 
* Combine web2 and web3 content for token issuance based on user growth and platform traffic, ensuring the reasonable distribution of tokens.

<figure><img src="/files/eHdNLNGzrr5Mag2cn476" alt=""><figcaption></figcaption></figure>


---

# 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://docs.fanshood.io/mainpage/fanshood-economic-model.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.