Continuation Transaction Binary Format

Learn more about Continuation transaction.

The Continuation transaction is added in node version 1.3.0 and enabled with feature #16 “Ride V5, dApp-to-dApp invocations, Continuations”. Versions 1.3.x are now available for Stagenet only.

Binary format is defined in transaction.proto (opens new window) protobuf scheme. The fields that are common to all types of transactions are described in the Transaction Binary Format article.

Please note: a Continuation transaction is not sent on behalf of any account. It does not have senderPublicKey, proofs, timestamp, and feeAssetId fields.

message ContinuationTransactionData {
    bytes invoke_transaction_id = 1;
    int32 nonce = 2;
};

Field	Size	Description
invoke_transaction_id	32 bytes	ID of the Invoke Script transaction that starts the computation sequence
nonce	4 bytes	Number that is unique in the computation sequence. It is used to calculate the transaction ID