# Understanding Token Distribution

## Key Concepts

**Token Distribution** is the most important part of building a healthy creator token ecosystem.

* **Tokens are Earned, not Bought -** Tokens are distributed to holders based off of on-chain proofs of engagement (ex: holding an NFT, following on Lens). Because tokens are not [transferable](https://p00ls.gitbook.io/p00ls-v2/p00ls-creator-tokens/transferability), they cannot be sold or bought.
* **Weekly Distribution** - Tokens are distributed weekly to eligible holders. This allows for a creator to take into account future states of their economy and community.
* **Eligible Holders** - Anyone who engages with a creator's web3 ecosystem can be eligible for rewards. The become eligible by holding an NFT, following on Sound.xyz, or any other [engagements](https://p00ls.gitbook.io/p00ls-v2/token-distribution/token-rewards-general/engagement-types) that Creators add as [**Rewards** ](https://p00ls.gitbook.io/p00ls-v2/token-distribution/token-rewards-general)to their [**Token Economy**](https://p00ls.gitbook.io/p00ls-v2/token-distribution/token-economy). 
* **Biggest Holder = Most Engaged Holder** - A holder's token balance directly indicates their engagement within your community. If you're a Creator, your biggest token holder is your biggest fan.
* **Fully On-Chain** - Tokens are automatically airdropped to eligible addresses on-chain. This ensures full composability of a token holder community with other web3 protocols or dApps.

## Token Economy Management

Token distribution is managed through the Creator Portal. Your **Rewards** represent the eligible engagements available to your community. You can adjust, update, and edit your Rewards directly in the Creator Portal. 

To learn more, visit the [Token Rewards](https://p00ls.gitbook.io/p00ls-v2/token-distribution/token-rewards-general) section. <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://p00ls.gitbook.io/p00ls-v2/token-distribution/understanding-token-distribution.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.