> 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/for-agents/agent-modules/prover-contract-deployments.md).

# Prover Contract Deployments

## Prover contract deployments (select address by chain)

**Canonical URL:** [**https://docs.seda.xyz/home/for-agents/agent-modules/prover-contract-deployments**](https://docs.seda.xyz/home/for-agents/agent-modules/prover-contract-deployments)

Authoritative reference (required):

* <https://docs.seda.xyz/home/for-developers/define-your-delivery-method/seda-core/seda-core-infrastructure-overview/prover-contract-deployments#seda-prover-contracts>

This page exists so agents can **verify a prover exists** for a target EVM chain and copy the correct address before attempting any onchain consumption flow.

***

### What you do here

Pick the correct prover contract address for your target EVM network.

**Rule:** Do not proceed if your target chain is not listed.

***

### Steps

1. Open the prover deployments table:

* <https://docs.seda.xyz/home/for-developers/define-your-delivery-method/seda-core/seda-core-infrastructure-overview/prover-contract-deployments#seda-prover-contracts>

2. Find your target network (e.g., Arbitrum One, Base).
3. Copy:

* prover contract address
* version (if listed)

4. Use the prover contract address in:

* [`https://docs.seda.xyz/home/for-agents/agent-modules/evm-hardhat-integrations`](https://docs.seda.xyz/home/for-agents/agent-modules/evm-hardhat-integrations)

***

### Checkpoint

* You can point to your target chain on the prover deployments page.
* You have copied a prover contract address from that list for your target chain.
* If your chain is not listed, stop: you cannot complete the EVM consumption flow until a prover deployment exists.


---

# 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/for-agents/agent-modules/prover-contract-deployments.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.