# send\_shielded\_transaction

Build, encrypt, sign, and broadcast a shielded transaction.

## Signatures

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

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

## Parameters

| Parameter   | Type                                                                                                            | Default  | Description                                     |
| ----------- | --------------------------------------------------------------------------------------------------------------- | -------- | ----------------------------------------------- |
| `to`        | `ChecksumAddress`                                                                                               | Required | Recipient contract address                      |
| `data`      | `HexBytes`                                                                                                      | Required | Plaintext calldata (SDK encrypts it)            |
| `value`     | `int`                                                                                                           | `0`      | Wei to transfer                                 |
| `gas`       | `int \| None`                                                                                                   | `None`   | Gas limit (defaults to `30_000_000`)            |
| `gas_price` | `int \| None`                                                                                                   | `None`   | Gas price in wei (fetched from chain if `None`) |
| `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` — transaction hash from `eth_sendRawTransaction`.

## Example

```python
from seismic_web3.contract.abi import encode_shielded_calldata

data = encode_shielded_calldata(SRC20_ABI, "transfer", ["0xRecipient", 100])
tx_hash = w3.seismic.send_shielded_transaction(to="0xTokenAddress", data=data)
```

## What's encrypted

The SDK encrypts the `data` field (function selector + arguments) using AES-GCM with the ECDH-derived key. An observer can see `from`, `to`, `value`, and gas parameters, but **not** which function was called or what arguments were passed.

## Notes

* For contract interactions, prefer `contract.write.functionName(...)` which handles ABI encoding and encryption automatically
* Creates a `TxSeismic` (type `0x4a`) transaction
* SDK auto-fetches nonce via `eth_getTransactionCount`

## See Also

* [debug\_send\_shielded\_transaction](/clients/python/namespaces/methods/debug-send-shielded-transaction.md) — Same pipeline with debug artifacts
* [signed\_call](/clients/python/namespaces/methods/signed-call.md) — Read-only equivalent (no state change)
* [contract.write](/clients/python/contract/namespaces/write.md) — High-level contract write API
* [SeismicSecurityParams](/clients/python/api-reference/transaction-types/seismic-security-params.md) — Security parameter reference


---

# Agent Instructions: 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:

```
GET https://docs.seismic.systems/clients/python/namespaces/methods/send-shielded-transaction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.