summaryrefslogtreecommitdiff
path: root/4e/7c866311485bd15124318a836a6e5121ad7b35
blob: 99c57a77c356e68000e6f55f84509853f53161b2 (plain)
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
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <pieter.wuille@gmail.com>) id 1Z3Tew-00051g-AP
	for bitcoin-development@lists.sourceforge.net;
	Fri, 12 Jun 2015 18:26:30 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.160.176 as permitted sender)
	client-ip=209.85.160.176; envelope-from=pieter.wuille@gmail.com;
	helo=mail-yk0-f176.google.com; 
Received: from mail-yk0-f176.google.com ([209.85.160.176])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Z3Tev-0003nW-KN
	for bitcoin-development@lists.sourceforge.net;
	Fri, 12 Jun 2015 18:26:30 +0000
Received: by ykfl8 with SMTP id l8so21477999ykf.1
	for <bitcoin-development@lists.sourceforge.net>;
	Fri, 12 Jun 2015 11:26:24 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.170.212.3 with SMTP id d3mr20412031ykf.69.1434133584176;
	Fri, 12 Jun 2015 11:26:24 -0700 (PDT)
Received: by 10.37.93.67 with HTTP; Fri, 12 Jun 2015 11:26:23 -0700 (PDT)
Received: by 10.37.93.67 with HTTP; Fri, 12 Jun 2015 11:26:23 -0700 (PDT)
In-Reply-To: <CANEZrP3=uM-d7zKcCW=YJnrgNBk3dCvSk8OhdUzR1g3m_ktBpw@mail.gmail.com>
References: <CAPg+sBi5fYHGLv4wtWbWE7jov8CX=q9UX=vhxDVepG6JfX30+g@mail.gmail.com>
	<CANEZrP3=uM-d7zKcCW=YJnrgNBk3dCvSk8OhdUzR1g3m_ktBpw@mail.gmail.com>
Date: Fri, 12 Jun 2015 20:26:23 +0200
Message-ID: <CAPg+sBgJAKA6s14SEoNSKOY=9-dTBBhNMzS03p0xTC4h9mmBvw@mail.gmail.com>
From: Pieter Wuille <pieter.wuille@gmail.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: multipart/alternative; boundary=001a1139f386d86e7b0518563e01
X-Spam-Score: -0.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
	(pieter.wuille[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-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: 1Z3Tev-0003nW-KN
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Mining centralization pressure from
 non-uniform propagation speed
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 Jun 2015 18:26:30 -0000

--001a1139f386d86e7b0518563e01
Content-Type: text/plain; charset=UTF-8

I'm merely proving the existence of the effect.
On Jun 12, 2015 8:24 PM, "Mike Hearn" <mike@plan99.net> wrote:

> are only connected to each other through a slow 2 Mbit/s link.
>>
>
> That's very slow indeed. For comparison, plain old 3G connections
> routinely cruise around 7-8 Mbit/sec.
>
> So this simulation is assuming a speed dramatically worse than a mobile
> phone can get!
>

--001a1139f386d86e7b0518563e01
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">I&#39;m merely proving the existence of the effect.</p>
<div class=3D"gmail_quote">On Jun 12, 2015 8:24 PM, &quot;Mike Hearn&quot; =
&lt;<a href=3D"mailto:mike@plan99.net">mike@plan99.net</a>&gt; wrote:<br ty=
pe=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div cla=
ss=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
"><div dir=3D"ltr"><div><div><div>are only connected to each other through =
a slow 2 Mbit/s link.<br></div></div></div></div></blockquote><div><br></di=
v><div>That&#39;s very slow indeed. For comparison, plain old 3G connection=
s routinely cruise around 7-8 Mbit/sec.</div><div><br></div><div>So this si=
mulation is assuming a speed dramatically worse than a mobile phone can get=
!</div></div></div></div>
</blockquote></div>

--001a1139f386d86e7b0518563e01--