📅 Original date posted:2015-05-16
📝 Original message:On Sat, May 16, 2015 at 4:58 AM, Stephen <stephencalebmorse at gmail.com>
wrote:
> We should make sure to consider how BIP34 affects normalized transaction
> ids, since the height of the block is included in the scriptSig ensuring
> that the txid will be different. We wouldn't want to enable replay attacks
> in the form of spending coinbase outputs in the same way they were spent
> from a previous block.
>
> So maybe normalized txids should strip the scriptSigs of all transactions
> except for coinbase transactions? This seems to make sense, since coinbase
> transactions are inherently not malleable anyway.
>
That is a good point. Since the point is the change is to use good
practice right back until the genesis block, maybe the scriptSig for
coinbases could be replaced by the height expressed as a varint. That
means that all coinbases get a unique normalized txid. The coinbases with
duplicate txids still wouldn't be spendable though.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150516/3f138563/attachment.html>;
Tier Nolan [ARCHIVE] /
npub1g6…sl5wd
2023-06-07 15:35:15
in reply to nevent1q…2xs2
Author Public Key
npub1g6vxlp4e0nyhs2dqxxcryztyf5f5hyuaq93nw4r87zcnv0sdsa0qqsl5wdPublished at
2023-06-07 15:35:15Event JSON
{
"id": "64cfab4bcc14976644a1a4365801768ec60faa7011831e96f63cee8b5a2ce349",
"pubkey": "46986f86b97cc97829a031b03209644d134b939d0163375467f0b1363e0d875e",
"created_at": 1686152115,
"kind": 1,
"tags": [
[
"e",
"d4296383f49c1a9f727ee325cad107826210d0f0a44bfb48a025773c99b7560e",
"",
"root"
],
[
"e",
"f5017ee20f3bae309141622cc101311e4b1a947b8a1f604d5f0b03795370542f",
"",
"reply"
],
[
"p",
"10238a6d0c6848c1acb963573a9db5f379583e293364361bd86476b496370490"
]
],
"content": "📅 Original date posted:2015-05-16\n📝 Original message:On Sat, May 16, 2015 at 4:58 AM, Stephen \u003cstephencalebmorse at gmail.com\u003e\nwrote:\n\n\u003e We should make sure to consider how BIP34 affects normalized transaction\n\u003e ids, since the height of the block is included in the scriptSig ensuring\n\u003e that the txid will be different. We wouldn't want to enable replay attacks\n\u003e in the form of spending coinbase outputs in the same way they were spent\n\u003e from a previous block.\n\u003e\n\u003e So maybe normalized txids should strip the scriptSigs of all transactions\n\u003e except for coinbase transactions? This seems to make sense, since coinbase\n\u003e transactions are inherently not malleable anyway.\n\u003e\n\nThat is a good point. Since the point is the change is to use good\npractice right back until the genesis block, maybe the scriptSig for\ncoinbases could be replaced by the height expressed as a varint. That\nmeans that all coinbases get a unique normalized txid. The coinbases with\nduplicate txids still wouldn't be spendable though.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150516/3f138563/attachment.html\u003e",
"sig": "426d9cdff0a3b9a1e918da9224f256f1a5bfe94cf6ca5271a118bce22ab057b106c88061c5a0a9cfc6d56f21338bbaf6e1f88b0241998c98ca232cde107ad952"
}