# Revenue Model

Beyond the intrinsic value and transactional utility of the EMC token, the project also captures sustainable revenue through the following channels:

1. **Hardware Advertising**
   * **Embedded Ads:** Customized ads placed in AI-enabled hardware (e.g., AR glasses, smart speakers) or platform interfaces.
   * **Targeted Campaigns:** AI-powered user profiling enhances the accuracy of hardware/software ad placement, for which EMC charges an advertising fee.
2. **Hardware Sales**
   * **Proprietary Hardware:** Official EMC products or partner-manufactured devices (e.g., GPU servers, home mining rigs, IoT nodes) contribute sales margins or profits to the ecosystem treasury or relevant collaborators.
   * **Value-Added Services:** Maintenance, upgrades, and data subscriptions are payable in EMC or fiat.
3. **Gas Fees**
   * **Transactions and Contract Execution:** All on-chain activity requires gas paid in EMC.
   * **Revenue Distribution:** 60% of gas fees may be allocated to validators/miners, with the remaining 40% funneled to the DAO fund (e.g., incentive pools).

By integrating token distribution with diversified revenue streams, EMC fosters a robust and sustainable tech ecosystem for AI-and-hardware convergence. As hardware advertising, hardware sales, gas fees, and protocol fees scale, the EMC network gains a more resilient economic foundation—empowering AI Agents, hardware providers, and everyday users to share in genuine, ongoing rewards.


---

# 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://docs.emc.network/emc/emc-network/tokenomics/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.