user133967: If i'm correct, i am pretty sure that signature data such as the scriptsigsize
and scriptsig is stored outside the Tx_Data of a Bitcoin transaction. But then where is it stored? Is it in the block or is it somehow connected to the transaction-data?
Also, how is it possible that this Bitcoin included in the transaction can be unlocked if the signature data is external from the transaction?

user208: From the perspective of new post-segwit nodes, the witness data is part of the transaction data. It is serialized in a new field, after all the transaction outputs, before the locktime field.
However, this field is stripped out before relaying to old pre-segwit nodes. So from the perspective of those old nodes, the witness data isn't just external - it just doesn't exist. They don't care about the witness data, as to them, these outputs are the equivalent of "True": anyone can spend them without any signatures.

133967: <p>If i'm correct, i am pretty sure that signature data such as the <code>scriptsigsize</code>
and <code>scriptsig</code> is stored outside the Tx_Data of a Bitcoin transaction. But then where is it stored? Is it in the block or is it somehow connected to the transaction-data?</p>
<p>Also, how is it possible that this Bitcoin included in the transaction can be unlocked if the signature data is external from the transaction?</p>
 208: <p>From the perspective of new post-segwit nodes, the witness data <strong>is</strong> part of the transaction data. It is serialized in a new field, after all the transaction outputs, before the locktime field.</p>
<p>However, this field is stripped out before relaying to old pre-segwit nodes. So from the perspective of those old nodes, the witness data isn't just external - it just doesn't exist. They don't care about the witness data, as to them, these outputs are the equivalent of &quot;True&quot;: anyone can spend them without any signatures.</p>
