summaryrefslogtreecommitdiff
path: root/48/8c7dda160777f0d2ba79f1dede88c904f1dc0c
blob: e5b6ade29b172140e90a8d0f92b649aa803d79cb (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
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
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <pindar.wong@gmail.com>) id 1YzXyA-0006fW-FN
	for bitcoin-development@lists.sourceforge.net;
	Mon, 01 Jun 2015 22:14:06 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 74.125.82.43 as permitted sender)
	client-ip=74.125.82.43; envelope-from=pindar.wong@gmail.com;
	helo=mail-wg0-f43.google.com; 
Received: from mail-wg0-f43.google.com ([74.125.82.43])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1YzXy8-0004Ua-S0
	for bitcoin-development@lists.sourceforge.net;
	Mon, 01 Jun 2015 22:14:06 +0000
Received: by wgbgq6 with SMTP id gq6so125901010wgb.3
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 01 Jun 2015 15:13:58 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.89.234 with SMTP id br10mr24805346wib.86.1433196838834; 
	Mon, 01 Jun 2015 15:13:58 -0700 (PDT)
Received: by 10.194.156.226 with HTTP; Mon, 1 Jun 2015 15:13:58 -0700 (PDT)
In-Reply-To: <BAY403-EAS416EB557ABDDCA6FE2FCC7FC2B60@phx.gbl>
References: <BAY403-EAS416EB557ABDDCA6FE2FCC7FC2B60@phx.gbl>
Date: Tue, 2 Jun 2015 06:13:58 +0800
Message-ID: <CAM7BtUqx6Ku+ozzPhk4jh2CPmA=XcuudWqCxF82qciFiwM_h5A@mail.gmail.com>
From: Pindar Wong <pindar.wong@gmail.com>
To: Thy Shizzle <thyshizzle@outlook.com>
Content-Type: multipart/alternative; boundary=e89a8f3ba2d578d9ba05177c2443
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: 1YzXy8-0004Ua-S0
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 22:14:06 -0000

--e89a8f3ba2d578d9ba05177c2443
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

It would be helpful to hear from the other miners, and perhaps arrange some
testing and telemetry in China with 8 ...  that's even a Chinese lucky
number ;)

p.


On Tue, Jun 2, 2015 at 5:32 AM, Thy Shizzle <thyshizzle@outlook.com> wrote:

>  Ah sorry, I just thought you were saying doesn't matter which side let
> 'em burn.
>
> If I were the Chinese and people moved to 20mb MAX size blocks and said
> stuff you, I'd just start firing out small coinbase only blocks now, if
> they truly have >50% hashing power and they collaborate chances are they
> can build a longer chain of just coinbase for themselves then the rest of
> the network doing big blocks. They don't even have to propagate this chai=
n
> to you in a hurry right? And then they never have to receive a 20mb block
> from you because they have a longer chain without 20mb blocks and always
> ahead of your big blocks. As long as it is the longest chain it is
> Authority so let you guys transact your coinbase from the blocks you crea=
te
> etc. then whamo along come the chinese and supply a longer chain of just
> coinbase only blocks which invalidates all your previous transactions and
> gives them all the coinbase they stamped, while invalidating yours.
>
> But who cares about them right :p
>  ------------------------------
> From: Warren Togami Jr. <wtogami@gmail.com>
> Sent: =E2=80=8E2/=E2=80=8E06/=E2=80=8E2015 4:19 AM
> Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
> Subject: Re: [Bitcoin-development] Fwd: Block Size Increase Requirements
>
>  By reversing Mike's language to the reality of the situation I had hoped
> people would realize how abjectly ignorant and insensitive his statement
> was.  I am sorry to those in the community if they misunderstood my post.=
 I
