1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1WDdN0-0003RT-R5
for bitcoin-development@lists.sourceforge.net;
Wed, 12 Feb 2014 17:13:10 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.212.177 as permitted sender)
client-ip=209.85.212.177; envelope-from=jgarzik@bitpay.com;
helo=mail-wi0-f177.google.com;
Received: from mail-wi0-f177.google.com ([209.85.212.177])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WDdMz-00043b-Q7
for bitcoin-development@lists.sourceforge.net;
Wed, 12 Feb 2014 17:13:10 +0000
Received: by mail-wi0-f177.google.com with SMTP id e4so7267901wiv.16
for <bitcoin-development@lists.sourceforge.net>;
Wed, 12 Feb 2014 09:13:03 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type
:content-transfer-encoding;
bh=GK+hrkNPVIzNk4QocCQtIv0PTTVX9V7QSI1WzC9Frdk=;
b=aEd0mPuNB4bA+NX9EgyMqOta3mFoOzSxGM/wxa2tMytcejoQInqLo6eoasSqiD5zUp
UX2Ov98+SPyWuV9VWwlzWsxrdLbRNzhainiTnoNmFHgdxc62wCUnY75lIZ1QEnKwzMQP
+kC59jFlKWbmRDe7rzTk8PrD3f0/tG2BK8kMpkFNDEyBMnbch8pThQYGw2y4+4X6jlfy
kjYEgA3wuLy00G0XzJjLgyL1BS68RZ8ucV3ViT24RicZuJEq26B/Pl5uJhQtesejoS9P
bt5+cXIqp0L9C/6FwcSKcc37b3lYm44qj0eDvmx97C+5xVwr/QYOgO/jMGgPDjtxslLd
p9dA==
X-Gm-Message-State: ALoCoQlSNP6pSpq1KtS+9A6gJ0WgENSPI4Mssg47ScD6+mDXfXqbHGezgq+/lc/TWAwLbn5yFm0m
MIME-Version: 1.0
X-Received: by 10.180.87.162 with SMTP id az2mr2904499wib.23.1392225183485;
Wed, 12 Feb 2014 09:13:03 -0800 (PST)
Received: by 10.194.82.197 with HTTP; Wed, 12 Feb 2014 09:13:03 -0800 (PST)
In-Reply-To: <CAH2=CKzNGN7mpe1NLtsLRNSszSD2ZNwjoAsaH40EvGtA5ezDeQ@mail.gmail.com>
References: <CAPg+sBgPG+2AMbEHSRQNFn6FikbRzxkWduj5MSZLz-O6Wh940w@mail.gmail.com>
<20140210030048.GB31925@savin>
<CAH2=CKzNGN7mpe1NLtsLRNSszSD2ZNwjoAsaH40EvGtA5ezDeQ@mail.gmail.com>
Date: Wed, 12 Feb 2014 12:13:03 -0500
Message-ID: <CAJHLa0P0M+DZ-NUzfwp7up==RXYOD8ZpRKEXckfTY5cMTUaSZQ@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
To: =?ISO-8859-1?Q?Rune_Kj=E6r_Svendsen?= <runesvend@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.6 (-)
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 SPF_PASS SPF: sender matches SPF record
-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
X-Headers-End: 1WDdMz-00043b-Q7
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] [RFC] [BIP proposal] Dealing with
malleability
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: Wed, 12 Feb 2014 17:13:11 -0000
On Wed, Feb 12, 2014 at 10:12 AM, Rune Kj=E6r Svendsen
<runesvend@gmail.com> wrote:
> Instead of trying to remove the possibility of transaction
> malleability, would it make sense to define a new, "canonical
> transaction hash/ID" (cTxID),
Yes, that is one proposal: https://github.com/sipa/bitcoin/commits/normtxi=
d
But it is not a complete solution for all transaction types.
--=20
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
