You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The current version for callContractMethod allows only SIGNA to be sent. If calls depend on sent tokens, this method cannot be used yet. Allowing token transfers to contract in combination with methods would simplify the usage
Describe the solution you'd like
Add optional assetId and quantity for as calling parameters
Describe alternatives you've considered
Current way to do is like this:
// generate the arguments stringconstmethodCall=generateMethodCall({methodHash: "99",methodArgs: [airdropTokenId],});// mount as attachmentconstattachment=newAttachmentMessage({message: methodCall,messageIsText: false,});// use transferAsset methodconst{ unsignedTransactionBytes }=awaitledger.asset.transferAsset({assetId: contractData.getPledgeTokenId(),quantity: quantity.getAtomic(),recipientId: this.contractId,amountPlanck: contractData.getActivationAmount().getPlanck(),feePlanck: fees.cheap.toString(10),senderPublicKey: this.getAccount().getPublicKey(),
attachment,});
Is your feature request related to a problem? Please describe.
The current version for
callContractMethod
allows only SIGNA to be sent. If calls depend on sent tokens, this method cannot be used yet. Allowing token transfers to contract in combination with methods would simplify the usageDescribe the solution you'd like
Add optional
assetId
andquantity
for as calling parametersDescribe alternatives you've considered
Current way to do is like this:
desired would be:
The text was updated successfully, but these errors were encountered: