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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <frankf44@gmail.com>) id 1VBVsG-0003fE-KV
for bitcoin-development@lists.sourceforge.net;
Mon, 19 Aug 2013 20:16:24 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.41 as permitted sender)
client-ip=209.85.212.41; envelope-from=frankf44@gmail.com;
helo=mail-vb0-f41.google.com;
Received: from mail-vb0-f41.google.com ([209.85.212.41])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VBVsF-0005nI-ES
for bitcoin-development@lists.sourceforge.net;
Mon, 19 Aug 2013 20:16:24 +0000
Received: by mail-vb0-f41.google.com with SMTP id g17so3675868vbg.28
for <bitcoin-development@lists.sourceforge.net>;
Mon, 19 Aug 2013 13:16:17 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.220.10.194 with SMTP id q2mr14968437vcq.2.1376943377902;
Mon, 19 Aug 2013 13:16:17 -0700 (PDT)
Received: by 10.220.165.201 with HTTP; Mon, 19 Aug 2013 13:16:17 -0700 (PDT)
In-Reply-To: <CAPg+sBjMdZfHpZrvHwMx6oQsS0yJaXVjTnyRwf6VCdnWTHQZaw@mail.gmail.com>
References: <CAJHLa0MnnWw=qiYC0nJcY=BdTDcAjGtraJ+kazoG7_bHW-HBtw@mail.gmail.com>
<CALxyHsXoCqL8dNXeayibfbR7-JU6Ke19gJJ1fToboULdUa155Q@mail.gmail.com>
<CAPg+sBjMdZfHpZrvHwMx6oQsS0yJaXVjTnyRwf6VCdnWTHQZaw@mail.gmail.com>
Date: Mon, 19 Aug 2013 15:16:17 -0500
Message-ID: <CALxyHsV=LWY+TzZG-XBQ6HNhxFEezjFhW++aJ7oVbVGEJWW0nw@mail.gmail.com>
From: Frank F <frankf44@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=001a11c3b944ea73aa04e4529c71
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: 1VBVsF-0005nI-ES
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:16:24 -0000
--001a11c3b944ea73aa04e4529c71
Content-Type: text/plain; charset=ISO-8859-1
Thank you for setting me straight. Please forgive my ignorance.
On Mon, Aug 19, 2013 at 3:14 PM, Pieter Wuille <pieter.wuille@gmail.com>wrote:
> On Mon, Aug 19, 2013 at 10:09 PM, Frank F <frankf44@gmail.com> wrote:
> > 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.
>
> They were addressed and fixed in a successor API, getblocktemplate.
> It's even more decentralization-friendly, as it allows the caller to
> see what transactions the daemon is trying to put into a block, and
> even modify it.
>
> The suggestion here is not to remove functionality - only to remove an
> obsolete API for doing so.
>
> --
> Pieter
>
--
*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
--001a11c3b944ea73aa04e4529c71
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Thank you for setting me straight. Please forgive my ignor=
ance.</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On=
Mon, Aug 19, 2013 at 3:14 PM, Pieter Wuille <span dir=3D"ltr"><<a href=
=3D"mailto:pieter.wuille@gmail.com" target=3D"_blank">pieter.wuille@gmail.c=
om</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"><div class=3D"im">On Mon, Aug 19, 2013 at 10=
:09 PM, Frank F <<a href=3D"mailto:frankf44@gmail.com">frankf44@gmail.co=
m</a>> wrote:<br>
> I strongly object to removing the only mechanism that allows anyone to=
say<br>
> that bitcoin is p2p, in the truest sense of the word. Moves like this =
that<br>
> favor only the pool operators and private mining interests are signs t=
hat<br>
> bitcoin is headed towards a monopoly/cartel model, and that would be a=
<br>
> tragic outcome for something that holds a great promise. Nobody knows =
what<br>
> mining will look like in the future, and denying the individual novice=
the<br>
> ability to mine at a small scale, even if we may think it is inefficie=
nt<br>
> now, is not a good path to start down.<br>
><br>
> If there are technical problems with getwork, maybe they should be add=
ressed<br>
> and fixed instead of outright abandoned.<br>
<br>
</div>They were addressed and fixed in a successor API, getblocktemplate.<b=
r>
It's even more decentralization-friendly, as it allows the caller to<br=
>
see what transactions the daemon is trying to put into a block, and<br>
even modify it.<br>
<br>
The suggestion here is not to remove functionality - only to remove an<br>
obsolete API for doing so.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
Pieter<br>
</font></span></blockquote></div><br><br clear=3D"all"><div><br></div>-- <b=
r><div style=3D"text-align:left"><b><span style=3D"font-size:xx-large">MONE=
Y 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>
--001a11c3b944ea73aa04e4529c71--
|
