2
1
My question comes from not understanding how BIP 144 works? Regarding the BIP what I ask is, whether legacy nodes support the new parser, so that they treat Segwit tranasctions as valid? There it is stated:
Parsers supporting this BIP will be able to distinguish between the old serialization format (without the witness) and this one. The marker byte is set to zero so that this structure will never parse as a valid transaction in a parser that does not support this BIP. If parsing were to succeed, such a transaction would contain no inputs and a single output.
In relation to my main question, I could not understand how legacy nodes treat the witness fields of a segwit transaction?
But a segwit transaction is sent with the new serialisation, how do they parse it? How do they "skip" the witness part ? I hope my question makes sense. – Ifo0 – 2018-08-01T20:07:29.020
Yes, it makes sense, it may just be, that you think the client requests a tx... before doing so, there is a handshake, which tells about the capabilities of a node. Based on this the nodes get or do not get segwit data. See a discussion held here: https://bitcointalk.org/index.php?topic=1682183.msg21389041#msg21389041
– pebwindkraft – 2018-08-01T23:02:47.927Perfect! Now it makes sense, I was looking exactly for this in-depth explanation we get in the forum! Thank you @pebwindkraft ! – Ifo0 – 2018-08-05T10:25:57.503