> thought it was obvious that it was sarcasm where I do not seriously belie=
ve
> particular participants should be excluded.
>
> On Mon, Jun 1, 2015 at 3:06 AM, Thy Shizzle <thyshizzle@outlook.com>
> wrote:
>
>  Doesn't mean you should build something that says "fuck you" to the
> companies that have invested in farms of ASICS. To say "Oh yea if they
> can't mine it how we want stuff 'em" is naive. I get decentralisation, bu=
t
> don't dis incentivise mining. If miners are telling you that you're going
> to hurt them, esp. Miners that combined hold > 50% hashing power, why wou=
ld
> you say too bad so sad? Why not just start stripping bitcoin out of
> adopters wallets? Same thing.
>  ------------------------------
> From: Warren Togami Jr. <wtogami@gmail.com>
> Sent: =E2=80=8E1/=E2=80=8E06/=E2=80=8E2015 10:30 PM
> Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
> Subject: Re: [Bitcoin-development] Fwd: Block Size Increase Requirements
>
>    Whilst it would be nice if miners in *outside* 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 *outside* China
> can't get the trivial amounts of bandwidth required through their firewal=
l *TO
> THE MAJORITY OF THE HASHRATE* and end up being outcompeted then OK, too
> bad, we'll have to carry on without them.
>
>
> On Mon, Jun 1, 2015 at 12:13 AM, 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" t=
o
> 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.
>
>
>
>
> -------------------------------------------------------------------------=
-----
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>

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

<div dir=3D"ltr"><div><div>It would be helpful to hear from the other miner=
s, and perhaps arrange some testing and telemetry in China with 8 ...=C2=A0=
 that&#39;s even a Chinese lucky number ;)<br></div><br></div>p.<br><span c=
lass=3D"im"></span><br><div><div class=3D"gmail_extra"><br><div class=3D"gm=
ail_quote">On Tue, Jun 2, 2015 at 5:32 AM, Thy Shizzle <span dir=3D"ltr">&l=
t;<a href=3D"mailto:thyshizzle@outlook.com" target=3D"_blank">thyshizzle@ou=
tlook.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">



<div>
<div>
<div style=3D"font-family:Calibri,sans-serif;font-size:11pt">Ah sorry, I ju=
st thought you were saying doesn&#39;t matter which side let &#39;em burn.<=
br>
<br>
If I were the Chinese and people moved to 20mb MAX size blocks and said stu=
ff you, I&#39;d just start firing out small coinbase only blocks now, if th=
ey truly have &gt;50% hashing power and they collaborate chances are they c=
an build a longer chain of just coinbase
 for themselves then the rest of the network doing big blocks. They don&#39=
;t even have to propagate this chain to you in a hurry right? And then they=
 never have to receive a 20mb block from you because they have a longer cha=
in without 20mb blocks and always ahead
 of your big blocks. As long as it is the longest chain it is Authority so =
let you guys transact your coinbase from the blocks you create etc. then wh=
amo along come the chinese and supply a longer chain of just coinbase only =
blocks which invalidates all your
 previous transactions and gives them all the coinbase they stamped, while =
invalidating yours.<br>
<br>
But who cares about them right :p</div>
</div>
<div dir=3D"ltr"><span class=3D"">
<hr>
<span style=3D"font-family:Calibri,sans-serif;font-size:11pt;font-weight:bo=
ld">From:
</span><span style=3D"font-family:Calibri,sans-serif;font-size:11pt"><a hre=
f=3D"mailto:wtogami@gmail.com" target=3D"_blank">Warren Togami Jr.</a></spa=
n><br>
</span><span style=3D"font-family:Calibri,sans-serif;font-size:11pt;font-we=
ight:bold">Sent:
</span><span style=3D"font-family:Calibri,sans-serif;font-size:11pt">=E2=80=
=8E2/=E2=80=8E06/=E2=80=8E2015 4:19 AM</span><span class=3D""><br>
<span style=3D"font-family:Calibri,sans-serif;font-size:11pt;font-weight:bo=
ld">Cc:
</span><span style=3D"font-family:Calibri,sans-serif;font-size:11pt"><a hre=
f=3D"mailto:bitcoin-development@lists.sourceforge.net" target=3D"_blank">Bi=
tcoin Dev</a></span><br>
<span style=3D"font-family:Calibri,sans-serif;font-size:11pt;font-weight:bo=
ld">Subject:
</span><span style=3D"font-family:Calibri,sans-serif;font-size:11pt">Re: [B=
itcoin-development] Fwd: Block Size Increase Requirements</span><br>
<br>
</span></div><span class=3D"">
<div>
<div dir=3D"ltr">By reversing Mike&#39;s language to the reality of the sit=
uation I had hoped people would realize how abjectly ignorant and insensiti=
ve his statement was.=C2=A0 I am sorry to those in the community if they mi=
sunderstood my post. I thought it was obvious
 that it was sarcasm where I do not seriously believe particular participan=
