> ## Documentation Index
> Fetch the complete documentation index at: https://docs.monad.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Transactions

## Summary

* Same address space and transaction format/fields as Ethereum, so the same wallet software is
  supported.
* Transaction types 0 ("legacy"), 1 ("EIP-2930"), 2 ("EIP-1559"), and 4 ("EIP-7702") are currently supported.
* Pre-[EIP-155](https://eips.ethereum.org/EIPS/eip-155) transactions are allowed on the protocol
  level, as in Ethereum and many other EVM-compatible blockchains. As a result, users are
  discouraged from using an Ethereum address that had previously sent pre-EIP-155 transactions.

## Address space

Same address space as Ethereum (last 20 bytes of ECDSA public key)

## Transaction format

[Same as Ethereum](https://ethereum.org/en/developers/docs/transactions/). Monad transactions use
the same typed transaction envelope introduced in
[EIP-2718](https://eips.ethereum.org/EIPS/eip-2718), encoded with
[RLP](https://ethereum.org/en/developers/docs/data-structures-and-encoding/rlp/).

## Transaction types

These [transaction types](https://ethereum.org/en/developers/docs/transactions/#typed-transaction-envelope)
are supported:

* Type 0 ("legacy")
* Type 1 (["EIP-2930"](https://eips.ethereum.org/EIPS/eip-2930))
* Type 2 (["EIP-1559"](https://eips.ethereum.org/EIPS/eip-1559); the default in Ethereum)
* Type 4 (["EIP-7702"](https://eips.ethereum.org/EIPS/eip-7702)) (see [EIP-7702 on Monad](/developer-essentials/eip-7702))

These types are not supported:

* Type 3 ("EIP-4844")

## Access lists

Access lists ([EIP-2930](https://eips.ethereum.org/EIPS/eip-2930)) are supported but not required.

## Transactions without a chain\_id

[EIP-155](https://eips.ethereum.org/EIPS/eip-155) introduced a transaction standard that includes a
chain id, to prevent transactions from one blockchain from being replayed on another one.

Transactions on Monad should always set the chain id, except for one very specific corner case:

<Note>
  **The corner case:** Some standard smart contracts such as ERC-1820 use a keyless deployment method
  (also known as Nick's method) that exploits replayability, as discussed
  [here](https://eips.ethereum.org/EIPS/eip-1820#deployment-method). In this method, a transaction is
  submitted on Ethereum but is intended to be replayed on other chains in order to have the contract
  deployed at the same address on other blockchains.
</Note>

In order to support this use case, pre-EIP-155 transactions are still allowed on the protocol level
(i.e. according to consensus rules) on Monad. This makes Monad consistent with most blockchains
including Ethereum. (Blockchains that have tried disallowing pre-EIP-155 transactions at the
protocol level have typically ended up reversing course, e.g.
[Celo](https://github.com/celo-org/celo-blockchain/issues/1734).)

However, because of this, please heed the following warning:

<Warning>
  Because replay of pre-EIP-155 transactions is allowed, it is discouraged to send funds to an
  Ethereum address that had previously sent pre-EIP-155 transactions.
</Warning>