# Tokenomics

FUNC is the **utility token** powering the Function Network, facilitating **staking, rewards, and governance** in a decentralized AI ecosystem.

***

## 🔗 **FUNC Token Utility**

1. **🔒 Staking** – Providers and gateways must stake FUNC tokens to participate in the network.
2. **🎁 Rewards** – Staked participants earn FUNC based on their contribution to AI inference.
3. **⚖️ Governance** – Future governance proposals and treasury management may be **FUNC-holder driven**.

***

## 💰 **Earning FUNC**

🔹 **Compute providers & gateways** earn FUNC by contributing compute power during each epoch.\
🔹 **Rewards are proportional** to the share of total **shards (work units) contributed**.

### **Example Calculation:**

* **Total epoch reward pool**: 10,000 FUNC
* **Your contribution**: 10% of total shards
* **Your earnings**: 🎯 **1,000 FUNC**

***

## 📈 **Economic Design**

### **🔗 Fixed Supply & Scarcity**

* FUNC has a **fixed supply of 1,000,000,000 tokens**, ensuring long-term value retention.
* No inflationary mechanisms. FUNC’s utility is **driven by demand and network participation**.

### **🏦 Treasury & Network Growth**

* The treasury is allocated for **ecosystem development, community initiatives, and staking rewards**.
* Governance mechanisms will allow **FUNC holders to propose and vote on treasury allocation**.

***

FUNC fuels **a decentralized, scalable AI network**, ensuring **fair rewards, governance, and long-term sustainability**. 🚀


---

# 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.function.network/function-network/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.