# Supported Transaction Types

[EIP-155](https://eips.ethereum.org/EIPS/eip-155) introduced a simple replay attack protection mechanism for Ethereum transactions. It was implemented to prevent transactions on one Ethereum-based chain from being valid on another chain. Zircuit does support standard legacy transactions, which comply with EIP-155 (including chain ID).

At the moment, Zircuit does **not** support pre-EIP-155 transactions (without a chain ID). Attempting to submit such transactions will result in rejection.

Zircuit supports [EIP-2930](https://eips.ethereum.org/EIPS/eip-2930) transactions. EIP-2930 further extends this functionality by introducing "Access List" transactions, which allow for explicit inclusion of accounts and storage keys that a transaction will access. This addition helps in optimizing gas fees and improving the predictability of transaction costs.

[EIP-1559](https://eips.ethereum.org/EIPS/eip-1559) transactions are also supported on Zircuit. EIP-1559 introduces a new transaction pricing mechanism aimed at improving fee market efficiency. It includes a base fee, which is a minimum amount of gas that must be paid for a transaction to be included in a block, and adjusts dynamically based on network congestion. Along with the base fee, users can include a "priority fee" to incentivize the sequencer to prioritize their transactions

[EIP-7702](https://eips.ethereum.org/EIPS/eip-7702) transactions type are supported on Zircuit. EIP-7702 is part of Ethereum's Pectra upgrade and allows Externally Owned Accounts (EOAs) to temporarily have code associated with them. It enables account abstraction capabilities for EOAs, allowing features like batched transactions and sponsored gas fees.


---

# 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.zircuit.com/info/architecture/supported-transaction-types.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.