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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1WowWD-00068J-AJ
for bitcoin-development@lists.sourceforge.net;
Mon, 26 May 2014 15:08:53 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.49 as permitted sender)
client-ip=209.85.219.49; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f49.google.com;
Received: from mail-oa0-f49.google.com ([209.85.219.49])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WowWC-0000Fa-8V
for bitcoin-development@lists.sourceforge.net;
Mon, 26 May 2014 15:08:53 +0000
Received: by mail-oa0-f49.google.com with SMTP id eb12so8270529oac.8
for <bitcoin-development@lists.sourceforge.net>;
Mon, 26 May 2014 08:08:46 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.47.77 with SMTP id b13mr25800891oen.40.1401116926755;
Mon, 26 May 2014 08:08:46 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.71.162 with HTTP; Mon, 26 May 2014 08:08:46 -0700 (PDT)
In-Reply-To: <CAAS2fgRrDR5nHpuyDg7tdu-kYjYc6XnyPcjquodYjsMWiTJRaQ@mail.gmail.com>
References: <CAOXABZohe93SSRm1FN5ai2H97eBJV2j+LAjA-39YAaNmX=ep0Q@mail.gmail.com>
<CAAS2fgSJh83YEZjRfL81sKjC=nSKHtWT1qzS0evLJ9Gy6qdA1w@mail.gmail.com>
<CANEZrP0wtyagZeSe7kRwk08Td-O5RGz_vwbTNm_v69VdfUuorw@mail.gmail.com>
<CAAS2fgRrDR5nHpuyDg7tdu-kYjYc6XnyPcjquodYjsMWiTJRaQ@mail.gmail.com>
Date: Mon, 26 May 2014 17:08:46 +0200
X-Google-Sender-Auth: Ty5i2kxv6QQcuZt1x0cVHn00HPQ
Message-ID: <CANEZrP3NQccynmtUZKN_9tdNO3r-fmfgZWdzWHUVsnXdzvRGWw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Gregory Maxwell <gmaxwell@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c21116b54a9a04fa4ef408
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: 1WowWC-0000Fa-8V
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Cut-through propagation of blocks
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: Mon, 26 May 2014 15:08:53 -0000
--001a11c21116b54a9a04fa4ef408
Content-Type: text/plain; charset=UTF-8
>
> it: I'd be much more likely to run an experimental gateway in another
> process on a node than experimental p2p code inside my production
> bitcoinds themselves.
>
Yes, it's certainly better to do that during the development phase. However
if it does turn out to be good and valuable then it'd eventually need to be
integrated or rewritten into Core anyway, lest we accidentally increase the
setup cost of running a node and end up with a two-tier network. And if the
code will eventually want to be merged into Core anyway, it might as well
be implemented into it directly, perhaps behind a switch that can disable
those codepaths if something goes wrong.
So I think the tradeoffs here are rather complicated and subtle.
--001a11c21116b54a9a04fa4ef408
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">it: I'd be much more likely to run an experi=
mental gateway in another<br>
process on a node than experimental p2p code inside my production<br>
bitcoinds themselves.<br>
</blockquote></div><br></div><div class=3D"gmail_extra">Yes, it's certa=
inly better to do that during the development phase. However if it does tur=
n out to be good and valuable then it'd eventually need to be integrate=
d or rewritten into Core anyway, lest we accidentally increase the setup co=
st of running a node and end up with a two-tier network. And if the code wi=
ll eventually want to be merged into Core anyway, it might as well be imple=
mented into it directly, perhaps behind a switch that can disable those cod=
epaths if something goes wrong.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">So I think =
the tradeoffs here are rather complicated and subtle.</div></div>
--001a11c21116b54a9a04fa4ef408--
|
