Lease Cancel Transaction Binary Format

Learn more about Lease Cancel transaction.

Version 3

Binary format of version 3 is defined in transaction.proto protobuf scheme. The fields that are common to all types of transactions are described in the Transaction Binary Format article.

Version 3 is enabled by feature #15 “Ride V4, VRF, Protobuf, Failed transactions”.

message LeaseCancelTransactionData {
    bytes lease_id = 1;
};

Field	Size	Description
lease_id	32 bytes	Lease ID

Version 2

#	Field	JSON field name	Field type	Field size in bytes	Comment
1	Version flag		Byte	1	Indicates the transaction version is 2 or higher. Value must be 0
2	Transaction type ID	type	Byte	1	Value must be 9
3	Transaction version	version	Byte	1	Value must be 2
4	Chain ID	chainId	Byte	1	87 — for Mainnet 84 — for Testnet 83 — for Stagenet
5	Public key of the transaction sender	senderPublicKey	Array[Byte]	32
6	Transaction fee	fee	Long	8
7	Transaction timestamp	timestamp	Long	8
8	Lease ID		Array[Byte]	32
9	Transaction proofs	proofs	See Transaction Proofs Binary Format	S	If the array is empty, then S = 3. If the array is not empty, then S = 3 + 2 × N + 64 × N, where N is the number of proofs in the array. The maximum number of proofs in the array is 8. The size of each proof is 64 bytes

The fields numbered in bold are the transaction body bytes.

JSON Representation of Transaction

See the example in Node API.

Version 1

Field order number	Field	Field type	Field size in bytes	Comment
1	Transaction type ID	Byte	1	Value must be 9
2	Public key of the transaction sender	Array[Byte]	32
3	Transaction fee	Long	8
4	Transaction timestamp	Long	8
5	Lease ID	Array[Byte]	32
6	Transaction signature	Array[Byte]	64

The fields numbered in bold are the transaction body bytes.