Lease

The lease transaction leases an amount of tokens to a node for staking.

{
  "type": 8,
  "version": 3,
  "id": "6XmeG7SRWiw8pD6Uad6D9AAaY354v5TV6AJMhPpHMkqy",
  "sender": "3JorA3ddE7i6fhgBjSuW6jNTYS8D4EZUzio",
  "senderKeyType": "ed25519",
  "senderPublicKey": "AWwAdRHFmSqTCMHJ346wFSbJUsGUzQYCzuqXWgaT4gL6",
  "fee": 100000000,
  "timestamp": 1607010190710,
  "proofs": [
    "2BK6wTH75N78ixT273kArQxTo6NHvSVWQvtubZ5PTVdybcwomoUFjcYdfxqY6Xk7BpePjDbyr9aWdE5iZxQLq63J"
  ],
  "amount": 553600000000,
  "recipient": "3JurbYJAuc8iMeujvS39L8cSv9kMfxDACYR",
  "height": 1012314
}

• 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 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=8)	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

• 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