# On-Chain Revenue (OCR)

The On-Chain Revenue (OCR) component tracks the real-world value streams that flow into the Energy Web ecosystem. It captures how payments made by corporate users — in USDC, BTC, or other stable assets — move through the network to reward Worker Nodes and strengthen token utility.

This is where Energy Web’s impact becomes measurable. By quantifying on-chain revenue, the community can see how verified compute translates into tangible value and how network adoption directly supports staking yields and token demand. Over time, OCR data will form the foundation for understanding Energy Web’s on-chain economy — connecting ecosystem growth to tokenholder rewards in a transparent, data-driven way.

This component depends on Energy Web Foundation’s implementation of OCR distribution to Worker Nodes and public visibility of those transactions on-chain. Once these data feeds are accessible, ewchain.io will visualize how real-world activity and business adoption fuel network growth and token value.

{% stepper %}
{% step %}

### First

* Track total OCR inflows (in USDC or BTC) that enter the network over time.
  {% endstep %}

{% step %}

### Next

* Break down revenue by solution, showing contributions from SAFc, Katalist, and others.
* Correlate OCR growth with staking yields to visualize how network revenue drives token value.
  {% endstep %}

{% step %}

### Later

* Use simulations to model how changes in OCR affect staking returns and valuation scenarios.
  {% endstep %}
  {% endstepper %}


---

# 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.ewchain.io/about/roadmap/on-chain-revenue-ocr.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.
