Skip to content
This repository has been archived by the owner on Jul 23, 2024. It is now read-only.

Release v1.8.0-rc.1

Pre-release
Pre-release
Compare
Choose a tag to compare
@jimni1222 jimni1222 released this 06 Mar 14:14
· 271 commits to dev since this release
v1.8.0-rc.1
c5bcee2
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

v1.8.0-rc.1 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!

  • 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: keyring.ecsign
Assets 2
Loading