eth provides functions related to accounts, blocks, transactions, configurations of networks or nodes, filters, and so on.eth of Ethereum's JSON-RPC API. Please note that some return values have been adjusted to match the Ethereum's API response body.eth namespace APIs.eth namespace APIs are supported from Klaytn v1.8.0.eth namespace APIs are supported on Klaytn.Please check the Caution section which describes the differences between Klaytn and Ethereum when serving eth namespace APIs in more detail.
0x0 because Klaytn does not have a baseFeePerGas scheme.blockScore in the Klaytn header, which is fixed to 0x1. This is because Klaytn's consensus mechanism is not based on PoW, indicating the technical concept of block difficulty is not applicable to Klaytn core.0x indicating the empty value. Owing to the fact that Klaytn's extraData contains consensus data such as validators addresses, validators signatures, and proposer signature, it is not applicable to eth namespace API.0xe8d4a50fff(=999999999999 in decimal), which is an arbitrary figure since Klaytn has no GasLimit. At the time of writing, this figure is 30 times higher than the block gas limit of Ethereum. Please refer to Computation Cost for more details.0x00...) because Klaytn's consensus mechanism is not based on PoW.0x00...) because Klaytn's consensus mechanism is not based on PoW.0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347, which is the Keccak256 hash of the RLP-encoded bytes of the list containing empty block header because there are no uncles blocks on Klaytn.[] because there is no technical concept of uncles block in Klaytn core.Due to the fundamental design differences between Klaytn and Ethereum, Klaytn transactions cannot be fully supported viaethnamespace APIs.
type returns the transaction type in string (e.g. "LegacyTransaction"), but it has been converted to hexadecimal (e.g. 0x0) to match Ethereum. Transaction types that are only valid in Klaytn always return 0x0.tx.signatures[0].V, tx.signatures[0].R, and tx.signatures[0].S.Due to the fundamental design differences existing between Klaytn and Ethereum, Klaytn transaction receipt cannot be fully supported when served via Ethereum namespace APIs.