Sponsor Fee Transaction Binary Format

Learn more about sponsorship.

Version 2

Binary format of version 2 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 2 is added in node version 1.2.0 and becomes available after activation of feature #15 “Ride V4, VRF, Protobuf, Failed transactions”. Versions 1.2.x are currently available on Stagenet only.

message SponsorFeeTransactionData {
    Amount min_fee = 1;
};
message Amount {
    bytes asset_id = 1;
    int64 amount = 2;
};

Field	Size	Description
min_fee.asset_id	32 bytes	ID of asset
min_fee.amount	8 bytes	Amount of asset that is equivalent to 0.001 WAVES (100 000 WAVELET), specified in the minimum fraction (“cents”) of asset. See the Sponsored fee article

Version 1

Field order number	Field	JSON field name	Field type	Field size in bytes	Comment
1	Version flag		Byte	1	Indicates the transaction version is version 2 or higher. Value must be 0
2	Transaction type ID	type	Byte	1	Value must be 14
3	Transaction version	version	Byte	1	Value must be 1
4	Public key of the transaction sender	senderPublicKey	Array[Byte]	32
5	Token ID	assetId	Array[Byte]	32
6	Minimal sponsor token fee	minSponsoredAssetFee	Long	8
7	Transaction fee	fee	Long	8
8	Transaction timestamp	timestamp	Long	8
9	Transaction proofs	proofs	Proofs	S	If the array is empty, then S = 3. If the array is not empty, then S = 3 + 2 × N + (P1 + P2 + ... + Pn), where N is the number of proofs in the array, Pn is the size on N-th proof in bytes. The maximum number of proofs in the array is 8. The maximum size of each proof is 64 bytes

JSON Representation of Transaction

See the example in Node API.