Release v1.1.0

v1.1.0 Release Notes

caver-java-ext-kas v1.1.0 added functions to use new API added in KAS (Klaytn API Service) v1.1.

New Features

• caver.kas.kip17(https://github.com/ground-x/caver-java-ext-kas/pull/43ß)

  • caver.kas.kip17 supports functions to use the KIP-17 API service newly provided by KAS.
    • caver.kas.kip17.deploy POST /v1/contract
    • caver.kas.kip17.getContractList GET /v1/contract
    • caver.kas.kip17.getContract GET /v1/contract/{contract-address-or-alias}
    • caver.kas.kip17.mint POST /v1/contract/{contract-address-or-alias}/token
    • caver.kas.kip17.getTokenList GET /v1/contract/{contract-address-or-alias}/token
    • caver.kas.kip17.getToken GET /v1/contract/{contract-address-or-alias}/token/{token-id}
    • caver.kas.kip17.transfer POST /v1/contract/{contract-address-or-alias}/token/{token-id}
    • caver.kas.kip17.burn DELETE /v1/contract/{contract-address-or-alias}/token/{token-id}
    • caver.kas.kip17.approve POST /v1/contract/{contract-address-or-alias}/approve/{token-id}
    • caver.kas.kip17.approveAll POST /v1/contract/{contract-address-or-alias}/approveall
    • caver.kas.kip17.getTokenListByOwner GET /v1​/contract​/{contract-address-or-alias}​/owner​/{owner-address}
    • caver.kas.kip17.getTransferHistory GET /v1/contract/{contract-address-or-alias}/token/{token-id}/history
  • KAS KIP-17 API is available with caver.kas.kip17 by implementing caver.initKASAPI(chainId, accessKeyId, secretAccessKey) or caver.initKIP17API(chainId, accessKeyId, secretAccessKey [, url]).
  • If the query parameters are required when using the KIP-17 API, it can be used through KIP17QueryOptions class. Fore more scenarios in details, refer to KAS Docs.

• caver.kas.wallet(#42)

  • caver.kas.wallet additionally supports the Key API and Registration API provided in the KAS Wallet API service.
    • caver.kas.wallet.createKeys POST /v2/key
    • caver.kas.wallet.getKey GET /v2/key/{key-id}
    • caver.kas.wallet.signMessage POST /v2/key/{key-id}/sign
    • caver.kas.wallet.registerAccounts POST /v2/registration/account
  • caver.kas.wallet provides additional API to call contract.
    • caver.kas.wallet.callContract POST /v2/tx/contract/call
  • caver.kas.wallet.getAccountList additionally supports status as a query parameter.
    • status field is added in WalletQueryOptions.
    • The status values can be 'enabled', 'disabled', 'all' or 'corrupted'.
    • The status values also can easily set using ACCOUNT_STATUS enum.
  • For more scenarios in detail, refer to KAS Docs.

• caver.kas.tokenHistory(#41)

  • caver.kas.tokenHistory additionally supports the API functions for KIP-37 Multi Token.
    • caver.kas.tokenHistory.getMTListByOwner GET /v2/contract/mt/{mt-address}/owner/{owner-address}
    • caver.kas.tokenHistory.getMT GET /v2/contract/mt/{mt-address}/owner/{owner-address}/token/{token-id}
    • caver.kas.tokenHistory.getMTOwnerListByTokenId GET /v2/contract/mt/{mt-address}/token/{token-id}
    • caver.kas.tokenHistory.getMTContractList GET /v2/contract/mt
    • caver.kas.tokenHistory.getMTContract GET /v2/contract/mt/{mt-address}
  • For more scenarios in detail, refer to KAS Docs.

Improvements

• Added requestId field to ErrorDetail class.(#45)
• Defined enum in TokenHistoryQueryOptions class.(#41)
  • The newly defined enum helps settings in ease.
• Add ApiClient getter/setter to class that represents to KAS API (Wallet, Anchor, TokenHistory and KIP17 classes).(#47)
  • The ApiClient class provides functions that can configure various types of settings for HTTP.
  • ApiClient getter/setter function is available to change HTTP configuration.