> 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/legacy-fields.md).

# LegacyFields

Standard EVM transaction fields

Standard EVM transaction fields used in [`TxSeismicMetadata`](/clients/python/api-reference/transaction-types/tx-seismic-metadata.md) for AAD (Additional Authenticated Data) construction.

## Definition

```python
@dataclass(frozen=True)
class LegacyFields:
    chain_id: int
    nonce: int
    to: ChecksumAddress | None
    value: int
```

## Fields

| Field      | Type                      | Description                                         |
| ---------- | ------------------------- | --------------------------------------------------- |
| `chain_id` | `int`                     | Numeric chain identifier (e.g., `5124` for testnet) |
| `nonce`    | `int`                     | Sender's transaction count                          |
| `to`       | `ChecksumAddress \| None` | Recipient address, or `None` for contract creation  |
| `value`    | `int`                     | Amount of wei to transfer                           |

## Example

```python
from seismic_web3 import LegacyFields

legacy = LegacyFields(
    chain_id=5124,
    nonce=42,
    to="0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266",
    value=1 * 10**18,  # 1 ETH in wei
)
```

## Notes

* Called "legacy" because these fields are unchanged from standard Ethereum transactions — present in every tx type since pre-EIP-2718
* Does not include `gas`, `gasPrice`, or `data`. These are the standard EVM fields that go into the AAD — `gas`/`gasPrice` are excluded because they aren't part of the authenticated context, and `data` is the plaintext being encrypted (so it can't also be AAD input)
* The AAD also includes [`SeismicElements`](/clients/python/api-reference/transaction-types/seismic-elements.md) (encryption params, block hash, expiry). The node validates these fields before the transaction enters the mempool

## See Also

* [TxSeismicMetadata](/clients/python/api-reference/transaction-types/tx-seismic-metadata.md) — uses LegacyFields
* [SeismicElements](/clients/python/api-reference/transaction-types/seismic-elements.md) — Seismic-specific fields (contrast)
* [UnsignedSeismicTx](/clients/python/api-reference/transaction-types/unsigned-seismic-tx.md) — full transaction structure


---

# 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/clients/python/api-reference/transaction-types/legacy-fields.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.