> 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://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 %}
---
# 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/archvie/seda-onchain.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.