diff options
author | Tier Nolan <tier.nolan@gmail.com> | 2015-05-16 11:52:34 +0100 |
---|---|---|
committer | bitcoindev <bitcoindev@gnusha.org> | 2015-05-16 10:52:40 +0000 |
commit | 9b3be56dcce5a1330ab5ae16903f6762d10fa158 (patch) | |
tree | 309e38a4e86ea063ca8a09934c8ecf5f9af29613 | |
parent | 9b386bcf0e58407df81f8d27e8e9fac4ffe1ce90 (diff) | |
download | pi-bitcoindev-9b3be56dcce5a1330ab5ae16903f6762d10fa158.tar.gz pi-bitcoindev-9b3be56dcce5a1330ab5ae16903f6762d10fa158.zip |
Re: [Bitcoin-development] [BIP] Normalized Transaction IDs
-rw-r--r-- | 58/17df57be080e51467f65d4128f33cfc6e2c932 | 114 |
1 files changed, 114 insertions, 0 deletions
diff --git a/58/17df57be080e51467f65d4128f33cfc6e2c932 b/58/17df57be080e51467f65d4128f33cfc6e2c932 new file mode 100644 index 000000000..132868c2d --- /dev/null +++ b/58/17df57be080e51467f65d4128f33cfc6e2c932 @@ -0,0 +1,114 @@ +Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] + helo=mx.sourceforge.net) + by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <tier.nolan@gmail.com>) id 1YtZhw-0002BK-Jn + for bitcoin-development@lists.sourceforge.net; + Sat, 16 May 2015 10:52:40 +0000 +Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com + designates 209.85.192.48 as permitted sender) + client-ip=209.85.192.48; envelope-from=tier.nolan@gmail.com; + helo=mail-qg0-f48.google.com; +Received: from mail-qg0-f48.google.com ([209.85.192.48]) + by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) + (Exim 4.76) id 1YtZhv-0007hP-QR + for bitcoin-development@lists.sourceforge.net; + Sat, 16 May 2015 10:52:40 +0000 +Received: by qgew3 with SMTP id w3so22156602qge.2 + for <bitcoin-development@lists.sourceforge.net>; + Sat, 16 May 2015 03:52:34 -0700 (PDT) +MIME-Version: 1.0 +X-Received: by 10.229.16.69 with SMTP id n5mr18575616qca.25.1431773554435; + Sat, 16 May 2015 03:52:34 -0700 (PDT) +Received: by 10.140.85.241 with HTTP; Sat, 16 May 2015 03:52:34 -0700 (PDT) +In-Reply-To: <AC0B3BAC-0934-46A3-B29A-F74238616F72@gmail.com> +References: <CALxbBHUnt7ToVK9reH6W6uT4HV=7NbxGHyNWWa-OEHg+Z1+qOg@mail.gmail.com> + <5555C26F.7080706@sky-ip.org> + <AC0B3BAC-0934-46A3-B29A-F74238616F72@gmail.com> +Date: Sat, 16 May 2015 11:52:34 +0100 +Message-ID: <CAE-z3OVNUyEwryKyAYvwokFdY6a8v7uDVRgnxGG7oSk29j86GA@mail.gmail.com> +From: Tier Nolan <tier.nolan@gmail.com> +Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net> +Content-Type: multipart/alternative; boundary=001a1133e3f61c6c3b051630c248 +X-Spam-Score: 2.3 (++) +X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. + See http://spamassassin.org/tag/ for more details. + -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for + sender-domain + 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider + (tier.nolan[at]gmail.com) + -0.0 SPF_PASS SPF: sender matches SPF record + 1.2 MISSING_HEADERS Missing To: header + 1.0 HTML_MESSAGE BODY: HTML included in message + -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from + author's domain + 0.1 DKIM_SIGNED Message has a DKIM or DK signature, + not necessarily valid + -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature + 1.9 MALFORMED_FREEMAIL Bad headers on message from free email service + -0.1 AWL AWL: Adjusted score from AWL reputation of From: address +X-Headers-End: 1YtZhv-0007hP-QR +Subject: Re: [Bitcoin-development] [BIP] Normalized Transaction IDs +X-BeenThere: bitcoin-development@lists.sourceforge.net +X-Mailman-Version: 2.1.9 +Precedence: list +List-Id: <bitcoin-development.lists.sourceforge.net> +List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> +List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> +List-Post: <mailto:bitcoin-development@lists.sourceforge.net> +List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> +List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> +X-List-Received-Date: Sat, 16 May 2015 10:52:40 -0000 + +--001a1133e3f61c6c3b051630c248 +Content-Type: text/plain; charset=UTF-8 + +On Sat, May 16, 2015 at 4:58 AM, Stephen <stephencalebmorse@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. + +--001a1133e3f61c6c3b051630c248 +Content-Type: text/html; charset=UTF-8 +Content-Transfer-Encoding: quoted-printable + +<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo= +te">On Sat, May 16, 2015 at 4:58 AM, Stephen <span dir=3D"ltr"><<a href= +=3D"mailto:stephencalebmorse@gmail.com" target=3D"_blank">stephencalebmorse= +@gmail.com</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style= +=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">We shoul= +d make sure to consider how BIP34 affects normalized transaction ids, since= + the height of the block is included in the scriptSig ensuring that the txi= +d will be different. We wouldn't want to enable replay attacks in the f= +orm of spending coinbase outputs in the same way they were spent from a pre= +vious block.<br> +<br> +So maybe normalized txids should strip the scriptSigs of all transactions e= +xcept for coinbase transactions? This seems to make sense, since coinbase t= +ransactions are inherently not malleable anyway.<br></blockquote><div><br><= +/div><div>That is a good point.=C2=A0 Since the point is the change is to u= +se good practice right back until the genesis block, maybe the scriptSig fo= +r coinbases could be replaced by the height expressed as a varint.=C2=A0 Th= +at means that all coinbases get a unique normalized txid.=C2=A0 The coinbas= +es with duplicate txids still wouldn't be spendable though.<br></div></= +div></div></div> + +--001a1133e3f61c6c3b051630c248-- + + |