📅 Original date posted:2017-11-20
📝 Original message:Hello Praveen
You're absolutely right. We could refer to transactions by the hash that gets signed.
However the way that bitcoin transactions reference each other has already been established to be hash of transaction+signature. Changing this would require a hard fork.
Segwit is the realization that this could be done as a soft fork if we simply extract the signature outside of what the old client considers a transaction. And into a new transaction format where we do exactly what you're describing.
In my opinion the way it originally worked with the sig inside the transaction was simply an oversight by satoshi. No different than a bug.
Cheers
Ariel Lorenzo-Luaces
On Nov 20, 2017, 9:29 AM, at 9:29 AM, Praveen Baratam via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> wrote:
>Bitcoin Noob here. Please forgive my ignorance.
>
>From what I understand, in SegWit, the transaction needs to be
>serialized
>into a data structure that is different from the current one where
>signatures are separated from the rest of the transaction data.
>
>Why change the format at all? Why cant we just compute the Transaction
>ID
>the same way the hash for signing the transaction is computed?
>
>--
>Dr. Praveen Baratam
>
>about.me <http://about.me/praveen.baratam>;
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>bitcoin-dev mailing list
>bitcoin-dev at lists.linuxfoundation.org
>https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20171120/292a25d9/attachment.html>;
Ariel Lorenzo-Luaces [ARCHIVE] /
npub1t5…vlpha
2023-06-07 18:07:49
in reply to nevent1q…3axu
Author Public Key
npub1t5mnh3ztdjmffuykas2g2ulx5y3tcv69t0qk0t0r4e3azxy3shfq0vlphaPublished at
2023-06-07 18:07:49Event JSON
{
"id": "230d7ed93bd59acc50163daa23e325b2f6b300d9b1207430b5edb52efdc51fd2",
"pubkey": "5d373bc44b6cb694f096ec148573e6a122bc33455bc167ade3ae63d1189185d2",
"created_at": 1686161269,
"kind": 1,
"tags": [
[
"e",
"eee7506507e946de4c59c91cb3baa47c489b31bb507a0da8ae8433013d8e1ac7",
"",
"root"
],
[
"e",
"6e000601db1161b09147508f6191b2db983f897891c762cb600f1a55e020faba",
"",
"reply"
],
[
"p",
"ac05a78bbf6404f2d73636d005183880f5ee97bf96418992be2ff07d86012d24"
]
],
"content": "📅 Original date posted:2017-11-20\n📝 Original message:Hello Praveen\n\nYou're absolutely right. We could refer to transactions by the hash that gets signed.\n\nHowever the way that bitcoin transactions reference each other has already been established to be hash of transaction+signature. Changing this would require a hard fork.\n\nSegwit is the realization that this could be done as a soft fork if we simply extract the signature outside of what the old client considers a transaction. And into a new transaction format where we do exactly what you're describing.\n\nIn my opinion the way it originally worked with the sig inside the transaction was simply an oversight by satoshi. No different than a bug.\n\nCheers\nAriel Lorenzo-Luaces\n\n\nOn Nov 20, 2017, 9:29 AM, at 9:29 AM, Praveen Baratam via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003eBitcoin Noob here. Please forgive my ignorance.\n\u003e\n\u003eFrom what I understand, in SegWit, the transaction needs to be\n\u003eserialized\n\u003einto a data structure that is different from the current one where\n\u003esignatures are separated from the rest of the transaction data.\n\u003e\n\u003eWhy change the format at all? Why cant we just compute the Transaction\n\u003eID\n\u003ethe same way the hash for signing the transaction is computed?\n\u003e\n\u003e-- \n\u003eDr. Praveen Baratam\n\u003e\n\u003eabout.me \u003chttp://about.me/praveen.baratam\u003e\n\u003e\n\u003e\n\u003e------------------------------------------------------------------------\n\u003e\n\u003e_______________________________________________\n\u003ebitcoin-dev mailing list\n\u003ebitcoin-dev at lists.linuxfoundation.org\n\u003ehttps://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20171120/292a25d9/attachment.html\u003e",
"sig": "2b0f9c42a3918df186a6856537e000a46e887d7a637ff62b53e925158d4160ae02450f5fbc1bac46975c58b104436d7b2775c342ff6252637be6f78485ee6505"
}