Interface TransferAssetArgs

The argument object for AssetApi.transferAsset

interface TransferAssetArgs {
    amountPlanck?: string;
    assetId: string;
    attachment?: Attachment;
    deadline?: number;
    feePlanck: string;
    quantity: string | number;
    recipientId: string;
    recipientPublicKey?: string;
    referencedTransactionFullHash?: string;
    senderPrivateKey?: string;
    senderPublicKey: string;
    skipAdditionalSecurityCheck?: boolean;
}

Hierarchy

  • DefaultSendArgs
    • TransferAssetArgs

Properties

amountPlanck?: string

The amount to be sent as Planck value

assetId: string

The assets id to be transferred

attachment?: Attachment

An optional attachment

deadline?: number

The deadline when after how many minutes the transaction will be discarded, if it was not processed, e.g. due to very low fee

feePlanck: string

The fee expressed in Planck

It's recommended to use util.Amount

quantity: string | number

The amount of assets to be transferred (take the decimals into consideration) If you set decimals to 4 and want to have 100 full assets, you need to set this value to 1000000

recipientId: string

The id of the recipient

recipientPublicKey?: string

The optional recipients public key in hex format.

referencedTransactionFullHash?: string

Using this field allows to make a transaction dependent on other transactions.

senderPrivateKey?: string

The senders private key, i.e. the crypto.SignKeys.signPrivateKey If the private key is not given, then the transaction method will return the unsigned byte string. The transaction won't be processed until the unsigned bytes are being signed and broadcasted using TransactionApi.signAndBroadcastTransaction

senderPublicKey: string

The senders public key, i.e. the crypto.SignKeys.publicKey

skipAdditionalSecurityCheck?: boolean

Setting this option to true, skips the additional security check, i.e. the verification of the unsigned transaction bytes, which detects tampered node responses. By default, the option is false. Usually, you won't use this option, but can be useful when a method cannot be verified, because the verification is not implemented yet.