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
|
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 <wtogami@gmail.com>) id 1VBYu4-0007Oy-VC
for bitcoin-development@lists.sourceforge.net;
Mon, 19 Aug 2013 23:30:29 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.160.45 as permitted sender)
client-ip=209.85.160.45; envelope-from=wtogami@gmail.com;
helo=mail-pb0-f45.google.com;
Received: from mail-pb0-f45.google.com ([209.85.160.45])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VBYu3-0006ht-Jf
for bitcoin-development@lists.sourceforge.net;
Mon, 19 Aug 2013 23:30:28 +0000
Received: by mail-pb0-f45.google.com with SMTP id mc17so5545446pbc.4
for <bitcoin-development@lists.sourceforge.net>;
Mon, 19 Aug 2013 16:30:21 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.68.189.228 with SMTP id gl4mr15872198pbc.57.1376955021683;
Mon, 19 Aug 2013 16:30:21 -0700 (PDT)
Received: by 10.66.72.225 with HTTP; Mon, 19 Aug 2013 16:30:21 -0700 (PDT)
In-Reply-To: <kuu86a$ii5$1@ger.gmane.org>
References: <CAJHLa0MnnWw=qiYC0nJcY=BdTDcAjGtraJ+kazoG7_bHW-HBtw@mail.gmail.com>
<CALxyHsXoCqL8dNXeayibfbR7-JU6Ke19gJJ1fToboULdUa155Q@mail.gmail.com>
<CAAS2fgQRcfbe+3A6_t4s8BJRaWwmLdKkGG1ePmG+Epm5W6CxdQ@mail.gmail.com>
<CAAS2fgT_9KX4tEOqehwBf=TCV1c92b3W2ADKLqwkzqvcyWseUw@mail.gmail.com>
<CAEz79PpZ8a1vByinFz03efHCS71AtnFCjkXtK7My6z=QG=F92A@mail.gmail.com>
<CAJHLa0MuF4r1cz1sQc=Qrf5CoHtei8CPvyAL8PBCo=Oug=hMRQ@mail.gmail.com>
<kuu86a$ii5$1@ger.gmane.org>
Date: Mon, 19 Aug 2013 13:30:21 -1000
Message-ID: <CAEz79PoZx6f9U6LQdWGPtb=tRxiDqONriV8pCobtnqGB_nCcQw@mail.gmail.com>
From: "Warren Togami Jr." <wtogami@gmail.com>
To: Andreas Schildbach <andreas@schildbach.de>
Content-Type: multipart/alternative; boundary=e89a8ff1cad2f0763e04e45552d7
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
(wtogami[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: 1VBYu3-0006ht-Jf
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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 23:30:29 -0000
--e89a8ff1cad2f0763e04e45552d7
Content-Type: text/plain; charset=UTF-8
Hence ship a miner that automatically reads the bitcoin.conf to find the
RPC authentication info. It would be faster and more efficient than the
unoptimized miner while simplifying the bitcoind code. Win for everyone.
Warren
On Mon, Aug 19, 2013 at 1:02 PM, Andreas Schildbach
<andreas@schildbach.de>wrote:
> On 08/19/2013 10:34 PM, Jeff Garzik wrote:
>
> >> FWIW, Litecoin 0.8.x entirely removed the internal miner and we warned
> >> people that getwork will be removed in the next major version.
> Pooler's CPU
> >> minerd which supports both sha256d and scrypt recently grew stratum
> support.
> >> Perhaps he could be convinced to add GBT support too, which would help
> this
> >> goal of completely removing the internal miner and getwork.
> >
> > The internal miner is still actively used for testnet, here.
>
> Here, too. If I'm too impatient to wait for the next block that is.
>
> I think it'd be a pity if the easy way to mine blocks would be removed.
>
>
>
>
> ------------------------------------------------------------------------------
> 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
>
--e89a8ff1cad2f0763e04e45552d7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hence ship a miner that automatically reads the bitcoin.co=
nf to find the RPC authentication info. =C2=A0It would be faster and more e=
fficient than the unoptimized miner while simplifying the bitcoind code. =
=C2=A0Win for everyone.<div>
<br></div><div>Warren</div></div><div class=3D"gmail_extra"><br><br><div cl=
ass=3D"gmail_quote">On Mon, Aug 19, 2013 at 1:02 PM, Andreas Schildbach <sp=
an dir=3D"ltr"><<a href=3D"mailto:andreas@schildbach.de" target=3D"_blan=
k">andreas@schildbach.de</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 08/19/2013 10:34 PM, Je=
ff Garzik wrote:<br>
<br>
>> FWIW, Litecoin 0.8.x entirely removed the internal miner and we wa=
rned<br>
>> people that getwork will be removed in the next major version. =C2=
=A0Pooler's CPU<br>
>> minerd which supports both sha256d and scrypt recently grew stratu=
m support.<br>
>> Perhaps he could be convinced to add GBT support too, which would =
help this<br>
>> goal of completely removing the internal miner and getwork.<br>
><br>
> The internal miner is still actively used for testnet, here.<br>
<br>
</div>Here, too. If I'm too impatient to wait for the next block that i=
s.<br>
<br>
I think it'd be a pity if the easy way to mine blocks would be removed.=
<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<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>
</div></div></blockquote></div><br></div>
--e89a8ff1cad2f0763e04e45552d7--
|
