# The Seismic Transaction

<figure><img src="/files/14bncp9MPv5oVnNu3ZIx" alt=""><figcaption></figcaption></figure>

Seismic extends Ethereum's transaction model with encrypted calldata and authenticated reads. This section covers the two core mechanisms:

* [**Tx Lifecycle**](/reference/seismic-transaction/tx-lifecycle.md) — How a Seismic transaction is constructed, encrypted, sent, decrypted, and executed. Covers key management, the `SeismicElements` metadata fields, AES encryption with AEAD, node-side decryption, and shielded storage via `CLOAD`/`CSTORE`.
* [**Signed Reads**](/reference/seismic-transaction/signed-reads.md) — How users make authenticated `eth_call` requests that prove `msg.sender` identity. Covers the motivation (preventing from-address spoofing), how signed reads are sent and validated, and the `signed_read` field that prevents replay as write transactions.


---

# 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/reference/seismic-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.