Transfer

The transfer transaction allows the sender to transfer LTO tokens to the recipient.

{
  "type": 4,
  "version": 3,
  "id": "5a1ZVJTu8Y7mPA6BbkvGdfmbjvz9YSppQXPnb5MxihV5",
  "sender": "3N9ChkxWXqgdWLLErWFrSwjqARB6NtYsvZh",
  "senderKeyType": "ed25519",
  "senderPublicKey": "9NFb1rvMyr1k8f3wu3UP1RaEGsozBt9gF2CmPMGGA42m",
  "fee": 100000000,
  "timestamp": 1609639213556,
  "amount": 100000000000,
  "recipient": "3NBcx7AQqDopBj3WfwCVARNYuZyt1L9xEVM",
  "attachment": "9Ajdvzr",
  "proofs": [
    "3ftQ2ArKKXw655WdHy2TK1MGXeyzKRqMQYwFidekkyxLpzFGsTziSFsbM5RCFxrn32EzisMgPWtQVQ4e5UqKUcES"
  ],
  "height": 1212761
}

• id and height should be omitted when broadcasting. These fields are set by the node.

• Binary strings (including attachment) are base58 encoded.

• timestamp is in microseconds since epoch.

• fee and amount include 8 digits, so LTO * 10^8

Binary schema

The binary data structure of the unsigned transaction.

V3 (current)

#	Field Name	Type	Length
1	Transaction type	Byte (constant, value=4)	1
2	Version	Byte (constant, value=3)	1
3	Network id	Byte	1
4	Timestamp	Long	8
5	Sender's key type	KeyType (Byte)	1
6	Sender's public key	PublicKey (Array[Byte])	32 | 33
7	Fee	Long	8
8	Recipient	Address (Array[Byte])	26
9	Amount	Long	8
10	Attachment length (N)	Short	2
11	Attachment	Array[Byte]	N

• Network id can be obtained by taking the 2nd byte from the sender address.

• Each key type has a numeric id in addition to the reference from the JSON.

• Integers (short, int, long) have a big endian byte order.

V2

V1