# Economic Opportunity

## Revenue Model

Tashi's coordination infrastructure generates real revenue. Applications pay for network services, and that revenue flows to operators who provide infrastructure.

### Revenue Split

| Recipient                   | Share | Components                                         |
| --------------------------- | ----- | -------------------------------------------------- |
| **Resource Node Operators** | 60%   | 30% job completions, 10% availability, 20% bonuses |
| **Foundation**              | 30%   | Operations, development, ecosystem                 |
| **Orchestrator Operators**  | 10%   | Coordination infrastructure                        |

This isn't token emission. It's revenue sharing from actual usage.

## How Earnings Work

### Reward Points

Operators earn **Reward Points** backed by USD at a 100:1 ratio (100 Reward Points = $1 USD).

Reward Points accumulate from:

| Source                | Share | Basis                        |
| --------------------- | ----- | ---------------------------- |
| **Job completions**   | 30%   | Pro rata by successful jobs  |
| **Availability**      | 10%   | Pro rata by uptime check-ins |
| **Incentive bonuses** | 20%   | Network-healthy behaviors    |

### Converting to $TASHI

Operators convert Reward Points to $TASHI tokens to withdraw value from the network. This conversion:

* Creates sustainable token demand as network usage grows
* Allows operators to choose when to exit positions
* Provides liquidity through market mechanisms

## Staking Requirements

### Minimum Stake

Each Resource Node requires **10,000 $TASHI** staked to participate.

This stake:

* Signals commitment to the network
* Enables reputation-based slashing for poor performance
* Aligns operator incentives with network health
* No platform fees on staking

### Excess Staking

Operators can stake more than the minimum:

* Excess stake divides evenly across bonded nodes
* Higher stake improves job selection odds
* Diminishing returns multiplier against reputation

**Example**: An operator with 50,000 $TASHI and 2 registered nodes has both bonded at 25,000 each, giving better selection odds than the minimum 10,000.

## Incentive Mechanisms

Twenty percent of operator revenue funds incentive bonuses that reward network-healthy behavior:

### Network Loyalty Bonus (Cash Back)

When operators (supply) become consumers (demand), they create economic turns within the system and increase the value of the network as a whole. We reward this with a cash-back model.

Operators who spend Reward Points on additional coordination services receive bonus multipliers, effectively getting cash back on their network spending. This encourages the economic flywheel:

* Supply becomes demand
* More economic activity within the network
* Increased network value for all participants

### Staking Bonus

Operators who convert Reward Points to $TASHI and stake (rather than immediately selling) receive conversion bonuses. This:

* Increases circulating stake
* Reduces sell pressure
* Rewards long-term alignment

### Peak Demand Bonus

Jobs are tagged as "peak" when demand in a region is high for a specific job type. Operators who handle peak jobs receive premium rates. This:

* Incentivizes global coverage
* Rewards capacity in underserved regions
* Encourages demand spike response

## Competitive Dynamics

Job assignment uses multi-factor scoring:

| Factor                     | Weight                 | Impact                          |
| -------------------------- | ---------------------- | ------------------------------- |
| **Reputation**             | Primary                | Higher reputation = more jobs   |
| **Geographic proximity**   | Critical for tunneling | Local operators preferred       |
| **Current capacity**       | Secondary              | Available nodes get assignments |
| **Stake amount**           | Secondary              | Higher stake signals commitment |
| **Historical performance** | Secondary              | Track record matters            |

This creates a competitive market:

* Better infrastructure → higher reputation → more jobs → higher earnings
* Operators compete on quality, not just presence

## Pooled Staking

Don't want to run infrastructure? You can still participate:

* Stake $TASHI without registering nodes
* Stake enters a pool that allocates to high-reputation unbonded nodes
* Allocation prioritizes nodes with strongest track records
* Pool participants earn rewards when supported nodes complete jobs

This enables passive participation for token holders who prefer not to operate infrastructure.

## Addressable Market

The market opportunity is substantial:

| Vertical                  | Current Spend              | Coordination Opportunity      |
| ------------------------- | -------------------------- | ----------------------------- |
| **Gaming servers**        | $5B+ annually              | 50%+ cost reduction possible  |
| **Robotics coordination** | Growing 25-30% annually    | Cross-operator coordination   |
| **AI agent networks**     | Emerging market            | Trillions of agents projected |
| **Industrial IoT**        | Billions in infrastructure | Cross-boundary coordination   |

As coordination volume grows, operator revenue scales proportionally.

## Getting Started

1. **Acquire $TASHI**: Minimum 10,000 tokens for staking
2. **Set up infrastructure**: See [Node Specifications](/node-operators/nodes/node-specifications.md)
3. **Register your node**: Follow [Installation Guide](/node-operators/nodes/node-installation.md)
4. **Build reputation**: Maintain high uptime, complete jobs successfully
5. **Scale operations**: Add nodes as demand and reputation grow


---

# 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.tashi.network/node-operators/nodes/economic-opportunity.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.
