description |
---|
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
}
{% hint style="info" %}
id
andheight
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
andamount
include 8 digits, soLTO * 10^8
{% endhint %}
The binary data structure of the unsigned transaction.
{% tabs %} {% tab title="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 |
{% hint style="info" %}
- 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. {% endhint %} {% endtab %}
{% tab title="V2" %}
# | Field Name | Type | Length |
---|---|---|---|
1 | Transaction type | Byte (constant, value=4) | 1 |
2 | Version | Byte (constant, value=2) | 1 |
3 | Sender's public key | PublicKey (Array[Byte]) | 32 |
4 | Timestamp | Long | 8 |
5 | Amount | Long | 8 |
6 | Fee | Long | 8 |
7 | Recipient | Address (Array[Byte]) | 26 |
8 | Attachment length (N) | Short | 2 |
9 | Attachment | Array[Byte] | N |
{% hint style="info" %} Integers (short, int, long) have a big endian byte order. {% endhint %} {% endtab %}
{% tab title="V1" %}
# | Field Name | Type | Length |
---|---|---|---|
1 | Transaction type | Byte (constant, value=4) | 1 |
2 | Sender's public key | PublicKey (Array[Byte]) | 32 |
3 | Timestamp | Long | 8 |
4 | Amount | Long | 8 |
5 | Fee | Long | 8 |
6 | Recipient | Address (Array[Byte]) | 26 |
7 | Attachment length (N) | Short | 2 |
8 | Attachment | Array[Byte] | N |
{% hint style="info" %} Integers (short, int, long) have a big endian byte order. {% endhint %} {% endtab %} {% endtabs %}