> 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/clients/python/namespaces/methods/signed-call.md).

# signed\_call

Execute a signed read with encrypted calldata.

## Signatures

```python
# sync
w3.seismic.signed_call(
    *,
    to: ChecksumAddress,
    data: HexBytes,
    value: int = 0,
    gas: int = 30_000_000,
    security: SeismicSecurityParams | None = None,
    eip712: bool = False,
) -> HexBytes

# async
await w3.seismic.signed_call(...same args...) -> HexBytes
```

## Parameters

| Parameter  | Type                                                                                                            | Default      | Description                          |
| ---------- | --------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------ |
| `to`       | `ChecksumAddress`                                                                                               | Required     | Contract address to call             |
| `data`     | `HexBytes`                                                                                                      | Required     | Plaintext calldata (SDK encrypts it) |
| `value`    | `int`                                                                                                           | `0`          | Wei to include in the call context   |
| `gas`      | `int`                                                                                                           | `30_000_000` | Gas limit                            |
| `security` | [`SeismicSecurityParams`](/clients/python/api-reference/transaction-types/seismic-security-params.md) `\| None` | `None`       | Override default security parameters |
| `eip712`   | `bool`                                                                                                          | `False`      | Use EIP-712 typed-data signing path  |

## Returns

`HexBytes` — decrypted response bytes. Empty RPC result (`"0x"`) returns `HexBytes(b"")`.

## Example

```python
raw = w3.seismic.signed_call(to="0xTarget", data=calldata)
if raw:
    print(raw.hex())
```

## Notes

* Does **not** modify blockchain state — this is a read-only `eth_call`
* Both request and response are encrypted end-to-end (calldata, function selector, arguments, and the returned data)
* Does not increment your account nonce
* For contract interactions, prefer `contract.read.functionName(...)` which handles ABI encoding/decoding automatically

## See Also

* [send\_shielded\_transaction](/clients/python/namespaces/methods/send-shielded-transaction.md) — Write equivalent (modifies state)
* [contract.read](/clients/python/contract/namespaces/read.md) — High-level signed read API
* [contract.tread](/clients/python/contract/namespaces/tread.md) — Transparent reads (no encryption)
* [SeismicSecurityParams](/clients/python/api-reference/transaction-types/seismic-security-params.md) — Security parameter reference


---

# 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.seismic.systems/clients/python/namespaces/methods/signed-call.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.