# Token Emission

## Compute Mining Emission

### **1. Allocation**

* **Total Compute Mining Allocation:** 15% of total $GRAFI supply
* **Total Compute Mining Emission:** 315,000,000 $GRAFI\
  (i.e., 15% of the entire supply is set aside for rewarding decentralized GPU providers.)

### 2. Rewards Factors

Four key factors determine how these monthly emissions are distributed among individual GPU providers:

**i. GPU Model**\
• Higher-performance GPUs (i.e., newer architectures, larger memory, or faster processing) earn a larger portion of rewards.\
\
**ii. Uptime Ratio**\
• GPUs that remain online and available for longer durations receive a higher share of rewards.

**iii. Bandwidth**\
• Providers offering higher network throughput or more data-transfer capacity qualify for enhanced rewards.\
\
**iv. Staking Collateral**\
• GPU providers who stakes more GRAFI tokens gain a multiplier on their compute mining rewards, incentivizing them to align with the network’s long-term success.

### 3. Emission Schedule

* **Total Mining Supply:** 315,000,000 $GRAFI
* **Monthly Emission Rate:** 1% of the 315,000,000 $GRAFI (i.e., 3,150,000 $GRAFI) every month.

**First Month**\
• **Emission:** 3,150,000 $GRAFI (1% of 315,000,000)

**Following Months**\
• **Emission Each Month:** 3,150,000 $GRAFI (1% of 315,000,000)

At a steady rate of 1% of the total mining allocation per month, the full 315,000,000 $GRAFI will be distributed over approximately 100 months (a bit over 8 years).


---

# 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.grafilab.io/home/whitepaper/token-info/token-emission.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.