> 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/technology/seda-network-architecture/seda-network-architecture.md).

# SEDA Network Architecture

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

### **The Key Components of the SEDA Network**

**The PoS SEDA Chain:** Used for processing of data requests and data storage for distribution.\
\
**Oracle Programs:** Modules that contain data request intent instructions defined by the data requestor.\
\
**Overlay Network**: A multi-party computation (MPC) network that queries data sources.\
\
**Solver Network:** Monitor prover contracts to relay requests and results between SEDA and data requestors.\
\
**SEDA Prover Contract:** Available in any coding language, act as a point of communication to SEDA via a decentralized Solver Network. Responsible for parsing SEDA proofs.&#x20;

### **Key Components for Data Accessibility on the SEDA Network**

**Proxy Nodes**: A single query point for data providers to connect any API to overlay nodes.

**Data Providers:** The private data providers that plug into SEDA and make data available to any blockchain.

Learn more about these features under the [Data Proxy section](/home/for-data-providers/operating-a-data-proxy.md).


---

# 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/technology/seda-network-architecture/seda-network-architecture.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.