Release v1.5.3-rc.4

Fixed

• Fixes the test cases that sometimes fails(#166)

Release v1.5.3-rc.3

Fixed

• Remove unsupported JSON/RPC API : isWriteThroughCaching() (#164)

Others

• add license description in file header.(#165)

Release v1.5.3-rc.2

Fixed

• Unified key value in in-memory wallet.(#163)
  • When adding keyring instance to wallet, the keyring's address(used key in in-memory wallet) converts lowercase.
    Also, when getting keyring instance form wallet, the address to find keyring converts lowercase.

Improvements

• Modified method in ContractMethod class(#161)
  • add call(List argument) / callWithSolidityWrapper(List argument) method in ContractMethod.
    • From now on, even if user don't need to create a CallObject instance, it is created internally.
    • If the function of the smart contract you want to call requires access permission, it maybe need customized CallObject instance.
  • modified encodeABI(), encodeABISolidityWrapper()
    • It handles the case when passed null parameter in these functions.
• Modified method to handle uncompressed public key with 04 tag(#162)

Release v1.5.3-rc.1

Fixes

• Added function getBlockTransactionCountByHash(), getBlockTransactionCountByNumber().[(#157)]
  • These functions have the same behavior as getTransactionCountByHash(), getTransactionCountByNumber().
• Unified error message for method in Abstract class.[(#158)]

Release v1.5.2

v1.5.2 Release Notes

Improvements

• sendRawTransaction() in com.klaytn.caver.rpc.Klay class now can receive a Transaction instance as a parameter (#153).
• encodeContractDeploy() in com.klaytn.caver.abi.ABI class now directly generates ABI bytecode of a contract (which will be fed into the input field of caver.transaction.smartContractDeploy) from the bytecode and the constructor parameters of this contract (#153).

Fixed

Fixed a bug that a smart contract can't choose the right function to execute/call when two or more overloaded functions (having the same name and the same number of input arguments but the type of these arguments are different from each other) (#153). Changes are made in the functions below:
* callWithSolidityWarapper() in com.klaytn.caver.contract.ContractMethod class
* sendWithSolidityWarapper() in com.klaytn.caver.contract.ContractMethod class
* encodeABIWithSolidityWrapper() in com.klaytn.caver.contract.ContractMethod class
* encodeFunctionCallWithSolidityWrapper() in com.klaytn.caver.abi.ABI class

• Fixed bugs in calling JSON-RPC APIs below (#155).
  • com.klaytn.caver.rpc.Klay.getAccount()
  • com.klaytn.caver.rpc.Klay.getAccountKey()
    • Fixed a bug that error occurs when the length of any one of the hexadecimal strings of the 'X' and 'Y' coordinates (your public key) in elliptic curve is less than 64, by padding a zero at the leftmost position in that string.

Release v1.5.2-rc.1

v1.5.2 Release Notes

Improvements

• sendRawTransaction() in com.klaytn.caver.rpc.Klay class now can receive a Transaction instance as a parameter (#153).
• encodeContractDeploy() in com.klaytn.caver.abi.ABI class now directly generates ABI bytecode of a contract (which will be fed into input field of caver.transaction.smartContractDeploy) from the bytecode and the constructor parameters of this contract (#153).

Fixed

• Fixed a bug that a smart contract can't choose the right function to execute/call when two or more different functions have the same number of input argument (#153). Changes are made in the functions below:
  • callWithSolidityWarapper() in com.klaytn.caver.contract.ContractMethod class
  • sendWithSolidityWarapper() in com.klaytn.caver.contract.ContractMethod class
  • encodeABIWithSolidityWrapper() in com.klaytn.caver.contract.ContractMethod class
  • encodeFunctionCallWithSolidityWrapper() in com.klaytn.caver.abi.ABI class
• Fixed a bug that JSON type response string parsed error from calling Klaytn JSON / RPC API (#155)
  • Klay.getAccount()
  • Klay.getAccountKey()

Release v1.5.1

New Features

• Contract class in caver.contract that enables you to use a smart contract as a Java object.
• ABI class in caver.abi that allows you to decode or encode parameters with an ABI (Application Binary Interface).
• ABI class in caver.abi that makes a function/event ID for the given function/event signature.
• KIP7 class in caver.kct.kip7 that allows you to interact with a KIP-7 token contract in Klaytn.
• KIP17 class in caver.kct.kip17 that allows you to interact with a KIP-17 token contract in Klaytn.

Release v1.5.1-rc.1

New Features

• Contract class in caver.contract that enables you to use smart contract as a Java object.
• ABI class in caver.abi that allows you to decode or encode parameters with an ABI (Application Binary Interface).
• KIP7 class in caver.kct.kip7 that allows you to interact with a KIP-7 token contract in Klaytn.
• KIP17 class in caver.kct.kip17 that allows you to interact with a KIP-17 token contract in Klaytn.

Release v1.5.0

v1.5.0 Release Notes

Highlights : The common architecture of caver, the Klaytn SDK, is implemented.

Common Architecture is a new software architecture for Klaytn development environment which is shared by all Klaytn SDKs (caver-js/caver-java). It is designed for your streamlined development experience and ease of extensibility to other programming languages. Common Architecture realizes a much easier implementation of blockchain applications with other languages if you have former experiences with the existing Klaytn SDKs, as they all share the same architectural background.
The changes made in this new version of caver-java align the architectural bases of Klaytn SDKs into a single structure. From these changes, you can understand and develop blockchain applications with Klaytn and expand your choice of languages for building your application, much more easily, fast, and with great convenience.

For more details about caver-java 1.5.0, please visit Getting Started.
This new version does not broke the backward compatibility. Usage with previous versions works as the same as before for the new versions.

New Features

• Introduced caver.account which provides a structure that can be used to update a Klaytn account.

  • Introduced Account class to update a Klaytn account. An Account instance has an address and an AccountKey.
  • • Introduced the AccountKey type classes to represent an account key (AccountKeyPublic, AccountKeyWeightedMultiSig, AccountKeyRoleBased, AccountKeyLegacy, AccountKeyFail, AccountKeyNil), which is used for validating transaction in Klaytn, of a Klaytn account.
      • Introduced AccountKeyLegacy class to represent AccountKeyLegacy
      • Introduced AccountKeyPublic class to represent AccountKeyPublic
      • Introduced AccountKeyFail class to represent AccountKeyFail
      • Introduced AccountKeyNil class to represent AccountKeyNil
      • Introduced AccountKeyWeightedMultiSig class to represent AccountKeyWeightedMultiSig
      • Introduced AccountKeyRoleBased class to represent AccountKeyRoleBased
  • caver.account replaces caver.tx.account in caver-java 1.4.0

• Introduced caver.wallet which provides functionality for using Klaytn account in caver-java

  • Introduced KeyringContainer class to manange keyrings in in-memory wallet
    • Introduced Keyring which includes an address and private key(s)
      • Introduced SingleKeyring which includes an address and a private key
      • Introduced MultipleKeyring which includes an address and private keys
      • Introduced RoleBasedKeyring which includes an address and private keys by role
    • caver.wallet replaces caver.crypto in caver-java 1.4.0
    • caver.wallet.KeyStore replaces caver.wallet.WalletFile in caver-java 1.4.0

• Introduced caver.transaction which provides classes for various transaction types provided by Klaytn

  • Basic type transaction classes
    • Introduced LegacyTransaction class to represent TxTypeLegacyTransaction
    • Introduced ValueTransfer class to represent TxTypeValueTransfer
    • Introduced ValueTransferMemo class to represent TxTypeValueTransferMemo
    • Introduced AccountUpdate class to represent TxTypeAccountUpdate
    • Introduced SmartContractDeploy class to represent TxTypeSmartContractDeploy
    • Introduced SmartContractExecution class to represent TxTypeSmartContractExecution
    • Introduced Cancel class to represent TxTypeCancel
    • Introduced ChainDataAnchoring class to represent TxTypeChainDataAnchoring
  • Fee delegation type transaction classes
    • Introduced FeeDelegatedValueTransfer class to represent TxTypeFeeDelegatedValueTransfer
    • Introduced FeeDelegatedValueTransferMemo class to represent TxTypeFeeDelegatedValueTransferMemo
    • Introduced FeeDelegatedAccountUpdate class to represent TxTypeFeeDelegatedAccountUpdate
    • Introduced FeeDelegatedSmartContractDeploy class to represent TxTypeFeeDelegatedSmartContractDeploy
    • Introduced FeeDelegatedSmartContractExecution class to represent TxTypeFeeDelegatedSmartContractExecution
    • Introduced FeeDelegatedCancel class to represent TxTypeFeeDelegatedCancel
    • Introduced FeeDelegatedChainDataAnchoring class to represent TxTypeFeeDelegatedChainDataAnchoring
  • Fee Delegated with ratio type transaction classes
    • Introduced FeeDelegatedValueTransferWithRatio class to represent TxTypeFeeDelegatedValueTransferWithRatio
    • Introduced FeeDelegatedValueTransferMemoWithRatio class to represent TxTypeFeeDelegatedValueTransferMemoWithRatio
    • Introduced FeeDelegatedAccountUpdateWithRatio class to represent TxTypeFeeDelegatedAccountUpdateWithRatio
    • Introduced FeeDelegatedSmartContractDeployWithRatio class to represent TxTypeFeeDelegatedSmartContractDeployWithRatio
    • Introduced FeeDelegatedSmartContractExecutionWithRatio class to represent TxTypeFeeDelegatedSmartContractExecutionWithRatio
    • Introduced FeeDelegatedCancelWithRatio class to represent TxTypeFeeDelegatedCancelWithRatio
    • Introduced FeeDelegatedChainDataAnchoringWithRatio class to represent TxTypeFeeDelegatedChainDataAnchoringWithRatio
  • caver.transaction replaces caver.tx in caver-java 1.4.0

• Introduced caver.rpc to interact with Klaytn nodes through JSON RPC calls.

  • Introduced caver.rpc.klay to access klay namespace in Klaytn by calling JSON RPC
  • Introduced caver.rpc.net to access net namespace in Klaytn by calling JSON RPC
  • caver.rpc replaces Klay, Net interfaces in caver-java 1.4.0

• Introduced caver.utils to provide utility functions.

Release v1.5.0-rc.1

Release Notes

Highlights : The common architecture of caver, the Klaytn SDK, is implemented.

Common Architecture is a new software architecture for Klaytn development environment which is shared by all Klaytn SDKs (caver-js/caver-java). It is designed for your streamlined development experience and ease of extensibility to other programming languages. Common Architecture realizes a much easier implementation of blockchain applications with other languages if you have former experiences with the existing Klaytn SDKs, as they all share the same architectural background.
The changes made in this new version of caver-js align the architectural bases of Klaytn SDKs into a single structure. From these changes, you can understand and develop blockchain applications with Klaytn and expand your choice of languages for building your application, much more easily, fast, and with great convenience.

For more details about caver-java 1.5.0, please visit Getting Started.
This new version does not broke the backward compatibility. Usage with previous versions works as the same as before for the new versions.

New Features

• Introduced caver.account which provides a structure that can be used to update a Klaytn account.

  • Introduced Account class to update a Klaytn account. An Account instance has an address and an accountKey
  • Introduced the AccountKey type classes to represent an account key of a Klaytn account.
    • Introduced the AccountKeyLegacy class represents AccountKeyLegacy
    • Introduced the AccountKeyPublic class represents AccountKeyPublic
    • Introduced the AccountKeyFail class represents AccountKeyFail
    • Introduced the AccountKeyWeightedMultiSig class represents AccountKeyWeightedMultiSig
    • Introduced the AccountKeyRoleBased class represents AccountKeyRoleBased
  • caver.account replaces caver.tx.account in caver-java 1.4.0

• Introduced caver.wallet which provides functionality for using Klaytn account in caver-java

  • Introduced the KeyringContainer class to manange keyrings in in-memory wallet
    • Introduced Keyring which includes an address and private key(s)
      • Introduced SingleKeyring which includes an address and a private key
      • Introduced MultipleKeyring which includes an address and private keys
      • Introduced RoleBasedKeyring which includes an address and private keys by roles
    • caver.wallet relpaces caver.crypto in caver-java 1.4.0
    • caver.wallet.KeyStore replaces caver.wallet.WalletFile in caver-java 1.4.0

• Introduced caver.transaction which provides classes for various transaction types provided by Klaytn

  • Basic type transaction classes
    • Introduced the LegacyTransaction class represents TxTypeLegacyTransaction
    • Introduced the ValueTransfer class represents TxTypeValueTransfer
    • Introduced the ValueTransferMemo class represents TxTypeValueTransferMemo
    • Introduced the AccountUpdate class represents TxTypeAccountUpdate
    • Introduced the SmartContractDeploy class represents TxTypeSmartContractDeploy
    • Introduced the SmartContractExecution class represents TxTypeSmartContractExecution
    • Introduced the Cancel class represents TxTypeCancel
    • Introduced the ChainDataAnchoring class represents TxTypeChainDataAnchoring
  • Fee delegation type transaction classes
    • Introduced the FeeDelegatedValueTransfer class represents TxTypeFeeDelegatedValueTransfer
    • Introduced the FeeDelegatedValueTransferMemo class represents TxTypeFeeDelegatedValueTransferMemo
    • Introduced the FeeDelegatedAccountUpdate class represents TxTypeFeeDelegatedAccountUpdate
    • Introduced the FeeDelegatedSmartContractDeploy class represents TxTypeFeeDelegatedSmartContractDeploy
    • Introduced the FeeDelegatedSmartContractExecution class represents TxTypeFeeDelegatedSmartContractExecution
    • Introduced the FeeDelegatedCancel class represents TxTypeFeeDelegatedCancel
    • Introduced the FeeDelegatedChainDataAnchoring class represents TxTypeFeeDelegatedChainDataAnchoring
  • Fee Delegated with ratio type transaction classes
    • Introduced the FeeDelegatedValueTransferWithRatio class represents TxTypeFeeDelegatedValueTransferWithRatio
    • Introduced the FeeDelegatedValueTransferMemoWithRatio class represents TxTypeFeeDelegatedValueTransferMemoWithRatio
    • Introduced the FeeDelegatedAccountUpdateWithRatio class represents TxTypeFeeDelegatedAccountUpdateWithRatio
    • Introduced the FeeDelegatedSmartContractDeployWithRatio class represents TxTypeFeeDelegatedSmartContractDeployWithRatio
    • Introduced the FeeDelegatedSmartContractExecutionWithRatio class represents TxTypeFeeDelegatedSmartContractExecutionWithRatio
    • Introduced the FeeDelegatedCancelWithRatio class represents TxTypeFeeDelegatedCancelWithRatio
    • Introduced the FeeDelegatedChainDataAnchoringWithRatio class represents TxTypeFeeDelegatedChainDataAnchoringWithRatio
  • caver.transaction replaces caver.tx in caver-java 1.4.0

• Introduced caver.rpc to interact with Klaytn nodes through JSON RPC calls.

  • Introduced caver.rpc.klay supports klay namespace JSON RPC calls
  • Introduced caver.rpc.net supports net namespace JSON RPC calls
  • caver.rpc replaces Klay, Net interfaces in caver-java 1.4.0

• Introduced caver.utils provides utility functions.