> For the complete documentation index, see [llms.txt](https://docs.getpip.com/getpip/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getpip.com/getpip/tokenomics/pip-token.md).

# PIP Token

### Address

<https://explorer.solana.com/address/HHjoYwUp5aU6pnrvN4s2pwEErwXNZKhxKGYjRJMoBjLw>

### Distribution

The total supply of PIP is 1,000,000,000 tokens, all minted at once. PIP Tokens will be distributed among 4 main groups. Community Treasury is 690,000,000 PIPs ( 69%) of the Total PIP supply. Community treasury will be distributed among 5 groups.

![](/files/LVbCTMFghmRifwD9K1Mg)

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

### Vesting Period

### Reward Farming

Users earn $PIP through various engagement activities such as creating content, peer-to-peer transactions, and community interactions. These rewards are distributed periodically based on participation.

&#x20;**Unclaimed Reward Farming Tokens** \
To ensure fair distribution and prevent token accumulation in inactive wallets, the protocol will introduce an automated mechanism for handling unclaimed reward tokens:

• Auto-Expiration: Reward farming tokens that remain unclaimed for over 30 days will be removed from circulation according to the protocol’s fairness mechanism. \
• Fairness & Integrity: This prevents token hoarding and ensures only active users receive rewards. This mechanism does not impact existing token holders and serves to maintain a healthy, efficient rewards system that benefits active participants.<br>

### Governance

$PIP is the native token of PipDAO. DAO represents ownership of the PIP ecosystem. $PIP holders are members of PipDAO and possess ownership of the PIP ecosystem.

### Staking Rewards

Liquidity providers gain rewards based on their percentage share of the overall liquidity pool. These rewards are paid in our native token $PIP to every provider that locks liquidity.


---

# 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.getpip.com/getpip/tokenomics/pip-token.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.
