> 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/archvie/seda-onchain.md).

# SEDA Onchain

SEDA is a layer one blockchain purpose-built for oracle infrastructure. The SEDA Core Network architecture consists of three interdependent subsystems:

**SEDA Chain** — the canonical ledger where data request settlement occurs. This ensures that every data request is recorded, validated, and economically finalized under Byzantine fault-tolerant consensus.

**Overlay Network** — a distributed system responsible for HTTP fetches from arbitrary public or private data sources. This enables the ingestion of both permissionless and permissioned information streams into the SEDA ecosystem.

**Solver Network** — a specialized routing layer tasked with forwarding data requests from origin networks → into SEDA → and back to the origin networks. This network ensures trustless bidirectional data flow across blockchain environments and SEDA.

At the application layer, Oracle Programs are deployed as customizable smart contracts. Unlike static price feeds, Oracle Programs allow developers to:

* Define bespoke data aggregation methodologies.
* Incorporate premium or proprietary data sources.
* Apply arbitrary computation (e.g., weighted indexes, smoothing filters, econometric adjustments).

Formally, an Oracle Program can be described as:[![](https://docs.seda.xyz/home/~gitbook/image?url=https%3A%2F%2Fpbs.twimg.com%2Fmedia%2FGyy-9i-WoAArjjC%3Fformat%3Dpng%26name%3Dsmall\&width=300\&dpr=4\&quality=100\&sign=8a314ce6\&sv=2)](https://x.com/sedaprotocol/article/1958152568682504334/media/1958149902568955904)

where Di​ are individual data sources, and f is a developer-defined transformation (aggregation, filtering, computation). The output y is an on-chain data feed that protocols can consume.

### **Next Steps:**

{% content-ref url="/pages/9cQ8VOKvW98gOkJyQQoT" %}
[Understanding Data Requests for Onchain Delivery](/home/technology/seda-network-architecture/seda-core/seda-core-infrastructure-overview/understanding-data-requests-for-onchain-delivery.md)
{% endcontent-ref %}

<figure><img src="https://4237789557-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWTQafbsjeB6Wu0r07ksa%2Fuploads%2FjGKHycEN6ayB1eUSKbya%2FScreenshot%202025-02-11%20at%2010.26.03%E2%80%AFAM.png?alt=media&amp;token=5a03f2bd-bc6a-4c71-88e7-27e54da5b1ff" alt=""><figcaption></figcaption></figure>


---

# 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/archvie/seda-onchain.md?ask=<question>&goal=<user_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.