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

# Demand Driver

<figure><img src="/files/0udm1PbPVjoXcx0dqA1V" alt=""><figcaption></figcaption></figure>

To ensure long-term sustainability and organic value growth, Piggycell integrates **native demand vectors** into protocol design:

1. **Ecosystem Sink Mechanisms**
   * Token-burn events tied to one-time NFT purchases
   * Usage-based redemption (e.g., hourly charging rate)
   * Premium challenge access or performance boosts
2. **Circular Utility Loop**
   * Earn via usage → Spend via charging/NFTs → Re-earn via missions, referrals, governance → Stake for higher tier access → This loop ensures **that PIGGY flows continuously through rewards earned by users.**
3. **Dynamic Supply Control**
   * Emissions schedule aligned with network adoption metrics
   * Adjustable reward pool tied to staking ratio and infrastructure uptime
4. **Cross-Ecosystem Bridgeability**
   * PIGGY is designed to be multichain-compatible, allowing it to move across Ethereum L2s, Internet Computer, and other RWA-aligned networks—expanding liquidity and utility reach.


---

# 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://piggycell.gitbook.io/docs/tokenomics/demand-driver.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.