Releases: ground-x/caver-java-ext-kas
Release v1.9.0
v1.9.0 Release Notes
New Features
- Supports KAS KIP-37 API.
- Functions to use the KIP-37 API service newly provided by KAS.
- caver.kas.kip37.deploy
POST /v1/contract
- caver.kas.kip37.importContract
POST /v1/contract/import
- caver.kas.kip37.updateContractOptions
PUT /v1/contract/{contract-address-or-alias}
- caver.kas.kip37.getContract
GET /v1/contract/{contract-address-or-alias}
- caver.kas.kip37.getContractList
GET /v1/contract
- caver.kas.kip37.getTokenListByOwner
GET /v1/contract/{contract-address-or-alias}/owner/{owner-address}/token
- caver.kas.kip37.getTokenList
GET /v1/contract/{contract-address-or-alias}/token
- caver.kas.kip37.setApprovalForAll
POST /v1/contract/{contract-address-or-alias}/approveall
- caver.kas.kip37.pause
POST /v1/contract/{contract-address-or-alias}/pause
- caver.kas.kip37.unpause
POST /v1/contract/{contract-address-or-alias}/unpause
- caver.kas.kip37.pauseToken
POST /v1/contract/{contract-address-or-alias}/token/pause/{token-id}
- caver.kas.kip37.unpauseToken
POST /v1/contract/{contract-address-or-alias}/token/unpause/{token-id}
- caver.kas.kip37.create
POST /v1/contract/{contract-address-or-alias}/token
- caver.kas.kip37.burn
DELETE /v1/contract/{contract-address-or-alias}/token
- caver.kas.kip37.mint
POST /v1/contract/{contract-address-or-alias}/token/mint
- caver.kas.kip37.transfer
POST /v1/contract/{contract-address-or-alias}/token/transfer
- caver.kas.kip37.getDeployer
GET /v1/deployer/default
- caver.kas.kip37.deploy
- KAS KIP-37 API is available with
caver.kas.kip37
by implementingcaver.initKASAPI(chainId, accessKeyId, secretAccessKey)
orcaver.initKIP37API(chainId, accessKeyId, secretAccessKey [, url])
. If query parameters are required when using the KIP-37 API, it can be used throughKIP37QueryOptions
class. For more scenarios in detail, refer to KAS Docs.
- Functions to use the KIP-37 API service newly provided by KAS.
- Supports new features in KAS KIP-7 API.
- Function to deploy KIP-7 contracts with fee payer options. You can use fee payer options with
Kip7FeePayerOptions
class.- caver.kas.kip7.deploy
POST /v1/contract
- caver.kas.kip7.deploy
- Function to update fee payer options of the KIP-7 contract with fee payer options. You can use fee payer options with
Kip7FeePayerOptions
class.- caver.kas.kip7.updateContractOptions
PUT v1/contract/{contract-address-or-alias}
- caver.kas.kip7.updateContractOptions
- Function to pause/unpause the KIP-7 contract with a pauser.
- caver.kas.kip7.pause
POST /v1/contract/{contract-address-or-alias}/pause
- caver.kas.kip7.unpause
POST /v1/contract/{contract-address-or-alias}/unpause
- caver.kas.kip7.pause
- Function to add/renounce pauser.
- caver.kas.kip7.addPauser
POST v1/contract/{contract-address-or-alias}/pauser
- caver.kas.kip7.renouncePauser
DELETE v1/contract/{contract-address-or-alias}/pauser
- caver.kas.kip7.addPauser
- Function to mint KIP-7 tokens with a minter.
- caver.kas.kip7.mint
POST v1/contract/{contract-address-or-alias}/mint
- caver.kas.kip7.mint
- Function to add/renounce minter.
- caver.kas.kip7.addMinter
POST v1/contract/{contract-address-or-alias}/minter
- caver.kas.kip7.renounceMinter
DELETE v1/contract/{contract-address-or-alias}/minter
- caver.kas.kip7.addMinter
- For more scenarios in detail, refer to KAS Docs.
- Function to deploy KIP-7 contracts with fee payer options. You can use fee payer options with
- Supports new features in KAS KIP-17 API.
- Function to deploy a KIP-17 contract with fee payer options. You can use fee payer options with
Kip17FeePayerOptions
class.- caver.kas.kip17.deploy
POST /v1/contract
- caver.kas.kip17.deploy
- Function to update fee payer options of the KIP-17 contract with fee payer options. You can use fee payer options with
Kip17FeePayerOptions
class.- caver.kas.kip17.updateContractOptions
PUT v1/contract/{contract-address-or-alias}
- caver.kas.kip17.updateContractOptions
- Function to deploy a KIP-17 contract with fee payer options. You can use fee payer options with
- Supports new features in KAS Wallet API.
- Function to create a fee payer account with the
withoutAccountUpdate
parameter. If you definewithoutAccountUpdate
astrue
, KAS will not update the fee payer account.- caver.kas.wallet.createFeePayer
POST /v2/feepayer
- caver.kas.wallet.createFeePayer
- Function to query a key list by KRN (KAS Resource Name).
- caver.kas.wallet.getKeyListByKRN
GET /v2/key
- caver.kas.wallet.getKeyListByKRN
- Function to get a fee delegated transaction list. This API works with the Cypress network only.
- caver.kas.wallet.getFDTransactionList
GET /v2/history/fd/tx
- caver.kas.wallet.getFDTransactionList
- Function to get a fee delegated transaction by hash. This API works with the Cypress network only.
- caver.kas.wallet.getFDTransaction
GET /v2/history/fd/tx/{transaction-hash}
- caver.kas.wallet.getFDTransaction
- For more scenarios in detail, refer to KAS Docs.
- Function to create a fee payer account with the
Release v1.9.0-rc.2
v1.9.0-rc.2 Release Notes
New Features
- Supports KAS KIP-37 API.
- Functions to use the KIP-37 API service newly provided by KAS.
- caver.kas.kip37.deploy
POST /v1/contract
- caver.kas.kip37.importContract
POST /v1/contract/import
- caver.kas.kip37.updateContractOptions
PUT /v1/contract/{contract-address-or-alias}
- caver.kas.kip37.getContract
GET /v1/contract/{contract-address-or-alias}
- caver.kas.kip37.getContractList
GET /v1/contract
- caver.kas.kip37.getTokenListByOwner
GET /v1/contract/{contract-address-or-alias}/owner/{owner-address}/token
- caver.kas.kip37.getTokenList
GET /v1/contract/{contract-address-or-alias}/token
- caver.kas.kip37.setApprovalForAll
POST /v1/contract/{contract-address-or-alias}/approveall
- caver.kas.kip37.pause
POST /v1/contract/{contract-address-or-alias}/pause
- caver.kas.kip37.unpause
POST /v1/contract/{contract-address-or-alias}/unpause
- caver.kas.kip37.pauseToken
POST /v1/contract/{contract-address-or-alias}/token/pause/{token-id}
- caver.kas.kip37.unpauseToken
POST /v1/contract/{contract-address-or-alias}/token/unpause/{token-id}
- caver.kas.kip37.create
POST /v1/contract/{contract-address-or-alias}/token
- caver.kas.kip37.burn
DELETE /v1/contract/{contract-address-or-alias}/token
- caver.kas.kip37.mint
POST /v1/contract/{contract-address-or-alias}/token/mint
- caver.kas.kip37.transfer
POST /v1/contract/{contract-address-or-alias}/token/transfer
- caver.kas.kip37.getDeployer
GET /v1/deployer/default
- caver.kas.kip37.deploy
- KAS KIP-37 API is available with
caver.kas.kip37
by implementingcaver.initKASAPI(chainId, accessKeyId, secretAccessKey)
orcaver.initKIP37API(chainId, accessKeyId, secretAccessKey [, url])
. If query parameters are required when using the KIP-37 API, it can be used throughKIP37QueryOptions
class. For more scenarios in detail, refer to KAS Docs.
- Functions to use the KIP-37 API service newly provided by KAS.
- Supports new features in KAS KIP-7 API.
- Function to deploy KIP-7 contracts with fee payer options. You can use fee payer options with
Kip7FeePayerOptions
class.- caver.kas.kip7.deploy
POST /v1/contract
- caver.kas.kip7.deploy
- Function to update fee payer options of the KIP-7 contract with fee payer options. You can use fee payer options with
Kip7FeePayerOptions
class.- caver.kas.kip7.updateContractOptions
PUT v1/contract/{contract-address-or-alias}
- caver.kas.kip7.updateContractOptions
- Function to pause/unpause the KIP-7 contract with a pauser.
- caver.kas.kip7.pause
POST /v1/contract/{contract-address-or-alias}/pause
- caver.kas.kip7.unpause
POST /v1/contract/{contract-address-or-alias}/unpause
- caver.kas.kip7.pause
- Function to add/renounce pauser.
- caver.kas.kip7.addPauser
POST v1/contract/{contract-address-or-alias}/pauser
- caver.kas.kip7.renouncePauser
DELETE v1/contract/{contract-address-or-alias}/pauser
- caver.kas.kip7.addPauser
- Function to mint KIP-7 tokens with a minter.
- caver.kas.kip7.mint
POST v1/contract/{contract-address-or-alias}/mint
- caver.kas.kip7.mint
- Function to add/renounce minter.
- caver.kas.kip7.addMinter
POST v1/contract/{contract-address-or-alias}/minter
- caver.kas.kip7.renounceMinter
DELETE v1/contract/{contract-address-or-alias}/minter
- caver.kas.kip7.addMinter
- For more scenarios in detail, refer to KAS Docs.
- Function to deploy KIP-7 contracts with fee payer options. You can use fee payer options with
- Supports new features in KAS KIP-17 API.
- Function to deploy a KIP-17 contract with fee payer options. You can use fee payer options with
Kip17FeePayerOptions
class.- caver.kas.kip17.deploy
POST /v1/contract
- caver.kas.kip17.deploy
- Function to update fee payer options of the KIP-17 contract with fee payer options. You can use fee payer options with
Kip17FeePayerOptions
class.- caver.kas.kip17.updateContractOptions
PUT v1/contract/{contract-address-or-alias}
- caver.kas.kip17.updateContractOptions
- Function to deploy a KIP-17 contract with fee payer options. You can use fee payer options with
- Supports new features in KAS Wallet API.
- Function to create a fee payer account with the
withoutAccountUpdate
parameter. If you definewithoutAccountUpdate
astrue
, KAS will not update the fee payer account.- caver.kas.wallet.createFeePayer
POST /v2/feepayer
- caver.kas.wallet.createFeePayer
- Function to query a key list by KRN (KAS Resource Name).
- caver.kas.wallet.getKeyListByKRN
GET /v2/key
- caver.kas.wallet.getKeyListByKRN
- Function to get a fee delegated transaction list. This API works with the Cypress network only.
- caver.kas.wallet.getFDTransactionList
GET /v2/history/fd/tx
- caver.kas.wallet.getFDTransactionList
- Function to get a fee delegated transaction by hash. This API works with the Cypress network only.
- caver.kas.wallet.getFDTransaction
GET /v2/history/fd/tx/{transaction-hash}
- caver.kas.wallet.getFDTransaction
- For more scenarios in detail, refer to KAS Docs.
- Function to create a fee payer account with the
Release v1.4.0
v1.4.0 Release Notes
Breaking Change
- The
caver.kas.wallet.signMessage
does not supportkrn
parameter. This function has been changed to work using the KAS user's default krn.
New Features
- Adds support for KAS KIP-7 API.
- Functions to use the KIP-7 API service newly provided by KAS.
- caver.kas.kip7.deploy
POST /v1/contract
- caver.kas.kip7.getContract
GET /v1/contract/{contract-address-or-alias}
- caver.kas.kip7.getContractList
GET /v1/contract
- caver.kas.kip7.allowance
GET /v1/contract/{contract-address-or-alias}/account/{owner}/allowance/{spender}
- caver.kas.kip7.balance
GET /v1/contract/{contract-address-or-alias}/account/{owner}/balance
- caver.kas.kip7.approve
POST /v1/contract/{contract-address-or-alias}/approve
- caver.kas.kip7.transfer
POST /v1/contract/{contract-address-or-alias}/transfer
- caver.kas.kip7.transferFrom
POST /v1/contract/{contract-address-or-alias}/transfer-from
- caver.kas.kip7.mint
POST /v1/contract/{contract-address-or-alias}/mint
- caver.kas.kip7.burn
POST /v1/contract/{contract-address-or-alias}/burn
- caver.kas.kip7.burnFrom
POST /v1/contract/{contract-address-or-alias}/burn-from
- caver.kas.kip7.pause
POST /v1/contract/{contract-address-or-alias}/pause
- caver.kas.kip7.unpause
POST /v1/contract/{contract-address-or-alias}/unpause
- caver.kas.kip7.getDeployer
GET /v1/deployer/default
- caver.kas.kip7.deploy
- KAS KIP-7 API is available with caver.kas.kip7 by implementing caver.initKASAPI(chainId, accessKeyId, secretAccessKey) or caver.initKIP7API(chainId, accessKeyId, secretAccessKey, url). If query parameters are required when using the KIP-7 API, they can be used through the
KIP7QueryOptions
class. For more scenarios in detail, refer to KAS Docs.
- Functions to use the KIP-7 API service newly provided by KAS.
- Now supports new functions with KAS Wallet API.
- caver.kas.wallet provides a function that migrates the existing Klaytn accounts to the KAS Wallet API service.
- caver.kas.wallet.migrateAccounts migrates specific Klaytn accounts to KAS Wallet API service.
- Adds support for newly added API functions in KAS Wallet API.
- Functions to use fee payer via KAS Wallet API.
- caver.kas.wallet.createFeePayer
POST /v2/feepayer
- caver.kas.wallet.deleteFeePayer
DELETE /v2/feepayer/{address}
- caver.kas.wallet.getFeePayer
GET /v2/feepayer/{address}
- caver.kas.wallet.getFeePayerList
GET /v2/feepayer
- caver.kas.wallet.createFeePayer
- For more scenarios in detail, refer to KAS Docs.
- Functions to use fee payer via KAS Wallet API.
- Supports for a new Key API function in KAS Wallet API.
- Function to delete a key in KAS Wallet API.
- caver.kas.wallet.deleteKey
DELETE /v2/key/{key-id}
- caver.kas.wallet.deleteKey
- For more scenarios in detail, refer to KAS Docs.
- Function to delete a key in KAS Wallet API.
- caver.kas.wallet provides a function that migrates the existing Klaytn accounts to the KAS Wallet API service.
- Adds new functions and query parameters to Token History API.
- Functions for integrated inquiry of tokens and contracts newly provided by KAS.
- caver.kas.wallet.getContractListByOwner
GET /v2/account/{address}/contract
- caver.kas.wallet.getTokenListByOwner
GET /v2/account/{address}/token
- caver.kas.wallet.getContractListByOwner
- KAS provides new query parameters.
- You can use
excludeZeroKlay
query parameter withcaver.kas.tokenHistory.getTransferHistory
. - You can use
fromOnly
,toOnly
andexcludeZeroKlay
query parameters withcaver.kas.tokenHistory.getTransferHistoryByAccount
.
- You can use
- For more scenarios in detail, refer to KAS Docs.
- Functions for integrated inquiry of tokens and contracts newly provided by KAS.
- Adds support for WebSocket provider with KAS Node API.
- KAS Node API service is now usable via WebSocket provider.
- Added a
ConfigOptions
class to provide various options for initializingCaverExtKAS
class.- Added a
useNodeAPIWithHttp
field to choose provider either Http or Websocket.
- Added a
- Added a new
CaverExtKAS
contstructor that requires aConfigOptions
instance as the last parameter to support websocket. - Added
initKASAPI
's overloading function that requires aConfigOptions
instance as the last parameter to support websocket. - Added
initNodeAPI
's overloading function that requiresfalse
as the last parameter to support websocket.
- Added a
- For more scenarios in detail, refer to KAS Docs.
- KAS Node API service is now usable via WebSocket provider.
Improvements
- Deleted the
krn
parameter to allow users to implement the function using the defaultkrn
in thecaver.kas.wallet.signMessage
. - Since KAS does not support querying the number of accounts by specifying the krn, the
krn
parameter is disabled in thecaver.kas.wallet.getAccountCountByKRN
function.
Release v1.4.0-rc.1
v1.4.0-rc.1 Release Notes
Breaking Change
- The
caver.kas.wallet.signMessage
does not supportkrn
parameter. This function has been changed to work using the KAS user's default krn.
New Features
- Adds support for KAS KIP-7 API.
- Functions to use the KIP-7 API service newly provided by KAS.
- caver.kas.kip7.deploy
POST /v1/contract
- caver.kas.kip7.getContract
GET /v1/contract/{contract-address-or-alias}
- caver.kas.kip7.getContractList
GET /v1/contract
- caver.kas.kip7.allowance
GET /v1/contract/{contract-address-or-alias}/account/{owner}/allowance/{spender}
- caver.kas.kip7.balance
GET /v1/contract/{contract-address-or-alias}/account/{owner}/balance
- caver.kas.kip7.approve
POST /v1/contract/{contract-address-or-alias}/approve
- caver.kas.kip7.transfer
POST /v1/contract/{contract-address-or-alias}/transfer
- caver.kas.kip7.transferFrom
POST /v1/contract/{contract-address-or-alias}/transfer-from
- caver.kas.kip7.mint
POST /v1/contract/{contract-address-or-alias}/mint
- caver.kas.kip7.burn
POST /v1/contract/{contract-address-or-alias}/burn
- caver.kas.kip7.burnFrom
POST /v1/contract/{contract-address-or-alias}/burn-from
- caver.kas.kip7.pause
POST /v1/contract/{contract-address-or-alias}/pause
- caver.kas.kip7.unpause
POST /v1/contract/{contract-address-or-alias}/unpause
- caver.kas.kip7.getDeployer
GET /v1/deployer/default
- caver.kas.kip7.deploy
- KAS KIP-7 API is available with caver.kas.kip7 by implementing caver.initKASAPI(chainId, accessKeyId, secretAccessKey) or caver.initKIP7API(chainId, accessKeyId, secretAccessKey, url). If query parameters are required when using the KIP-7 API, they can be used through the
KIP7QueryOptions
class. For more scenarios in detail, refer to KAS Docs.
- Functions to use the KIP-7 API service newly provided by KAS.
- Now supports new functions with KAS Wallet API.
- caver.kas.wallet provides a function that migrates the existing Klaytn accounts to the KAS Wallet API service.
- caver.kas.wallet.migrateAccounts migrates specific Klaytn accounts to KAS Wallet API service.
- Adds support for newly added API functions in KAS Wallet API.
- Functions to use fee payer via KAS Wallet API.
- caver.kas.wallet.createFeePayer
POST /v2/feepayer
- caver.kas.wallet.deleteFeePayer
DELETE /v2/feepayer/{address}
- caver.kas.wallet.getFeePayer
GET /v2/feepayer/{address}
- caver.kas.wallet.getFeePayerList
GET /v2/feepayer
- caver.kas.wallet.createFeePayer
- For more scenarios in detail, refer to KAS Docs.
- Functions to use fee payer via KAS Wallet API.
- Supports for a new Key API function in KAS Wallet API.
- Function to delete a key in KAS Wallet API.
- caver.kas.wallet.deleteKey
DELETE /v2/key/{key-id}
- caver.kas.wallet.deleteKey
- For more scenarios in detail, refer to KAS Docs.
- Function to delete a key in KAS Wallet API.
- caver.kas.wallet provides a function that migrates the existing Klaytn accounts to the KAS Wallet API service.
- Adds new functions and query parameters to Token History API.
- Functions for integrated inquiry of tokens and contracts newly provided by KAS.
- caver.kas.wallet.getContractListByOwner
GET /v2/account/{address}/contract
- caver.kas.wallet.getTokenListByOwner
GET /v2/account/{address}/token
- caver.kas.wallet.getContractListByOwner
- KAS provides new query parameters.
- You can use
excludeZeroKlay
query parameter withcaver.kas.tokenHistory.getTransferHistory
. - You can use
fromOnly
,toOnly
andexcludeZeroKlay
query parameters withcaver.kas.tokenHistory.getTransferHistoryByAccount
.
- You can use
- For more scenarios in detail, refer to KAS Docs.
- Functions for integrated inquiry of tokens and contracts newly provided by KAS.
- Adds support for WebSocket provider with KAS Node API.
- KAS Node API service is now usable via WebSocket provider.
- Added a
ConfigOptions
class to provide various options for initializingCaverExtKAS
class.- Added a
useNodeAPIWithHttp
field to choose provider either Http or Websocket.
- Added a
- Added a new
CaverExtKAS
contstructor that requires aConfigOptions
instance as the last parameter to support websocket. - Added
initKASAPI
's overloading function that requires aConfigOptions
instance as the last parameter to support websocket. - Added
initNodeAPI
's overloading function that requiresfalse
as the last parameter to support websocket.
- Added a
- For more scenarios in detail, refer to KAS Docs.
- KAS Node API service is now usable via WebSocket provider.
Improvements
- Deleted the
krn
parameter to allow users to implement the function using the defaultkrn
in thecaver.kas.wallet.signMessage
. - Since KAS does not support querying the number of accounts by specifying the krn, the
krn
parameter is disabled in thecaver.kas.wallet.getAccountCountByKRN
function.
Release v1.1.1
v1.1.1 Release Notes
Fixes
- Modified logic to check whether the account type is
AccountKeyWeightedMultiSig
. (#65).- Handled the case if the response of
getAccountKey()
returns null.
- Handled the case if the response of
- Modified
initKIP17API
that initializes the KIP17API function. (#71)- Modified KIP17 instance has null despite executing
initKIP17API
.
- Modified KIP17 instance has null despite executing
- Modified
registerAccounts
code example. (#70) - Modified Wallet and KIP17 API test code. (#78)
- Added an enough delay to submit transaction.
- Modified some test cases in Wallet API test code.
Others
v1.1.1-rc.3: Merge pull request #75 from sirano11/maven
add a nexus staging info.
Release v1.1.1-rc.2
v1.1.1-rc.2 Release Notes
Fixed
- Resolved a problem that when creating a CaverExtKAS instance, the KIP17 API instance was not set.(#71)
Improved
Release v1.1.1-rc.1
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
- caver.kas.kip17.deploy
- KAS KIP-17 API is available with
caver.kas.kip17
by implementingcaver.initKASAPI(chainId, accessKeyId, secretAccessKey)
orcaver.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.kip17 supports functions to use the KIP-17 API service newly provided by KAS.
-
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.createKeys
- caver.kas.wallet provides additional API to call contract.
- caver.kas.wallet.callContract
POST /v2/tx/contract/call
- caver.kas.wallet.callContract
- 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.
- status field is added in
- For more scenarios in detail, refer to KAS Docs.
- caver.kas.wallet additionally supports the Key API and Registration API provided in the KAS Wallet API service.
-
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}
- caver.kas.tokenHistory.getMTListByOwner
- For more scenarios in detail, refer to KAS Docs.
- caver.kas.tokenHistory additionally supports the API functions for KIP-37 Multi Token.
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.
- The
Release v1.0.2
v1.0.2 Release Notes
Highlights : Introducing KASWallet
KASWallet
allows you to use features (e.g., transaction signing, contract deployment, contract execution, etc) provided by caver-java with Klaytn accounts in KAS Wallet API.
KASWallet
has the following features:
- Creates and manages Klaytn Accounts in KAS Wallet API.
- Signs transaction instances using KAS Wallet API.
KASWallet
provides the same usability of Caver.wallet
in caver-java so that signing transactions is done as before.
In addition, if a CaverExtKAS
instance is passed as a parameter to the classes Contract
, KIP7
and KIP17
in caver-java, you can execute and deploy Contract
, KIP7
and KIP17
in the same manner as before except that KAS APIs are called internally.
Breaking Changes
From caver-java-ext-kas v1.0.2, the wallet
member variable in CaverExtKAS
, a KeyringContainer
instance previously, has been changed to a KASWallet
instance, a wallet that manages Klaytn accounts in KAS Wallet API.
If you want to use KeyringContainer
, an in-memory wallet of caver-java, please refer to KAS Docs.
New Features
- Implemented KASWallet to manage Klaytn accounts in KAS Wallet API.
- KASWallet provides the following methods.
- caver.wallet.generate
- caver.wallet.getAccount
- caver.wallet.isExisted
- caver.wallet.remove
- caver.wallet.disableAccount
- caver.wallet.enableAccount
- caver.wallet.sign
- caver.wallet.signAsFeePayer
- caver.wallet.signAsGlobalFeePayer
- The following packages can be performed with KASWallet of KAS SDK:
- caver.contract
- caver.kct.kip7
- caver.kct.kip17
- The transaction instance in caver-java can be signed by using
caver.wallet.sign()
orcaver.wallet.signAsFeePayer()
. - For more details of KASWallet, please refer to caver-java-ext-kas API Reference.
- KASWallet provides the following methods.
- KeyringContainer
- If you want to use KeyringContainer seperately in KAS SDK, please refer to KAS Docs.
Fixes
- Changed the default address from
0x
to0x0000000000000000000000000000000000000000
to reflect the caver-java change. (klaytn/caver-java#190).