ts should be excluded.<br>
<div><br>
<div>On Mon, Jun 1, 2015 at 3:06 AM, Thy Shizzle <span dir=3D"ltr">
&lt;<a href=3D"mailto:thyshizzle@outlook.com" target=3D"_blank">thyshizzle@=
outlook.com</a>&gt;</span> wrote:<br>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex">
<div>
<div>
<div style=3D"font-family:Calibri,sans-serif;font-size:11pt">Doesn&#39;t me=
an you should build something that says &quot;fuck you&quot; to the compani=
es that have invested in farms of ASICS. To say &quot;Oh yea if they can&#3=
9;t mine it how we want stuff &#39;em&quot; is naive. I get decentralisatio=
n,
 but don&#39;t dis incentivise mining. If miners are telling you that you&#=
39;re going to hurt them, esp. Miners that combined hold &gt; 50% hashing p=
ower, why would you say too bad so sad? Why not just start stripping bitcoi=
n out of adopters wallets? Same thing.</div>
</div>
<div dir=3D"ltr">
<hr>
<span style=3D"font-family:Calibri,sans-serif;font-size:11pt;font-weight:bo=
ld">From:
</span><span style=3D"font-family:Calibri,sans-serif;font-size:11pt"><a hre=
f=3D"mailto:wtogami@gmail.com" target=3D"_blank">Warren Togami Jr.</a></spa=
n><br>
<span style=3D"font-family:Calibri,sans-serif;font-size:11pt;font-weight:bo=
ld">Sent:
</span><span style=3D"font-family:Calibri,sans-serif;font-size:11pt">=E2=80=
=8E1/=E2=80=8E06/=E2=80=8E2015 10:30 PM</span><span><br>
<span style=3D"font-family:Calibri,sans-serif;font-size:11pt;font-weight:bo=
ld">Cc:
</span><span style=3D"font-family:Calibri,sans-serif;font-size:11pt"><a hre=
f=3D"mailto:bitcoin-development@lists.sourceforge.net" target=3D"_blank">Bi=
tcoin Dev</a></span><br>
<span style=3D"font-family:Calibri,sans-serif;font-size:11pt;font-weight:bo=
ld">Subject:
</span><span style=3D"font-family:Calibri,sans-serif;font-size:11pt">Re: [B=
itcoin-development] Fwd: Block Size Increase Requirements</span><br>
<br>
</span></div>
<div>
<div>
<div>
<div dir=3D"ltr">
<blockquote style=3D"margin:0px 0px 0px 40px;border:medium none;padding:0px=
">Whilst it would be nice if miners
<strike>in</strike> <b>outside</b> China can carry on forever regardless of=
 their internet situation, nobody has any inherent &quot;right&quot; to min=
e if they can&#39;t do the job - if miners
<strike>in</strike>=C2=A0<b>outside</b> China can&#39;t get the trivial amo=
unts of bandwidth required
<strike>through their firewall</strike> <b>TO THE MAJORITY OF THE HASHRATE<=
/b> and end up being outcompeted then OK, too bad, we&#39;ll have to carry =
on without them.<br>
</blockquote>
</div>
<div><br>
<div>On Mon, Jun 1, 2015 at 12:13 AM, Mike Hearn <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:mike@plan99.net" target=3D"_blank">mike@plan99.net</a>&gt;</s=
pan> wrote:<br>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex">
<div dir=3D"ltr">
<div>Whilst it would be nice if miners in China can carry on forever regard=
less of their internet situation, nobody has any inherent &quot;right&quot;=
 to mine if they can&#39;t do the job - if miners in China can&#39;t get th=
e trivial amounts of bandwidth required through their
 firewall and end up being outcompeted then OK, too bad, we&#39;ll have to =
carry on without them.</div>
<div><br>
</div>
<div>But I&#39;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=
.</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</span></div>

<br>-----------------------------------------------------------------------=
-------<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>
<br></blockquote></div><br></div></div></div>

--e89a8f3ba2d578d9ba05177c2443--