> 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/chains/seismic-tx-type.md).

# SEISMIC\_TX\_TYPE

Transaction type byte for Seismic transactions

Protocol constant representing the transaction type byte for Seismic custom transactions.

## Overview

`SEISMIC_TX_TYPE` is the EIP-2718 transaction type identifier used by Seismic's custom transaction format. This byte prefixes all serialized Seismic transactions.

## Value

| Representation | Value  |
| -------------- | ------ |
| Hexadecimal    | `0x4A` |
| Decimal        | `74`   |

## Definition

```python
SEISMIC_TX_TYPE: int = 0x4A
```

## EIP-2718 Context

EIP-2718 introduced typed transaction envelopes to Ethereum. Transaction types are identified by a single byte prefix:

| Type   | Description                        |
| ------ | ---------------------------------- |
| `0x00` | Legacy transactions (pre-EIP-2718) |
| `0x01` | EIP-2930 (Access lists)            |
| `0x02` | EIP-1559 (Dynamic fee)             |
| `0x03` | EIP-4844 (Blob transactions)       |
| `0x04` | EIP-7702 (Set EOA account code)    |
| `0x4A` | **Seismic custom transactions**    |

## Transaction Format

A serialized Seismic transaction has the format:

```
[0x4A] + RLP([chainId, nonce, gasPrice, gas, to, value, data, ...])
```

Where `0x4A` is the `SEISMIC_TX_TYPE` prefix.

## Protocol Notes

* The SDK automatically sets this type for all shielded writes
* Seismic nodes recognize and process transactions with this type
* Standard Ethereum nodes will reject transactions with unknown types
* This type is part of the Seismic protocol specification

## See Also

* [UnsignedSeismicTx](https://docs.seismic.systems/clients/python/api-reference/transaction-types/unsigned-seismic-tx.md) - Seismic transaction structure
* [sign\_seismic\_tx\_eip712](https://docs.seismic.systems/clients/python/api-reference/eip712/sign-seismic-tx-eip712.md) - Transaction signing
* [ChainConfig](https://docs.seismic.systems/clients/python/chains/chain-config.md) - Chain configuration with chain IDs
* [Shielded Write Guide](https://docs.seismic.systems/clients/python/guides/shielded-write.md) - Guide to sending Seismic transactions


---

# 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/chains/seismic-tx-type.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.
