# Block Rewards

## Network Rewards on GAN Chain

Earn, stake, and grow your influence in the decentralized ecosystem.

GAN Chain introduces a robust reward distribution framework designed to incentivize network contributors whether you're a GPU provider, Validator, Queen, or King.

This system is divided into Proof of Work (PoW) and Proof of Stake (PoS) components, ensuring all roles are rewarded fairly based on performance, participation, and influence.

**Total Block Emission:** **2,880 $GPU** per day *(as of 15 June 2025)*

**King Subnets – 1,440 $GPU/day**

Earn based on the number of **votes** your subnet receives.\
If your subnet has **X votes** and the total network votes are **Y**, you earn:\
`(X / Y) * 1,440 GPU` 

**Examples:**

Total votes = 1000

* Subnet A gets 300 votes ⇒ earns 432 GPU/day
* Subnet B gets 200 votes ⇒ earns 288 GPU/day
* Subnet C gets 500 votes ⇒ earns 720 GPU/day

**Queen Stakers – 720 $GPU/day**

Total staked GPU = 100,000

Earn based on the amount of **$GPU staked** in PoS voting.\
If you’ve staked **X $GPU**, and total staked is **Y**, you earn:\
`(X / Y) * 720 GPU` 

**Examples:**

* Staker A stakes 10,000 GPU ⇒ earns 72 GPU/day
* Staker B stakes 30,000 GPU ⇒ earns 216 GPU/day
* Staker C stakes 60,000 GPU ⇒ earns 432 GPU/day

**Validators – 720 $GPU/day**

Earn based on the number of **nodes bonded**.\
If you’ve bonded **X nodes**, and total bonded nodes are **Y**, you earn:\
`(X / Y) * 720 GPU` 

**Examples:**

Total bonded nodes = 100

* Validator A bonds 10 nodes out of 100 total ⇒ earns 72 GPU/day
* Validator B bonds 40 nodes out of 100 total ⇒ earns 288 GPU/day
* Validator C bonds 50 nodes out of 100 total ⇒ earns 360 GPU/day

### Daily Emission Breakdown

Each day, the network emits a set amount of rewards split into two equal parts:

* 50% → Proof of Work (PoW)\
  Shared between:
  * Providers: Those offering GPU compute power.
  * Kings: Subnet creators and operators.
  * Distribution is based on:
    * Subnet-specific allocation ratios.
    * Queen vote popularity.
* 50% → Proof of Stake (PoS)\
  Equally split:
  * 25% to Validators: Securing the chain, validating blocks.
  * 25% to Queens: Based on voting engagement.

## King Rewards

If you create a subnet, you’re a King  and eligible for 50% of the total emissions via PoW.

* Voting Score: Calculated from Queen votes received by your subnet.
* Reward Formula:\
  (Votes for your subnet / Total votes across all subnets) × 50% daily emissions
* Impact: The more Queens vote for your subnet, the more rewards you earn.
* Role: Kings operate and manage services within their subnets.

## Queen Rewards

As a Queen, you stake and vote your rewards depending on your engagement.

* Reward Pool: 25% of daily emissions.
* Voting Score: Based on how many votes you cast and how consistently you participate.
* Reward Formula:\
  (Your votes cast / Total network votes cast) × 25% daily emissions
* Impact: Broader voting = bigger share. Be active, vote smart.

## Validator Rewards

Validators secure the chain and get rewarded from the remaining 25% emissions.

* Node Score Factors:
  * Uptime
  * Block production efficiency
  * Transaction validation accuracy
  * Consistent participation
* Impact: Better performance = higher rewards.

## Automatic Reward Staking

To promote compounding and network loyalty:

*  Auto-Staked Rewards: All PoW and Queen rewards are automatically restaked daily.
*  Manual Unstaking Required:
  * Queens: Can unstake rewards immediately via the dashboard.
  * Validators: Must wait through a 28-day unbonding period.


---

# 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.gpu.net/gan-chain-l1/block-rewards.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.