> For the complete documentation index, see [llms.txt](https://docs.nearby.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nearby.finance/protocol-layers/proof-of-location-location-layer/node-network/geographic-reward-weighting.md).

# Geographic Reward Weighting

Node rewards are influenced by geographic coverage value, network demand, and strategic infrastructure importance. Higher-tier regions (dense, high-demand, high-value data environments) receive **higher multipliers**, while lower-connectivity regions receive lower baseline multipliers but benefit from mining accessibility.

***

#### Region Tiers <a href="#region-tiers" id="region-tiers"></a>

| Tier                                    | Regions                                                                            | Reward Multiplier                 |
| --------------------------------------- | ---------------------------------------------------------------------------------- | --------------------------------- |
| Tier 1 (High Value)                     | USA, Western Europe, Canada, Australia, Japan, South Korea                         | **2.0x**                          |
| Tier 2 (Developed / Mid Density)        | Eastern Europe, Singapore, Hong Kong, Israel                                       | **1.6x**                          |
| Tier 3 (Emerging Markets)               | Latin America (Brazil, Mexico, Argentina), Middle East (UAE, Saudi Arabia, Turkey) | **1.3x**                          |
| Tier 4 (Low Coverage / Expansion Zones) | Africa, South Asia (India, Pakistan, Bangladesh), Southeast Asia (excluding SG/HK) | **1.0x + Coverage Bonus Scaling** |

**Tier 1**

* Highest device density
* Highest data reliability
* Strongest infrastructure stability&#x20;
* Highest economic activity per node 👉 Therefore they generate **premium-quality proof data**, which increases reward weighting

***

**Tier 2**

* Stable infrastructure
* Medium density coverage
* Moderate competition between nodes

***

**Tier 3**

* Rapidly growing infrastructure zones
* Increasing adoption potential
* Strategic expansion regions

***

**Tier 4**

* Low infrastructure coverage
* High strategic expansion value
* Incentivized via coverage gap rewards

👉 Instead of lowering rewards, Tier 4 gets:

* **coverage-based bonus multipliers**
* **ecosystem expansion incentives**
* **first-node advantage rewards**

***

#### Global Design Intent <a href="#global-design-intent" id="global-design-intent"></a>

This model creates a balanced system:

* Tier 1 = high-value proof density + premium rewards
* Tier 2–3 = balanced expansion zones
* Tier 4 = early adoption + coverage incentives

***

#### Why this matters for Nearby Protocol <a href="#why-this-matters-for-nearby-protocol" id="why-this-matters-for-nearby-protocol"></a>

This structure ensures:

* High-quality geolocation data comes from high-density regions
* Global coverage expands naturally via incentives
* Nodes compete for high-value geographic zones
* Protocol builds a **real-world economic map of physical presence**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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.nearby.finance/protocol-layers/proof-of-location-location-layer/node-network/geographic-reward-weighting.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.