> 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/how-sedas-burn-works.md).
# How SEDA’s Burn Works
How SEDA token burn works: deterministic burn tied to Oracle Program execution, network computation, and inherited security across SEDA Onchain and SEDA Fast.
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.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.seda.xyz/home/token-overview/seda-token-utility/how-sedas-burn-works.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
