The serialization of the output at the same index as this input (A.K.A.
hashOutputs with SIGHASH_SINGLE
) – only used if SINGLE
is set.
The encoded script currently being executed, beginning at the
lastCodeSeparator
.
Optional
forkWhile a bitcoin-encoded signature only includes a single byte to encode the signing serialization type, a 3-byte forkId can be appended to provide replay-protection between different forks. (See Bitcoin Cash's Replay Protected Sighash spec for details.)
The locktime of the transaction.
The index of the outpoint being spent in outpointTransactionHash
.
The big-endian (standard) transaction hash of the outpoint being spent.
The encoded token prefix of the output being spent (see encodeTokenPrefix).
If the output includes no tokens, a zero-length Uint8Array.
The 8-byte Uint64LE
-encoded value of the outpoint in satoshis (see
bigIntToBinUint64LE).
The sequence number of the input (A.K.A. nSequence
).
The signing serialization type of the signature (A.K.A. sighash
type).
The serialization of all input outpoints (A.K.A. hashPrevouts) –
used if ANYONECANPAY
is not set.
The serialization of output amounts and locking bytecode values (A.K.A.
hashOutputs with SIGHASH_ALL
) – only used if ALL
is set.
The serialization of all input sequence numbers. (A.K.A.
hashSequence) – used if none of ANYONECANPAY
, SINGLE
, or
NONE
are set.
The signing serialization of all UTXOs spent by the transaction's inputs (concatenated in input order).
The version number of the transaction.
Generated using TypeDoc
Encode the signature-protected properties of a transaction following the algorithm required by the
signingSerializationType
of a signature.Note: When validating transactions with multiple signatures, performance-critical applications should use a memoized sha256 implementation to avoid re-computing hashes.