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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <frankf44@gmail.com>) id 1VBVls-0005Bn-Ql
for bitcoin-development@lists.sourceforge.net;
Mon, 19 Aug 2013 20:09:48 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.45 as permitted sender)
client-ip=209.85.212.45; envelope-from=frankf44@gmail.com;
helo=mail-vb0-f45.google.com;
Received: from mail-vb0-f45.google.com ([209.85.212.45])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VBVlr-0005Hj-I1
for bitcoin-development@lists.sourceforge.net;
Mon, 19 Aug 2013 20:09:48 +0000
Received: by mail-vb0-f45.google.com with SMTP id e15so3443059vbg.4
for <bitcoin-development@lists.sourceforge.net>;
Mon, 19 Aug 2013 13:09:42 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.58.137.167 with SMTP id qj7mr14863434veb.1.1376942981976;
Mon, 19 Aug 2013 13:09:41 -0700 (PDT)
Received: by 10.220.165.201 with HTTP; Mon, 19 Aug 2013 13:09:41 -0700 (PDT)
In-Reply-To: <CAJHLa0MnnWw=qiYC0nJcY=BdTDcAjGtraJ+kazoG7_bHW-HBtw@mail.gmail.com>
References: <CAJHLa0MnnWw=qiYC0nJcY=BdTDcAjGtraJ+kazoG7_bHW-HBtw@mail.gmail.com>
Date: Mon, 19 Aug 2013 15:09:41 -0500
Message-ID: <CALxyHsXoCqL8dNXeayibfbR7-JU6Ke19gJJ1fToboULdUa155Q@mail.gmail.com>
From: Frank F <frankf44@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=047d7b677efa51198a04e4528551
X-Spam-Score: 0.9 (/)
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
(frankf44[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
digit (frankf44[at]gmail.com)
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
X-Headers-End: 1VBVlr-0005Hj-I1
Subject: Re: [Bitcoin-development] Proposal: remove "getwork" RPC from
bitcoind
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, 19 Aug 2013 20:09:49 -0000
--047d7b677efa51198a04e4528551
Content-Type: text/plain; charset=ISO-8859-1
I strongly object to removing the only mechanism that allows anyone to say
that bitcoin is p2p, in the truest sense of the word. Moves like this that
favor only the pool operators and private mining interests are signs that
bitcoin is headed towards a monopoly/cartel model, and that would be a
tragic outcome for something that holds a great promise. Nobody knows what
mining will look like in the future, and denying the individual novice the
ability to mine at a small scale, even if we may think it is inefficient
now, is not a good path to start down.
If there are technical problems with getwork, maybe they should be
addressed and fixed instead of outright abandoned.
On Mon, Aug 19, 2013 at 11:27 AM, Jeff Garzik <jgarzik@bitpay.com> wrote:
> Pull request https://github.com/bitcoin/bitcoin/pull/2905 proposes to
> remove "getwork" RPC from bitcoind: https://en.bitcoin.it/wiki/Getwork
>
> On mainnet, almost everybody uses a pool (and therefore, not "getwork"
> directly to bitcoind). Those few who solo mine use a pool server to
> talk to bitcoind via "getblocktemplate" or other means. Tests show
> that attempts to solo mine on mainnet via "getwork" lead to delays and
> problems.
>
> On testnet, getwork has a better chance of continuing to work.
> Nevertheless, the same tools (open source pool servers or p2pool) are
> available for testnet, obviating the continued need to support
> getwork.
>
> However, at one time, getwork to bitcoind was widely used. I wanted
> to poke the audience, to gauge response to removing "getwork." If a
> driving use case remains of which we're unaware, speak up, please. We
> don't want to break anybody needlessly.
>
> --
> Jeff Garzik
> Senior Software Engineer and open source evangelist
> BitPay, Inc. https://bitpay.com/
>
>
> ------------------------------------------------------------------------------
> Introducing Performance Central, a new site from SourceForge and
> AppDynamics. Performance Central is your source for news, insights,
> analysis and resources for efficient Application Performance Management.
> Visit us today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--
*MONEY IS OVER!*
IF YOU WANT IT<http://www.zeitgeistmovie.com/>
=====================================================
The causes of my servitude can be traced to the tyranny of money.
-Serj Tankian
--047d7b677efa51198a04e4528551
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">I strongly object to removing the only mechanism that allo=
ws anyone to say that bitcoin is p2p, in the truest sense of the word. Move=
s like this that favor only the pool operators and private mining interests=
are signs that bitcoin is headed towards a monopoly/cartel model, and that=
would be a tragic outcome for something that holds a great promise. Nobody=
knows what mining will look like in the future, and denying the individual=
novice the ability to mine at a small scale, even if we may think it is in=
efficient now, is not a good path to start down.<div>
<br></div><div>If there are technical problems with getwork, maybe they sho=
uld be addressed and fixed instead of outright abandoned.</div></div><div c=
lass=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Mon, Aug 19, 201=
3 at 11:27 AM, Jeff Garzik <span dir=3D"ltr"><<a href=3D"mailto:jgarzik@=
bitpay.com" target=3D"_blank">jgarzik@bitpay.com</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Pull request <a href=3D"https://github.com/b=
itcoin/bitcoin/pull/2905" target=3D"_blank">https://github.com/bitcoin/bitc=
oin/pull/2905</a> proposes to<br>
remove "getwork" RPC from bitcoind: <a href=3D"https://en.bitcoin=
.it/wiki/Getwork" target=3D"_blank">https://en.bitcoin.it/wiki/Getwork</a><=
br>
<br>
On mainnet, almost everybody uses a pool (and therefore, not "getwork&=
quot;<br>
directly to bitcoind). =A0Those few who solo mine use a pool server to<br>
talk to bitcoind via "getblocktemplate" or other means. =A0Tests =
show<br>
that attempts to solo mine on mainnet via "getwork" lead to delay=
s and<br>
problems.<br>
<br>
On testnet, getwork has a better chance of continuing to work.<br>
Nevertheless, the same tools (open source pool servers or p2pool) are<br>
available for testnet, obviating the continued need to support<br>
getwork.<br>
<br>
However, at one time, getwork to bitcoind was widely used. =A0I wanted<br>
to poke the audience, to gauge response to removing "getwork." =
=A0If a<br>
driving use case remains of which we're unaware, speak up, please. =A0W=
e<br>
don't want to break anybody needlessly.<br>
<br>
--<br>
Jeff Garzik<br>
Senior Software Engineer and open source evangelist<br>
BitPay, Inc. =A0 =A0 =A0<a href=3D"https://bitpay.com/" target=3D"_blank">h=
ttps://bitpay.com/</a><br>
<br>
---------------------------------------------------------------------------=
---<br>
Introducing Performance Central, a new site from SourceForge and<br>
AppDynamics. Performance Central is your source for news, insights,<br>
analysis and resources for efficient Application Performance Management.<br=
>
Visit us today!<br>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D48897511&iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D48897511&iu=3D/4140/ostg.clktrk</a><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>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div style=
=3D"text-align:left"><b><span style=3D"font-size:xx-large">MONEY IS OVER!</=
span></b></div><div><div style=3D"text-align:left"><span style=3D"font-size=
:x-small">=A0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0<a href=3D"http://www.zeitgeistmovie.com/" target=3D"_blank">IF YOU WANT=
IT</a></span></div>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D<br>The causes of my servitude can be traced to the tyranny of mon=
ey.<br>-Serj Tankian</div>
</div>
--047d7b677efa51198a04e4528551--
|
