> 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/sedas-prover-contract.md).

# SEDA’s Prover Contract

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

The SEDA Prover Contract is permissionless and can be deployed to any chain at any time. The prover acts as the point of communication between any network and the decentralized Solver Network. Solvers monitor the Prover Contract for inbound data requests and relay them to the SEDA Network. Once a data request has been executed and the results land on the SEDA Chain, the same Solver relays the results to the network via the Prover Contract. When results are relayed back, the Prover Contract can verify that the data result has come from SEDA.

By deploying a prover contract, any network theoretically gains access to any data type and achieves interoperability with any other network that has a Prover Contract. By integrating with SEDA via a single Prover Contract that is monitored by a Solver Network, SEDA can facilitate same-day access to any data from new networks. In contrast to rigid network-specific architecture, this method can reduce integration time to several hours from what has traditionally been several months.

Any network, protocol or smart contract can interact with SEDA and all its resources without directly integrating with the SEDA Chain.


---

# 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/sedas-prover-contract.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.