EthereumTxTypeEnvelope
. Therefore, users can successfully deploy transactions generated by Ethereum development tools on Klaytn. The type delimiter is also omitted when users use eth
namespace APIs, so they can use Klaytn just as if they were using Ethereum. Using klay
namespace APIs, users can deploy and retrieve Ethereum formatted transactions as a type of Klaytn transactions without getting confused with the existing Klaytn transaction types.EthereumTxTypeEnvelope
which allows for separation and expansion for future Ethereum transaction types.EthereumTxTypeEnvelope
is an additional type delimiter and used only for raw transactions and type numbering. It is not used for transaction hash or signature hash. For that purpose, EthereumTransactionType
as defined in EIPs is used.0x78
TxTypeEthereumAccessList
represents a type of Ethereum transaction specified in EIP-2930. This transactions type contains an access list, a list of addresses and storage keys that the transaction is supposed to access. Since this transaction type exists to support compatibility, it only works with EOAs associated with [AccountKeyLegacy]. EOAs associated with other account key types should use other transaction types such as TxTypeValueTransfer
, TxTypeSmartContractExecution
, and so on. This transaction type can create accounts, transfer tokens, deploy/execute smart contracts or a mix of the aforementioned.EthTxTypeCompatibleBlock
TxTypeEthereumAccessList
that is a concatenation of EthereumTxTypeEnvelope
and EthereumTransactionType
. This must be 0x7801.gas
* gasPrice
. For example, the sender will pay 10 KLAY for a transaction fee if gas is 10 and gasPrice is 10^18. See [Unit of KLAY].peb
to be transferred.SenderTxHash
for this transaction type, the RLP serialization proceeds as follows:eth_getTransactionByHash
klay_getTransactionByHash
TxTypeEthereumDynamicFee
represents a type of Ethereum transaction specified in EIP-1559. This transaction type contains gasTipCap
and gasFeeCap
instead of gasPrice
. Since this transaction type exists to support compatibility, it only works with EOAs associated with [AccountKeyLegacy]. EOAs associated with other account key types should use other transaction types such as TxTypeValueTransfer
, TxTypeSmartContractExecution
, and so on. This type of transaction can create accouns, transfer tokens, deploy/execute smart contracts, or a mix of the aforementioned.EthTxTypeCompatibleBlock
gasTipCap
and gasFeeCap
should take the gas price for the respective network, which is 250 ston at the time of writing.TxTypeEthereumDynamicFee
that is a concatenation of EthereumTxTypeEnvelope
and EthereumTransactionType
. It must be 0x7802
.baseFee
. Since Klaytn has a fixed gas price, gasTipCap
and gasFeeCap
should take the gas price for the respective network, which is 250 ston at the time of writing.gas
* gasFeeCap
. Since Klaytn has a fixed gas price, gasTipCap
and gasFeeCap
should take the gas price for the respective network, which is 250 ston at the time of writing.peb
to be transferred.SenderTxHash
for this transaction type, the RLP serialization proceeds as follows:eth_getTransactionByHash
klay_getTransactionByHash