# eth\_sendRawTransaction Submits a signed transaction to the network. On Seismic, this endpoint is extended in two ways beyond standard Ethereum. ## Seismic transactions (type `0x4A`) The endpoint accepts Seismic transaction type `0x4A` in addition to all standard Ethereum transaction types. Seismic transactions include encrypted calldata and `SeismicElements` metadata (e.g. encryption public key, block expiry). The transaction stays encrypted in the mempool and in blocks — decryption only happens inside the TEE at execution time. See [Transaction Lifecycle](/reference/seismic-transaction/tx-lifecycle.md) for the full flow. ## EIP-712 typed data The endpoint also accepts EIP-712 typed data as an alternative to RLP-encoded bytes. Instead of passing a hex-encoded raw transaction, you can pass a signed EIP-712 `TypedData` object directly. The node decodes the typed data, recovers the signer, and submits the transaction to the pool. ## Related * [The Seismic Transaction](/reference/seismic-transaction.md) — transaction type specification * [Transaction Lifecycle](/reference/seismic-transaction/tx-lifecycle.md) — end-to-end transaction flow * [Shielded Writes](/clients/typescript/viem/shielded-writes.md) — sending transactions with seismic-viem --- # 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/rpc-methods/eth-send-raw-transaction.md?ask= ``` 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.