{"type":"rich","version":"1.0","author_name":"npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwet","author_url":"https://nostr.ae/npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwet","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2017-11-20\n📝 Original message:On Mon, Nov 20, 2017 at 5:24 PM, Praveen Baratam via bitcoin-dev\n\u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e Bitcoin Noob here. Please forgive my ignorance.\n\u003e\n\u003e From what I understand, in SegWit, the transaction needs to be serialized\n\u003e into a data structure that is different from the current one where\n\u003e signatures are separated from the rest of the transaction data.\n\u003e\n\u003e Why change the format at all? Why cant we just compute the Transaction ID\n\u003e the same way the hash for signing the transaction is computed?\n\nThat is effectively what segwit does, upto engineering minutia and\ncompatibility details.\n\nSegwit does not serialize transactions in to a data structure where\nsignatures are separated from the rest of the transaction data; this\nis a misunderstanding.  The \"segregated\" refers to them being excluded\nfrom the TXID.   The serialization of segwit on the p2p network in\ntransactions and in blocks encodes the witness field inside the\ntransactions, immediately prior to the nlocktime field."}