TxTypeEthereumAccessList
and TxTypeEthereumDynamicFee
(#1142 #1158)EthereumTxTypeEnvelope
(#1171)eth
namespace APIs to support Ethereum API format (#1076 #1077 #1083 #1088 #1093 #1095 #1121 #1123 #1124 #1127 #1129 #1130 #1134 #1172)klay
namespace APIs: klay_maxPriorityFeePerGas
, klay_createAccessList
, and klay_feeHistory
(#1156)rpc.eth.noncompatible
flag that disables Ethereum API format compatibility (#1072)baseFeePerGas
field in the block header API returns (#1183)klay_gasPrice
API to return proper gas price values (#1211)EthTxType
hard fork. If you need the new transaction formats for a service that requires accessing the transactions of other accounts, make sure to update your caver to v1.8.0 (js, java) or higher. For more details on the new types, please refer to Toward Ethereum Equivalence #4 — Ethereum transaction types.eth
andklay
APIseth
namespace and it worked the same as klay
namespace. But starting with v1.8.0, the eth
namespace APIs will adopt Ethereum API return formats. You can find out more in Toward Ethereum Equivalence #3 — Supporting Ethereum API formats. If you want to stick to the behaviors of the old version and use eth
like klay
, just add the --rpc.eth.noncompatible
init option.eth
in the EN’s default allowed API listeth
namespace APIs are supported for ENs, and eth
has been added to the default allowed list. You need to add eth
to the configurations pf RPC_API
and WS_API
in the kend.conf
file in order to use eth
APIs. net
, web3
APIs used with Ethereum tools like hardhat have also been added to the list. To sum up, the default API white list in v1.8.0 includes: RPC_API="klay,net,eth,web3", WS_API="klay,net,eth,web3"