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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <wtogami@gmail.com>) id 1YzUJO-0006Ee-Qo
for bitcoin-development@lists.sourceforge.net;
Mon, 01 Jun 2015 18:19:46 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.47 as permitted sender)
client-ip=209.85.220.47; envelope-from=wtogami@gmail.com;
helo=mail-pa0-f47.google.com;
Received: from mail-pa0-f47.google.com ([209.85.220.47])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YzUJN-0000jx-Sk
for bitcoin-development@lists.sourceforge.net;
Mon, 01 Jun 2015 18:19:46 +0000
Received: by padjw17 with SMTP id jw17so42512891pad.2
for <bitcoin-development@lists.sourceforge.net>;
Mon, 01 Jun 2015 11:19:40 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.66.118.166 with SMTP id kn6mr42311411pab.93.1433182780235;
Mon, 01 Jun 2015 11:19:40 -0700 (PDT)
Received: by 10.70.93.72 with HTTP; Mon, 1 Jun 2015 11:19:40 -0700 (PDT)
In-Reply-To: <BAY403-EAS318194A3B22E4C5D5FE559DC2B60@phx.gbl>
References: <BAY403-EAS318194A3B22E4C5D5FE559DC2B60@phx.gbl>
Date: Mon, 1 Jun 2015 08:19:40 -1000
Message-ID: <CAEz79PqGJ5XSMUbWVQOQ6DjJqbqHmad6t37RUX9Zz=2k4HJK3Q@mail.gmail.com>
From: "Warren Togami Jr." <wtogami@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=e89a8ffbaba783a6f3051778de12
X-Spam-Score: 3.1 (+++)
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
(wtogami[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.2 MISSING_HEADERS Missing To: header
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
2.7 MALFORMED_FREEMAIL Bad headers on message from free email service
-0.2 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1YzUJN-0000jx-Sk
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 18:19:46 -0000
--e89a8ffbaba783a6f3051778de12
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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 believe
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.
>
>
--e89a8ffbaba783a6f3051778de12
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">By reversing Mike'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 d=
o not seriously believe particular participants should be excluded.<br><div=
class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Jun 1, 2015 a=
t 3:06 AM, Thy Shizzle <span dir=3D"ltr"><<a href=3D"mailto:thyshizzle@o=
utlook.com" target=3D"_blank">thyshizzle@outlook.com</a>></span> wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:soli=
d;padding-left:1ex">
<div>
<div>
<div style=3D"font-family:Calibri,sans-serif;font-size:11pt">Doesn't me=
an you should build something that says "fuck you" to the compani=
es that have invested in farms of ASICS. To say "Oh yea if they can=
9;t mine it how we want stuff 'em" is naive. I get decentralisatio=
n,
but don't dis incentivise mining. If miners are telling you that you&#=
39;re going to hurt them, esp. Miners that combined hold > 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 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><div><div class=3D"h5">
<div>
<div dir=3D"ltr">
<blockquote style=3D"margin:0px 0px 0px 40px;border:none;padding:0px">Whils=
t 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 "right" to min=
e if they can't do the job - if miners
<strike>in</strike>=C2=A0<b>outside</b> China can'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'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">
<<a href=3D"mailto:mike@plan99.net" target=3D"_blank">mike@plan99.net</a=
>></span> wrote:<br>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-=
left-color:rgb(204,204,204);border-left-style:solid;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 "right"=
to mine if they can't do the job - if miners in China can't get th=
e 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.</div>
<div><br>
</div>
<div>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=
.</div>
</div>
</blockquote></div></div></div></div></div></div></blockquote></div><br></d=
iv></div>
--e89a8ffbaba783a6f3051778de12--
|
