user88171: I have become fairly familiar with constructing raw transaction. One thing I can't understand is after a raw transaction comes back from a signing, it doesn't look like it conforms to the transaction formatting. I was wondering if there was a different specification for signed raw transactions vs unsigned as shown here
https://developer.bitcoin.org/reference/transactions.html
here is the original unsigned raw broken into its chunks

02000000 01
5aab7df5106f76ae87544058edf7768fcb4c8fcbe2906d7ef9721a261bf505d3
01000000 00 ffffffff 01 968601000000 00
00160014e874b2647cf1f47e7d360a0e9753045950910f8a 00000000

the following is a signed raw transaction. I can see the parts that were added but the 0001 specifically should have the first byte be none zero sense it is a compactSize type. The bold areas were the data that was added. Obviously the second long hex is the signature/unlocking script of sorts but I can't find where to decode that either in the docs.

02000000 0001 01
5aab7df5106f76ae87544058edf7768fcb4c8fcbe2906d7ef9721a261bf505d3
01000000 00 ffffffff 01 9686010000000000 16
0014e874b2647cf1f47e7d360a0e9753045950910f8a
02473044022049ea695e1e7454be2e365142faa8258b8f5ce58b2c9cd9474085ce23df1b7e220220349da1acb0327a5025a0ed85dd88e9628703ed4086f4f8f4ac9b3c020a855bce012103773c3298e0ab8b000b48691c9262e774376239e23069370509e643217062010f
00000000

Any help is greatly appreciated.

user208: What you're seeing is the extended transaction serialization format introduced in BIP144 (segregated witness). It adds a marker 0x0001 to indicate the presence of a witness after the version number, and a list of witness stack items after the transaction inputs.

88171: <p>I have become fairly familiar with constructing raw transaction. One thing I can't understand is after a raw transaction comes back from a signing, it doesn't look like it conforms to the transaction formatting. I was wondering if there was a different specification for signed raw transactions vs unsigned as shown here
<a href="https://developer.bitcoin.org/reference/transactions.html" rel="nofollow noreferrer">https://developer.bitcoin.org/reference/transactions.html</a>
here is the original unsigned raw broken into its chunks</p>
<blockquote>
<p>02000000 01
5aab7df5106f76ae87544058edf7768fcb4c8fcbe2906d7ef9721a261bf505d3
01000000 00 ffffffff 01 968601000000 00
00160014e874b2647cf1f47e7d360a0e9753045950910f8a 00000000</p>
</blockquote>
<p>the following is a signed raw transaction. I can see the parts that were added but the 0001 specifically should have the first byte be none zero sense it is a compactSize type. The bold areas were the data that was added. Obviously the second long hex is the signature/unlocking script of sorts but I can't find where to decode that either in the docs.</p>
<blockquote>
<p>02000000 <strong>0001</strong> 01
5aab7df5106f76ae87544058edf7768fcb4c8fcbe2906d7ef9721a261bf505d3
01000000 00 ffffffff 01 9686010000000000 16
0014e874b2647cf1f47e7d360a0e9753045950910f8a
<strong>02473044022049ea695e1e7454be2e365142faa8258b8f5ce58b2c9cd9474085ce23df1b7e220220349da1acb0327a5025a0ed85dd88e9628703ed4086f4f8f4ac9b3c020a855bce012103773c3298e0ab8b000b48691c9262e774376239e23069370509e643217062010f</strong>
00000000</p>
</blockquote>
<p>Any help is greatly appreciated.</p>
 208: <p>What you're seeing is the extended transaction serialization format introduced in BIP144 (segregated witness). It adds a marker 0x0001 to indicate the presence of a witness after the version number, and a list of witness stack items after the transaction inputs.</p>
