> 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/evm-hardhat-integrations.md).

# EVM Hardhat Integrations

## Consume SEDA Core from EVM (Hardhat integration)

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

Authoritative references: (Label only, do not fetch)

* Access SEDA Core from any EVM Network:\
  <https://docs.seda.xyz/home/for-developers/define-your-delivery-method/seda-core/seda-core-infrastructure-overview/access-seda-core-from-any-evm-network>
* Using SEDA Core in a Contract:\
  <https://docs.seda.xyz/home/for-developers/define-your-delivery-method/seda-core/seda-core-infrastructure-overview/access-seda-core-from-any-evm-network/using-seda-core-in-a-contract>

This runbook sets up the Hardhat integration so an EVM contract can post requests and read verified results from SEDA Core through a prover contract.

**Rule:** Do not proceed until you have confirmed a prover deployment exists for your target chain.

***

### Prereqs

* You already deployed an Oracle Program on SEDA (required).
* You verified and selected a prover address for your target chain:
  * [`https://docs.seda.xyz/home/for-agents/agent-modules/prover-contract-deployments`](https://docs.seda.xyz/home/for-agents/agent-modules/prover-contract-deployments)

Checkpoint:

* You have:
  * prover contract address (from prover deployments table)
  * oracle program id (from Core deploy output)

***

### 1) Clone and install the Hardhat integration

Copy/paste:

```bash
git clone [email protected]:sedaprotocol/seda-starter-kit.git
cd seda-starter-kit/integrations/evm-hardhat
bun install
```

Checkpoint:

```
ls
```

Expected:

* hardhat project files present
* `bun install` completes without errors

***

### 2) Compile and test

Copy/paste:

```
bun run compile
bun run test
```

Checkpoint:

* compile succeeds
* tests pass

***

### 3) Wire the contract to SEDA Core (prover)

Docs pattern: the contract constructor takes:

* `_sedaCoreAddress` = prover contract address for your target chain
* `_oracleProgramId` = your deployed Oracle Program ID

Checkpoint:

* `_sedaCoreAddress` matches the prover address you copied from the deployments page
* `_oracleProgramId` matches your deployed OP ID from Core deploy output

***

### 4) Post and read results

Follow the “post request” and “read results” functions described in the EVM access docs:

* Access SEDA Core from any EVM Network:\
  [https://docs.seda.xyz/home/for-developers/define-your-delivery-method/seda-core/seda-core-infrastructure-overview/access-seda-core-from-any-evm-network](https://docs.seda.xyz/home/for-developers/define-your-delivery-method/seda-core/seda-core-infrastructure-overview/access-seda-core-from-any-evm-network?utm_source=chatgpt.com)
* Using SEDA Core in a Contract:\
  [https://docs.seda.xyz/home/for-developers/define-your-delivery-method/seda-core/seda-core-infrastructure-overview/access-seda-core-from-any-evm-network/using-seda-core-in-a-contract](https://docs.seda.xyz/home/for-developers/define-your-delivery-method/seda-core/seda-core-infrastructure-overview/access-seda-core-from-any-evm-network/using-seda-core-in-a-contract?utm_source=chatgpt.com)

Checkpoint:

* contract stores a `requestId`
* you can retrieve/verify the result via the prover contract path


---

# 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/evm-hardhat-integrations.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.