Burn

Burn LTO. Annnnd it's gone...

JSON

{
  "type": 21,
  "version": 3,
  "id": "8M6dgn85eh3bsHrVhWng8FNaHBcHEJD4MPZ5ZzCciyon",
  "sender": "3Jq8mnhRquuXCiFUwTLZFVSzmQt3Fu6F7HQ",
  "senderKeyType": "ed25519",
  "senderPublicKey": "AJVNfYjTvDD2GWKPejHbKPLxdvwXjAnhJzo6KCv17nne",
  "fee": 100000000,
  "timestamp": 1647870282634,
  "amount": 100000000000,
  "proofs": [
    "49Y3FhLkE8gy7ryWZbxMgs2oWzkjE6qSj7cH1p9rmpnsMd1mMgTg9NynERLdtgWDiq57sDwr4gNUJoP9qYzidRPR"
  ]
}

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

#	Field Name	Type	Length
1	Transaction type	Byte (constant, value=21)	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	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.