> 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/network-security.md).
# Network Security
The SEDA Chain operates under Proof-of-Stake consensus mechanisms. Validators stake SEDA tokens to participate in consensus and secure Oracle Program execution, Data Proxies, data request batching, and signing tamper-resistant proofs.
As circulating supply reduces through usage-based burns, the economic weight securing the network increases, raising the cost of malicious behavior.
Network security scales alongside network growth and security is enforced by bonded stake and protocol rules. Token supply reduction resulting from network usage strengthens network security by increasing the weight of bonded stake, reinforcing integrity of the SEDA Network.
---
# 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/network-security.md?ask=&goal=
```
`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.