The recipient is the address of the account that receives the transfer transaction.
It is possible to send mosaics to any valid address, even if the address has not previously participated in any transaction.
If nobody owns the private key of the recipient’s account, the funds are most likely lost forever.
A mosaic could be a token, but it could also be more specialized assets such as reward points, shares of stock, signatures, status flags, votes or even other currencies.
You can send a combination of different mosaics in the same transaction.
A transfer transaction can hold a message up to
1023 characters in length, making them suitable for timestamping data permanently on the blockchain.
The messages attached are visible by default to all network participants.
Encrypted messages are only accessible by the sender and the recipient.
Sirius Chain uses Bouncy Castle’s AES block cipher implementation in CBC mode to encrypt and decrypt messages.
The client-side handles the encryption and decryption of the message. You can find under the
crypto module how to encode and decode encrypted messages, but we recommend you to use the available SDK public methods instead.
How to transfer mosaics and messages between two accounts.
How to ensure a transaction gets included in the blockchain after being announced.
Send an enctypted message that only can be read by the recipient account.
Configuration parameters are editable . Public network configuration may differ.
Entity type: 0x4154
|recipient||25 bytes (binary)||The address of the recipient account.|
|messageSize||uint16||The size of the attached message.|
|mosaicsCount||uint8||The number of attached mosaics.|
|message||array(byte, messageSize)||The message type (0) and a payload of up to |
|mosaics||array(UnresolvedMosaic, mosaicsCount)||The different mosaic to be sent.|