> 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/api-reference/transaction-types/tx-seismic-metadata.md).

# TxSeismicMetadata

Complete metadata for a Seismic transaction, used as Additional Authenticated Data (AAD) for AES-GCM encryption.

## Definition

```python
@dataclass(frozen=True)
class TxSeismicMetadata:
    sender: ChecksumAddress
    legacy_fields: LegacyFields
    seismic_elements: SeismicElements
```

## Fields

| Field              | Type                                                                                     | Description                                   |
| ------------------ | ---------------------------------------------------------------------------------------- | --------------------------------------------- |
| `sender`           | `ChecksumAddress`                                                                        | Checksummed sender address                    |
| `legacy_fields`    | [`LegacyFields`](/clients/python/api-reference/transaction-types/legacy-fields.md)       | Standard EVM transaction fields               |
| `seismic_elements` | [`SeismicElements`](/clients/python/api-reference/transaction-types/seismic-elements.md) | Seismic-specific encryption and expiry fields |

## AAD binding

The metadata is RLP-encoded and used as AAD in AES-GCM encryption, ensuring the ciphertext is cryptographically bound to the full transaction context. Any modification to transaction parameters (sender, recipient, value, etc.) invalidates the ciphertext.

## Example

```python
from seismic_web3 import TxSeismicMetadata, LegacyFields, SeismicElements

metadata = TxSeismicMetadata(
    sender="0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266",
    legacy_fields=LegacyFields(
        chain_id=5124,
        nonce=42,
        to="0x00000000219ab540356cBB839Cbe05303d7705Fa",
        value=0,
    ),
    seismic_elements=SeismicElements(...),
)
```

## Notes

* Automatically constructed by the SDK — most users won't interact with this type directly
* Combines [`LegacyFields`](/clients/python/api-reference/transaction-types/legacy-fields.md) and [`SeismicElements`](/clients/python/api-reference/transaction-types/seismic-elements.md) into one structure

## See Also

* [LegacyFields](/clients/python/api-reference/transaction-types/legacy-fields.md) — standard EVM fields
* [SeismicElements](/clients/python/api-reference/transaction-types/seismic-elements.md) — Seismic-specific fields
* [UnsignedSeismicTx](/clients/python/api-reference/transaction-types/unsigned-seismic-tx.md) — transaction that uses this metadata


---

# 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/api-reference/transaction-types/tx-seismic-metadata.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.