Initializes a new instance of the SubTransaction class.
Data structure that contains all the elements of the sub transaction.
Collection of digital signatures that are attached to the sub transaction to prove that it has been authorized by the appropriate parties, the witness set also contain all required information to satisfy native or plutus script execution requirements, such as Datums, Redeemers and the script itself.
Optional auxiliaryData: Serialization.AuxiliaryDataAdditional information that can be attached to the sub transaction to provide more context or information about it.
Private #auxiliaryPrivate #bodyPrivate #originalPrivate #witnessGets the sub transaction Auxiliary data.
A clone of the sub transaction Auxiliary data (or undefined if the sub transaction doesnt have auxiliary data).
Data structure that contains all key elements of the sub transaction.
A deep clone of the sub transaction body.
Performs a deep clone of the sub transaction object.
Computes the transaction id for this sub transaction.
Sub transaction ids follow the top level transaction id convention: the blake2b-256 hash of the body bytes.
Sets the sub transaction auxiliary data.
The auxiliary is additional information that can be attached to the sub transaction to provide more context or information about it.
Optional auxiliaryData: Serialization.AuxiliaryDataThe auxiliary data to be set.
Sets the sub transaction body.
The sub transaction body.
Sets the witness set of the sub transaction.
A deep clone of the witness set in this sub transaction.
Creates a Core SubTransaction object from the current SubTransaction object.
The Core SubTransaction object.
Collection of digital signatures that are attached to the sub transaction to prove that it has been authorized by the appropriate parties, the witness set also contain all required information to satisfy native or plutus script execution requirements, such as Datums, Redeemers and the script itself.
A deep clone of the sub transaction witness set.
Static fromDeserializes the SubTransaction from a CBOR byte array.
The frame must be exactly 3 elements. In particular the 4-element is_valid mempool form is rejected: the ledger only tolerates that grace-period frame for top level transactions, never for sub transactions.
The new SubTransaction instance.
The CBOR encoded SubTransaction object.
Optional options: Serialization.DeserializationOptionsDeserialization options. When strict is true, throws on unknown map keys
instead of skipping them.
Static fromCreates a SubTransaction object from the given Core SubTransaction object.
The core SubTransaction object.
Generated using TypeDoc
A Dijkstra sub transaction (CIP-0118 nested transactions).
A sub transaction is carried inside the enclosing top level transaction (body key 23) and is serialized as exactly three elements: its body, its witness set and its nullable auxiliary data. Unlike top level transactions there is no is_valid flag, not even the grace-period 4-element mempool form - the enclosing transaction's flag covers the whole batch.
Sub transactions are identified by their own transaction id, derived exactly like a top level transaction id: the blake2b-256 hash of the body bytes.