# $P Tokenomics

## **Value Creation Engine**

#### Real Revenue Backing

**Revenue is generated from:**

* Lending & borrowing interest spreads
* Repayment Fees
* Liquidations
* Bridge & Swap Fees

**Direct Holder Incentives:**

* 100% of protocol revenue is distributed to $P stakers
* Rewards are paid in stablecoins, not inflationary emissions

## Token Fundamentals

#### Token Supply & Allocation

**Total Supply: 1,000,000,000 $P**

**Circulating Supply at Launch: 500,000,000 $P**

| Allocation          | Percentage | Tokens      |
| ------------------- | ---------- | ----------- |
| Public Sale         | 40%        | 400,000,000 |
| Liquidity Provision | 10%        | 100,000,000 |
| Infinitely Locked   | 50%        | 500,000,000 |

* No Venture capital or private Investors
* No team token sell pressure
* Team compensation is derived solely from protocol revenue via staking
* Public sale provides a **2–3 year operational runway**

The 50% staking allocation is **permanently locked** and can never enter circulation.

### Cross-Chain Deployment

$P is launched on Solana and will be interopable across:

* Solana
* BNB
* Monad
* Somnia (soon)
* Stellar (soon)

### Utility & Holder Rights

Holding and staking $P grants:

* **Revenue Participation** - 100% of protocol revenue goes towards $P stakers
* **Future Governance Rights** - Influence protocol parameters and strategic decisions
* **Future Loyalty Benefits** - Premium protocol features and discounts


---

# 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://peridot-finance.gitbook.io/peridot-protocol/usdp-tokenomics.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.