> For the complete documentation index, see [llms.txt](https://docs.seda.xyz/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.seda.xyz/home/token-overview/seda-token-utility/seda-growth-engine-explained.md).

# SEDA Growth Engine Explained

SEDA’s ecosystem expansion increases the “surface area” that contributes to network usage and associated token burn.

Each new integration to the network introduces:

* Additional Oracle Programs
* New market types
* Higher request frequency
* Greater computational density

As SEDA’s programmable oracle logic continues to unlock more complex use cases — 24/7 equity perpetual markets, complex structured products, new prediction markets, dynamic liquidation models —more builders migrate to the network adding to the number of data requests executed.

Usage compounds, and compounded usage compounds burn. The more SEDA becomes the baseline oracle infrastructure for onchain markets, the more its token mechanics activate.

**Explore current use cases on SEDA:**

{% content-ref url="/pages/oNWRsVKZOE5pgRd9mOVI" %}
[Dreamcash | 24/7 Equity Perpetual Markets Using Session-Aware Oracle Infrastructure](/home/learn/bespoke-pricing-methodologies/dreamcash-or-24-7-equity-perpetual-markets-using-session-aware-oracle-infrastructure.md)
{% endcontent-ref %}

{% content-ref url="/pages/a24wXbwrZnuNKJjfERyZ" %}
[Injective | 24/5 US Equities Using Session-Aware Oracle Programs](/home/learn/bespoke-pricing-methodologies/injective-or-24-5-us-equities-using-session-aware-oracle-programs.md)
{% endcontent-ref %}


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.seda.xyz/home/token-overview/seda-token-utility/seda-growth-engine-explained.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.