# Revenue Model

The Frogyo ecosystem is built on a comprehensive revenue model that incorporates multiple income streams, including user-driven transactions, social incentives, and strategic collaborations. By offering various ways for users to engage, earn, and participate in the economy, Frogyo ensures a sustainable flow of revenue while rewarding both players and investors for their involvement in the platform.

* **In-Game Purchases:** Players can make purchases within the game for items, upgrades, and resources.
* **Social Rewards:**
  * **Referral Rewards:** Users earn rewards for referring new players to the platform.
  * **Friend Shared Rewards:** Players can share rewards with friends to encourage social engagement.
* **Ecosystem Yield Rewards:**
  * **Airdrops & Special Events:** Revenue is boosted through special token distributions and event-based rewards.
  * **Staking Rewards:** Users can stake tokens to earn a passive yield.
  * **Pool Rewards:** Rewards are distributed from shared liquidity pools.
  * **Holder Rank Rewards:** Top holders receive additional rewards based on their rank.
  * **Lucky Draw & Treasure Hunting:** Revenue is driven by engaging reward-based activities.
* **Partnerships & Collaborations:** Revenue is generated through strategic partnerships and collaborations within the ecosystem.
* **Merchandise Sales:** Frogyo-branded merchandise adds another revenue stream.
* **NFT Sales & Royalties:** Income is earned through initial NFT sales and ongoing royalties from secondary market transactions.


---

# 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://whitepaper.frogyo.com/economy/revenue-model.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.
