Release v1.8.0

v1.8.0 Release Notes

What's New

• In line with Klaytn's pursuit of Ethereum equivalence, Klaytn now supports Ethereum transaction types. But what is an update without SDKs? You can start using these transactions with caver, via caver.transaction.
  • Access lists are now available with TxTypeEthereumAccessList which was introduced with EIP-2930
    • The EthereumAccessList class is available in caver.transaction.ethereumAccessList as TxTypeEthereumAccessList.
  • The transaction type TxTypeEthereumDynamicFee presented in the proposal EIP-1559 is also available
    • The EthereumDynamicFee class is available in caver.transaction.ethereumDynamicFee as TxTypeEthereumDynamicFee.
• The newly added klay namespace API functions are now available with caver via caver.rpc.klay!
  • caver.rpc.klay.getHeader
  • caver.rpc.klay.getFeeHistory
  • caver.rpc.klay.getMaxPriorityFeePerGas
  • caver.rpc.klay.createAccessList
• You can use the ecsign function the new Ethereum transaction types.
  • The nitty-gritty: You have to sign the transaction types EthereumAccessList and EthereumDynamicFee via ecsign to generate the ECDSA signatures.
  • If you are inquisitive, the v in the signature values {v, r, s} for the new Ethreuem transaction types is a parity (0 for even, 1 for odd) of the y-value of the Secp256k1 curve, whereas the v in Klaytn contains chainId, making them incompatible.
  • Find it here.
    • AbstractKeyring#ecsign()
    • SingleKeyring#ecsign()
    • MultipleKeyring#ecsign()
    • RolebasedKeyring#ecsign()