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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1XSSuN-0008Gw-Ml
for bitcoin-development@lists.sourceforge.net;
Fri, 12 Sep 2014 15:37:11 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.52 as permitted sender)
client-ip=209.85.219.52; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f52.google.com;
Received: from mail-oa0-f52.google.com ([209.85.219.52])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1XSSuM-0002GN-Qx
for bitcoin-development@lists.sourceforge.net;
Fri, 12 Sep 2014 15:37:11 +0000
Received: by mail-oa0-f52.google.com with SMTP id jd19so621663oac.39
for <bitcoin-development@lists.sourceforge.net>;
Fri, 12 Sep 2014 08:37:05 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.124.10 with SMTP id me10mr8941689oeb.4.1410536225302;
Fri, 12 Sep 2014 08:37:05 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.22.108 with HTTP; Fri, 12 Sep 2014 08:37:05 -0700 (PDT)
In-Reply-To: <CANOOu=-yhKK-db+VtoJbWH8H_rwrNHqXM1J12SketBXeLL6L1Q@mail.gmail.com>
References: <mailman.341412.1410515709.2178.bitcoin-development@lists.sourceforge.net>
<A4CC413B-D5A5-423C-9D56-463FCDBDDE08@coinqy.com>
<luuk5f$i8o$1@ger.gmane.org>
<CANEZrP1iTfZxY915hzoAEApz1+wd_S9j5RCwVJCNFqQ_+DNTSQ@mail.gmail.com>
<luv0dp$qms$1@ger.gmane.org>
<CANOOu=8RJgUW+=regOcqa9udiLr=nK=4fiZoW0fj2UU2GCjH3w@mail.gmail.com>
<CANOOu=-yhKK-db+VtoJbWH8H_rwrNHqXM1J12SketBXeLL6L1Q@mail.gmail.com>
Date: Fri, 12 Sep 2014 17:37:05 +0200
X-Google-Sender-Auth: KF9W4sdo6XuSLlFjREvoZ3mzT5Y
Message-ID: <CANEZrP2adsaM8dtA94JV+5qThDNrT8m+X45-q_DecT42i5L=jg@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Christophe Biocca <christophe.biocca@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b5d3f1ca6f0ab0502e00e16
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1XSSuM-0002GN-Qx
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>,
Andreas Schildbach <andreas@schildbach.de>
Subject: Re: [Bitcoin-development] BIP72 amendment proposal
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: Fri, 12 Sep 2014 15:37:11 -0000
--047d7b5d3f1ca6f0ab0502e00e16
Content-Type: text/plain; charset=UTF-8
>
> That way we leave up to implementers to experiment with different
> lengths and figure out what the optimum is
Ah, that's a good suggestion if we do go this way.
--047d7b5d3f1ca6f0ab0502e00e16
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">That way we leave up to implementers to experime=
nt with different<br>
lengths and figure out what the optimum is</blockquote><div><br></div><div>=
Ah, that's a good suggestion if we do go this way.=C2=A0</div></div></d=
iv></div>
--047d7b5d3f1ca6f0ab0502e00e16--
|
