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

Releases: klaytn/caver-js

Release v1.8.2-r.c2

18 Apr 06:14
a2a5199
Compare
Choose a tag to compare
Release v1.8.2-r.c2 Pre-release
Pre-release

v1.8.2-rc.2 Release Notes

Fixes

  • Fixed logic to send old tx types object to Klaytn Node for using keystore in Node. (#646, #647)

Release v1.8.1-rc.7

01 Apr 05:30
3c386f0
Compare
Choose a tag to compare
Release v1.8.1-rc.7 Pre-release
Pre-release

v1.8.1-rc.7 Release Notes

Fixes

  • Fixed to handle no gasPrice when formatting a transaction receipt. (#638)
  • Fixed a bug when localStorage is available but access is restricted. (#639)

Release v1.8.1-rc.6

23 Mar 00:18
8a4aad7
Compare
Choose a tag to compare
Release v1.8.1-rc.6 Pre-release
Pre-release

v1.8.1-rc.6 Release Notes

Fixes

  • Fixed type errors. (#635)

Release v1.8.1-rc.5

22 Mar 07:42
fe57427
Compare
Choose a tag to compare
Release v1.8.1-rc.5 Pre-release
Pre-release

v1.8.1-rc.5 Release Notes

Fixes

  • Fixed type errors. (#633)

Release v1.8.1-rc.4

21 Mar 05:55
87ca0ff
Compare
Choose a tag to compare
Release v1.8.1-rc.4 Pre-release
Pre-release

v1.8.1-rc.4 Release Notes

Breaking Change

  • To create a transaction, you must use the create function, not the constructor since v1.8.1-rc.4.
    If you use new caver.transaction.xxx({...}) to create a transaction instance, use caver.transaction.create({...}) instead.

Fixes

  • Fixed a bug in klaytnCall that is declared as a static variable and used publicly when using multiple Caver instances. In case of using multiple instances, since static variables are overwritten based on klaytnCall of the latest Caver instance, when signing a transaction in an instance other than the latest Caver, the endpoint to which the rpc call should be sent is changed to the provider of another instance has been modified. (#534)

Release v1.8.1-rc.3

14 Mar 01:09
62a11f1
Compare
Choose a tag to compare
Release v1.8.1-rc.3 Pre-release
Pre-release

v1.8.1-rc.3 Release Notes

Fixes

Release v1.8.1-rc.2

10 Mar 00:09
c5443db
Compare
Choose a tag to compare
Release v1.8.1-rc.2 Pre-release
Pre-release

v1.8.1-rc.2 Release Notes

Fixes

  • Fixed caver.klay.estimateGas return type. (#619)
  • Downgrade ipfs-http-client version to support Node v12 and v14. (#618)

Release v1.8.1-rc.1

08 Mar 04:27
0fb7f0b
Compare
Choose a tag to compare
Release v1.8.1-rc.1 Pre-release
Pre-release

v1.8.1-rc.1 Release Notes

Improvements

Release v1.8.0

07 Mar 04:22
d710fba
Compare
Choose a tag to compare

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!

  • 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

Release v1.8.0-rc.1

06 Mar 14:14
c5bcee2
Compare
Choose a tag to compare
Release v1.8.0-rc.1 Pre-release
Pre-release

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