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
154
155
156
157
158
159
160
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pindar.wong@gmail.com>) id 1YzNas-0000Gl-Ef
for bitcoin-development@lists.sourceforge.net;
Mon, 01 Jun 2015 11:09:22 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.178 as permitted sender)
client-ip=209.85.212.178; envelope-from=pindar.wong@gmail.com;
helo=mail-wi0-f178.google.com;
Received: from mail-wi0-f178.google.com ([209.85.212.178])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YzNaq-0004ly-6Y
for bitcoin-development@lists.sourceforge.net;
Mon, 01 Jun 2015 11:09:22 +0000
Received: by wibut5 with SMTP id ut5so34922469wib.1
for <bitcoin-development@lists.sourceforge.net>;
Mon, 01 Jun 2015 04:09:14 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.84.179 with SMTP id a19mr39274556wjz.29.1433156954147;
Mon, 01 Jun 2015 04:09:14 -0700 (PDT)
Received: by 10.194.156.226 with HTTP; Mon, 1 Jun 2015 04:09:13 -0700 (PDT)
In-Reply-To: <CAFzgq-ykeMeWF-ndgSm9upHTe8j6ZFYhBQjFs_WSz1oVd29j7g@mail.gmail.com>
References: <554BE0E1.5030001@bluematt.me>
<CAFzgq-xByQ1E_33_m3UpXQFUkGc78HKnA=7XXMshANDuTkNsvA@mail.gmail.com>
<CABsx9T0kbRe31LMwk499MQUw225f5GGd67GfhXBezHmDqxkioA@mail.gmail.com>
<CAFzgq-z5WCznGhbOexS0XESNGAVauw45ewEV-1eMij7yDT61=Q@mail.gmail.com>
<CAFzgq-zTybEQyGz0nq90u5n5JZcJzxQS_XKaTpr5POJi-tHM6A@mail.gmail.com>
<CABsx9T2L5bi-c63-KqSifOMeNayUWSPo0_Hx8VjMR_4=kC3ixg@mail.gmail.com>
<CAE28kUT61qYxqV0mOqw5Dan=eMiCvnG2SnsAeWzOWTxwLydyeQ@mail.gmail.com>
<CABsx9T2hfpts5y_M6PdDcxmq9Q2smesJ0Nmp9a9iyPD_MoPC9g@mail.gmail.com>
<CAE28kUTZV3YsaSCX2d5YwLetnf=f+bOWGrwxLXdZFywTZ=+Pjg@mail.gmail.com>
<CALC81CNq-GK5q6R4bmgHL5_Ej2+cZrtQMMLVmuhvMxkZokM3hQ@mail.gmail.com>
<CAE28kUQr+kUPak67tcNQGGscUXtJiD1LiXfjdD8_LMUWyVdR5w@mail.gmail.com>
<CANEZrP12WAcUOJp5UYg4pfWL7_4WiAHWWZAoaxAb5xB+qAP4Xg@mail.gmail.com>
<CAFzgq-ykeMeWF-ndgSm9upHTe8j6ZFYhBQjFs_WSz1oVd29j7g@mail.gmail.com>
Date: Mon, 1 Jun 2015 19:09:13 +0800
Message-ID: <CAM7BtUo0kJOmA+7+4pr-SPZb-YO-cOvrE8f0GZ-=v3mFT8MEYg@mail.gmail.com>
From: Pindar Wong <pindar.wong@gmail.com>
To: Chun Wang <1240902@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bfcfa0a28d233051772db3e
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
(pindar.wong[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: 1YzNaq-0004ly-6Y
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Fwd: Block Size Increase Requirements
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, 01 Jun 2015 11:09:22 -0000
--047d7bfcfa0a28d233051772db3e
Content-Type: text/plain; charset=UTF-8
I think it would be helpful if we could all *chill* and focus on the solid
engineering necessary to make Bitcoin succeed.
p.
On Mon, Jun 1, 2015 at 7:02 PM, Chun Wang <1240902@gmail.com> wrote:
> On Mon, Jun 1, 2015 at 6:13 PM, Mike Hearn <mike@plan99.net> wrote:
> > Whilst it would be nice if miners in China can carry on forever
> regardless
> > of their internet situation, nobody has any inherent "right" to mine if
> they
> > can't do the job - if miners in China can't get the trivial amounts of
> > bandwidth required through their firewall and end up being outcompeted
> then
> > OK, too bad, we'll have to carry on without them.
> >
> > But I'm not sure why it should be a big deal. They can always run a node
> on
> > a server in Taiwan and connect the hardware to it via a VPN or so.
>
> Ignorant. You seem do not understand the current situation. We
> suffered from orphans a lot when we started in 2013. It is now your
> turn. If Western miners do not find a China-based VPN into China, or
> if Western pools do not manage to improve their connectivity to China,
> or run a node in China, it would be them to have higher orphans, not
> us. Because we have 50%+.
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--047d7bfcfa0a28d233051772db3e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>I think it would be helpful if we could all *chill* a=
nd focus on the solid engineering necessary to make Bitcoin succeed.<br><br=
></div>p.<br><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Mon, Jun 1, 2015 at 7:02 PM, Chun Wang <span dir=3D"ltr"><<a href=3D"=
mailto:1240902@gmail.com" target=3D"_blank">1240902@gmail.com</a>></span=
> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><span class=3D"">On Mon, Jun 1, =
2015 at 6:13 PM, Mike Hearn <<a href=3D"mailto:mike@plan99.net">mike@pla=
n99.net</a>> wrote:<br>
</span><div><div class=3D"h5">> Whilst it would be nice if miners in Chi=
na can carry on forever regardless<br>
> of their internet situation, nobody has any inherent "right"=
to mine if they<br>
> can't do the job - if miners in China can't get the trivial am=
ounts of<br>
> bandwidth required through their firewall and end up being outcompeted=
then<br>
> OK, too bad, we'll have to carry on without them.<br>
><br>
> But I'm not sure why it should be a big deal. They can always run =
a node on<br>
> a server in Taiwan and connect the hardware to it via a VPN or so.<br>
<br>
</div></div>Ignorant. You seem do not understand the current situation. We<=
br>
suffered from orphans a lot when we started in 2013. It is now your<br>
turn. If Western miners do not find a China-based VPN into China, or<br>
if Western pools do not manage to improve their connectivity to China,<br>
or run a node in China, it would be them to have higher orphans, not<br>
us. Because we have 50%+.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
---------------------------------------------------------------------------=
---<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></div>
--047d7bfcfa0a28d233051772db3e--
|
