> 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/decentralized-solver-network.md).
# Decentralized Solver Network
Between SEDA and all networks lives a [decentralized Solver Network](https://docs.seda.xyz/home/for-developers/technical-guides-and-examples/access-data-from-any-network/advanced-run-your-own-solver) tasked with relaying data requests and results between SEDA and all chains. The Solver Network is a permissionless network that any Solver operator can deploy. Solvers monitor the Prover Contract for data requests and offer quotes to the data requestor in a bid to gain the right to manage the relay of their data request to SEDA. A data request cost is determined by the Solver taking into account:
* Their solver service fee
* The data provider set costs
* Network computation and gas
* Overlay cost for source query
Solvers offer a quote to the data requestor in a currency of their choice. The value is settled between the data requestor and the Solver in the selected currency. Once settled, the Solver, using its own inventory of SEDA Tokens, facilitates the relay of data requests in an equal amount of SEDATokens minus the solver service fee.
As Solvers are independent of the SEDA Network, they are responsible for managing their own SEDA Token inventory to participate in facilitating communication between data requestors and the SEDA Network.
The decentralized network of Solvers enables permissionless communication across blockchain networks through SEDA, breaking down ecosystem silos. By providing an intent-centric framework for data transmission, SEDA creates an omnichain access layer that overcomes traditional scalability limitations in cross-chain communication.
---
# 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/decentralized-solver-network.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.