# How SEDA’s Burn Works

The SEDA Network executes data requests across two delivery paths:

* SEDA Onchain, where Oracle Programs execute directly on the SEDA Chain.
* SEDA Fast, where execution inherits security and computation from the SEDA Chain.

In both cases, each data request consumes network resources, as Oracle Programs and Data Proxies are stored, executed, queried, and secured on the SEDA chain.

The value of that computation and inherited security is reflected in a deterministic token burn tied directly to execution across both delivery systems. As execution rates increase, the token burn scales proportionally with network activity.

Data requests, Oracle Program deployments, and transactions can be tracked on the SEDA explorer. 

With SEDA, network usage, security, and burn grow together.

<figure><img src="/files/wR016bAcV8Vm7FFv3krF" alt=""><figcaption></figcaption></figure>


---

# 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.seda.xyz/home/token-overview/seda-token-utility/how-sedas-burn-works.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.