github.com/amazechain/amc@v0.1.3/docs/run/transactions.md (about)

     1  # Transaction types
     2  
     3  Over time, the Ethereum network has undergone various upgrades and improvements to enhance transaction efficiency, security, and user experience. Three significant transaction types that have evolved are:
     4  
     5  - Legacy Transactions,
     6  - EIP-2930 Transactions,
     7  - EIP-1559 Transactions.
     8  
     9  Each of these transaction types brings unique features and improvements to the Ethereum network.
    10  
    11  ## Legacy Transactions
    12  
    13  Legacy Transactions (type `0x0`), the traditional Ethereum transactions in use since the network's inception, include the following parameters:
    14  - `nonce`,
    15  - `gasPrice`,
    16  - `gasLimit`,
    17  - `to`,
    18  - `value`,
    19  - `data`,
    20  - `v`,
    21  - `r`,
    22  - `s`.
    23  
    24  These transactions do not utilize access lists, which specify the addresses and storage keys to be accessed, nor do they incorporate EIP-1559 fee market changes.
    25  
    26  ## EIP-2930 Transactions
    27  
    28  Introduced in [EIP-2930](https://eips.ethereum.org/EIPS/eip-2930), transactions with type `0x1` incorporate an `accessList` parameter alongside legacy parameters. This `accessList` specifies an array of addresses and storage keys that the transaction plans to access, enabling gas savings on cross-contract calls by pre-declaring the accessed contract and storage slots. They do not include EIP-1559 fee market changes.
    29  
    30  ## EIP-1559 Transactions
    31  
    32  [EIP-1559](https://eips.ethereum.org/EIPS/eip-1559) transactions (type `0x2`) were introduced in Ethereum's London fork to address network congestion and transaction fee overpricing caused by the historical fee market. Unlike traditional transactions, EIP-1559 transactions don't specify a gas price (`gasPrice`). Instead, they use an in-protocol, dynamically changing base fee per gas, adjusted at each block to manage network congestion.
    33  
    34  Alongside the `accessList` parameter and legacy parameters (except `gasPrice`), EIP-1559 transactions include:
    35  - `maxPriorityFeePerGas`, specifying the maximum fee above the base fee the sender is willing to pay,
    36  - `maxFeePerGas`, setting the maximum total fee the sender is willing to pay.
    37  
    38  The base fee is burned, while the priority fee is paid to the miner who includes the transaction, incentivizing miners to include transactions with higher priority fees per gas.