How to implement and deploy Smart Contracts with SDK system
KAP20 for SDK
Within the KAP20SDK contract, the functions approveBySDK and transferFromBySDK have been added. For the purpose of functioning as a User, i.e., the client-side User can approve or transferFrom with the SDK without the need to sign the message themselves. Send Transaction to Bitkub Chain instead as User.
For Example link
Constructor
_name
Name of your token
_symbol
Symbol of your token
_decimals
Decimal of your token
_kyc
0x0B80357691c27c0c9Ba25123F832190C0b86aCA1
_committee
0x5bcDFb971d6622eEf0bFcAf7EcB6120a822B1Cd3
_transferRouter
0xF2B8821FA1e5cE47A99bD67c9f9E1724e48FD680
_executorEnv
0x9D9815a91d7E1Cf47dd48838f21dc373F51DdD17
_acceptedKycLevel
4
_envId
ENV ID of your token
KAP721 for SDK
Within the KAP721SDK contract, the functions adminApproveBySDK, approveForAllBySDK, and transferFromBySDK have been added. For the purpose of functioning as a User, i.e., the client-side User can approve or transferFrom with the SDK without the need to sign the message themselves. Send Transaction to Bitkub Chain instead as User.
For Example link Constructor
_name
Name of your token
_symbol
Symbol of your token
_baseURI
baseURI of your token
_kyc
0x0B80357691c27c0c9Ba25123F832190C0b86aCA1
_committee
0x5bcDFb971d6622eEf0bFcAf7EcB6120a822B1Cd3
_transferRouter
0x217ee59291692B00Eb8377a293E98811FB18b0Ca
_executorEnv
0x9D9815a91d7E1Cf47dd48838f21dc373F51DdD17
_acceptedKycLevel
4
_envId
ENV ID of your token
Last updated