> 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="https://3261080487-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRycfs1JcYnLmMUtAfaoi%2Fuploads%2FojJ34L2WZBFZG5TqKRC2%2Fimage.png?alt=media&amp;token=1950f3ab-f1bd-439a-ad3f-fbf1b3f94e81" 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.