# Worked Example

### Worked Example

#### Scenario: Era 1, Day 100

| Parameter           | Value                                                           |
| ------------------- | --------------------------------------------------------------- |
| Active nodes        | 5,000                                                           |
| Daily pool          | 342,466 $SIGHT (no Vision Credits sold yet)                     |
| Node setup          | Claw Pro, 6 hours of high-quality capture in an underserved hex |
| Node's score        | 412                                                             |
| Network total score | 184,500                                                         |

#### Calculation

```
score share = 412 / 184,500 = 0.2233%
reward = 342,466 × 0.002233 = ~764.7 $SIGHT
```

***

### Six Months Later: Vision Credits Are Selling

Now assume Vision Credit sales have grown to **$50,000/day** in burn (\~5M $SIGHT at $0.01/SIGHT spot).

The recycled pool adds **1.25M $SIGHT** per epoch on top of the era emission.

The same node, holding its share at 0.2233%, would earn:

```
reward = (342,466 + 1,250,000) × 0.002233 = ~3,553 $SIGHT
```

***

### The Takeaway

> As real demand grows, every miner's share gets paid out of a **thicker pool** — without inflation, without re-issuance, without cap erosion.

The same effort, the same data quality, the same contribution share — but **4.6× the reward** because real buyers are consuming the network's data.


---

# 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://clawglasses.gitbook.io/clawglasses-docs/reward-engine/worked-example.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.