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
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <robbak@robbak.com>) id 1Uei1W-0001kE-Qy
for bitcoin-development@lists.sourceforge.net;
Tue, 21 May 2013 08:34:22 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of robbak.com
designates 209.85.128.178 as permitted sender)
client-ip=209.85.128.178; envelope-from=robbak@robbak.com;
helo=mail-ve0-f178.google.com;
Received: from mail-ve0-f178.google.com ([209.85.128.178])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Uei1V-0000wg-Pq
for bitcoin-development@lists.sourceforge.net;
Tue, 21 May 2013 08:34:22 +0000
Received: by mail-ve0-f178.google.com with SMTP id d10so230033vea.37
for <bitcoin-development@lists.sourceforge.net>;
Tue, 21 May 2013 01:34:16 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type:x-gm-message-state;
bh=M7OQbFXdu04UkGuxe6lxGyGk0ReWrj6mSwlEoyp8PR8=;
b=ZIOat5GNRjUsH5GHRij9UjvgZ59+Ox0w3EIagJr+enEZbm5SW9LlVRgTTldA9MLK02
kS7Ms6sk0GX56DTrH5kmPpnvM9KjCtuE2JbR+Z3CYMUOIDT/iHUwAbFBINalKY+Bp7mx
lDMA2fe5yeRoiY6PySEnB3ffOqZj9PIVoRd2iCCOy9YpR23TPiUUiu/GPHhvJFSp47K5
7dHxtV4QHo4csjSYem9H8/CSuQ1k9v0XkP0IknKAALigqMKQvEu3Um1WpZpQDS/28wo6
dsAOSQ1J3vDCtqKU6AcLhlntzHWPJlzrJXUB+IOc3g/M99C903EHQiq17yUSV6vOfMSK
/czQ==
MIME-Version: 1.0
X-Received: by 10.52.95.227 with SMTP id dn3mr373643vdb.111.1369123685110;
Tue, 21 May 2013 01:08:05 -0700 (PDT)
Received: by 10.52.88.172 with HTTP; Tue, 21 May 2013 01:08:04 -0700 (PDT)
In-Reply-To: <CAAS2fgSfbKGp5Qe4_RQeSvU0Ay-=m3CncaiQ5LLrMBtx0z5Pmg@mail.gmail.com>
References: <519AC3A8.1020306@quinnharris.me>
<CA+i0-i_+Tes+ePRqmDGEXDQ_L=S5y8gHBKk77zaLgTGOS3OMyA@mail.gmail.com>
<CAPg+sBjmXyLkgfwzC8h+ZFkmyUf6nzbGo0oAWR9nsJOTOfOXEg@mail.gmail.com>
<CAAS2fgRCpXUgw=GpE9_AcTgWcdCaDC6_16Xp5+oOZC0_1xmf-w@mail.gmail.com>
<CABsx9T1nqGCL00Hmq11srMU-n_KVYm2t-EjsBkWBtf699AECwA@mail.gmail.com>
<CAAS2fgSfbKGp5Qe4_RQeSvU0Ay-=m3CncaiQ5LLrMBtx0z5Pmg@mail.gmail.com>
Date: Tue, 21 May 2013 18:08:04 +1000
Message-ID: <CA+i0-i8R7oVfFnrcsdZ2JbR_4q8H9O6aTnCV4MwTi=VdBnQb6g@mail.gmail.com>
From: Robert Backhaus <robbak@robbak.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=20cf307d04aee7d79204dd35f227
X-Gm-Message-State: ALoCoQmKwnNpNrXOgtoWXXdBq1sQVGcOsORY1y9Kl4fs4iEZlwfKQHn/mAm2eB29w0MCvkB3/sL0
X-Spam-Score: -0.5 (/)
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
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1Uei1V-0000wg-Pq
Subject: Re: [Bitcoin-development] Double Spend Notification
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: Tue, 21 May 2013 08:34:23 -0000
--20cf307d04aee7d79204dd35f227
Content-Type: text/plain; charset=ISO-8859-1
Not at all - ACK from me, fwiw. Any attempt at a double spend should be
shouted from the housetops.
What Miners should do with that is still up for debate, it seems. My
opinion is that they should hold on and attempt to confirm the first,
letting it go only if a conflicting transaction is mined elsewhere. (Let
your Yes mean Yes...) But I understand the contrary arguments.
On 21 May 2013 17:04, Gregory Maxwell <gmaxwell@gmail.com> wrote:
> On Mon, May 20, 2013 at 9:39 PM, Gavin Andresen <gavinandresen@gmail.com>
> wrote:
> > I'm very much in favor of double-spend propagation across the network.
>
> Absolutely.
>
> (to the list:) Is there anyone who is not? (assuming that it doesn't
> allow arbitrary traffic multiplication, which is easily solved)
>
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--20cf307d04aee7d79204dd35f227
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Not at all - ACK from me, fwiw. Any attempt at a double sp=
end should be shouted from the housetops.=A0<div><br></div><div>What Miners=
should do with that is still up for debate, it seems. My opinion is that t=
hey should hold on and attempt to confirm the first, letting it go only if =
a conflicting transaction is mined elsewhere. (Let your Yes mean Yes...) Bu=
t I understand the contrary arguments.</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On 21 M=
ay 2013 17:04, Gregory Maxwell <span dir=3D"ltr"><<a href=3D"mailto:gmax=
well@gmail.com" target=3D"_blank">gmaxwell@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">
<div class=3D"im">On Mon, May 20, 2013 at 9:39 PM, Gavin Andresen <<a hr=
ef=3D"mailto:gavinandresen@gmail.com">gavinandresen@gmail.com</a>> wrote=
:<br>
> I'm very much in favor of double-spend propagation across the netw=
ork.<br>
<br>
</div>Absolutely.<br>
<br>
(to the list:) Is there anyone who is not? =A0(assuming that it doesn't=
<br>
allow arbitrary traffic multiplication, which is easily solved)<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
---------------------------------------------------------------------------=
---<br>
Try New Relic Now & We'll Send You this Cool Shirt<br>
New Relic is the only SaaS-based application performance monitoring service=
<br>
that delivers powerful full stack analytics. Optimize and monitor your<br>
browser, app, & servers with just a few lines of code. Try New Relic<br=
>
and get this awesome Nerd Life shirt! <a href=3D"http://p.sf.net/sfu/newrel=
ic_d2d_may" target=3D"_blank">http://p.sf.net/sfu/newrelic_d2d_may</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</div></div></blockquote></div><br></div>
--20cf307d04aee7d79204dd35f227--
|
