> For the complete documentation index, see [llms.txt](https://docs.seismic.systems/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.seismic.systems/reference/rpc-methods/eth-call.md).

# eth\_call

Executes a message call without creating a transaction on the blockchain. On Seismic, `eth_call` behaves differently depending on whether the call is unsigned or signed.

## Unsigned calls

When you send a standard unsigned `eth_call`, the `from` field is **zeroed out** (`0x00...0`) regardless of what you pass. This is what makes `msg.sender`-based access control possible on Seismic — without it, anyone could set an arbitrary `from` address and bypass access checks.

## Signed calls (signed reads)

To make an `eth_call` that preserves your identity — so the contract can return caller-specific data like shielded balances — you send a raw signed Seismic transaction (type `0x4A`) or an EIP-712 typed data request as the call payload. This is the same format you'd send to [`eth_sendRawTransaction`](/reference/rpc-methods/eth-send-raw-transaction.md).

Set the `signed_read` field to `true` in the transaction's `SeismicElements` to prevent the read from being replayed as an actual transaction. See [Transaction Lifecycle](/reference/seismic-transaction/tx-lifecycle.md) for the full flow.

## Related

* [Signed Reads](/reference/seismic-transaction/signed-reads.md) — detailed signed read specification
* [Shielded Wallet Client](/clients/typescript/viem/shielded-wallet-client.md) — viem client that handles this automatically


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.seismic.systems/reference/rpc-methods/eth-call.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.