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
|
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 <gmaxwell@gmail.com>) id 1UegcS-00064D-6d
for bitcoin-development@lists.sourceforge.net;
Tue, 21 May 2013 07:04:24 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.215.47 as permitted sender)
client-ip=209.85.215.47; envelope-from=gmaxwell@gmail.com;
helo=mail-la0-f47.google.com;
Received: from mail-la0-f47.google.com ([209.85.215.47])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UegcR-0002r6-FK
for bitcoin-development@lists.sourceforge.net;
Tue, 21 May 2013 07:04:24 +0000
Received: by mail-la0-f47.google.com with SMTP id fq12so289693lab.34
for <bitcoin-development@lists.sourceforge.net>;
Tue, 21 May 2013 00:04:16 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.152.19.132 with SMTP id f4mr575536lae.16.1369119856758; Tue,
21 May 2013 00:04:16 -0700 (PDT)
Received: by 10.112.69.140 with HTTP; Tue, 21 May 2013 00:04:16 -0700 (PDT)
In-Reply-To: <CABsx9T1nqGCL00Hmq11srMU-n_KVYm2t-EjsBkWBtf699AECwA@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>
Date: Tue, 21 May 2013 00:04:16 -0700
Message-ID: <CAAS2fgSfbKGp5Qe4_RQeSvU0Ay-=m3CncaiQ5LLrMBtx0z5Pmg@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Content-Type: text/plain; charset=UTF-8
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(gmaxwell[at]gmail.com)
-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: 1UegcR-0002r6-FK
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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 07:04:24 -0000
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)
|
