LTO Network
Search…
Sponsorship
Sponsor an account, offering to pay for all transaction fees for that account.
You should only sponsor an account you trust, and/or have a legally binding agreement with. A sponsored account holder can easily drain your account through spam transactions. If the account holder is running a node, he/she can claim part of the spend tokens as mining reward. Limit the amount of tokens on the sponsoring account, adding funds when necessary.

JSON

1
{
2
"type": 18,
3
"version": 3,
4
"id": "HtxiY9x8aVBDfPvEUifYZuBEDge5TCDDAtqRGBW8HDef",
5
"sender": "3NBcx7AQqDopBj3WfwCVARNYuZyt1L9xEVM",
6
"senderKeyType": "Ed25519",
7
"senderPublicKey": "7gghhSwKRvshZwwh6sG97mzo1qoFtHEQK7iM4vGcnEt7",
8
"recipient": "3N9ChkxWXqgdWLLErWFrSwjqARB6NtYsvZh",
9
"timestamp": 1610410901000,
10
"fee": 500000000,
11
"proofs": [
12
"QKef6R8LrMBupBF9Ry8zjFTu3mexC55J6XNofDDQEcJnZJsRjZPnAk6Yn2eiHkqqd2uSjB2r58fC8QVLaVegQEz"
13
],
14
"height": 1225821
15
}
Copied!
  • id and height should be omitted when broadcasting. These fields are set by the node.
  • Binary strings are base58 encoded.
  • timestamp is in microseconds since epoch.
  • fee includes 8 digits, so LTO * 10^8

Binary schema

The binary data structure of the unsigned transaction.
V3 (current)
V1
#
Field Name
Type
Length
1
Transaction type
Byte (constant, value=18)
1
2
Version
Byte (constant, value=3)
1
3
Chain 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
  • Chain 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.
#
Field Name
Type
Length
1
Transaction type
Byte (constant, value=18)
1
2
Version
Byte (constant, value=1)
1
3
Chain id
Byte
1
4
Sender's public key
PublicKey (Array[Byte])
32
5
Recipient
Address (Array[Byte])
26
6
Fee
Long
8
7
Timestamp
Long
8
  • Chain id can be obtained by taking the 2nd byte from the sender or recipient address.
  • Integers (short, int, long) have a big endian byte order.
Copy link