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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1VBSIO-00031s-N1
for bitcoin-development@lists.sourceforge.net;
Mon, 19 Aug 2013 16:27:08 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitpay.com
designates 74.125.82.173 as permitted sender)
client-ip=74.125.82.173; envelope-from=jgarzik@bitpay.com;
helo=mail-we0-f173.google.com;
Received: from mail-we0-f173.google.com ([74.125.82.173])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VBSIN-0007sG-QJ
for bitcoin-development@lists.sourceforge.net;
Mon, 19 Aug 2013 16:27:08 +0000
Received: by mail-we0-f173.google.com with SMTP id x54so2789619wes.18
for <bitcoin-development@lists.sourceforge.net>;
Mon, 19 Aug 2013 09:27:01 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=x-gm-message-state:mime-version:date:message-id:subject:from:to
:content-type;
bh=XqsLI/Xm257rw/wvU+f3Ns8yPWyQG90mXLUOzhh8dtc=;
b=W0iOS40b9ENTKvDLlW7pkH4hBJXfqPVehP9I29NCJK01qbEKLQdDD0Gn1vF0JHdHGY
ZO8A15VTTSfJcf5C82t4+I0NOXNkkpa91g1VN/J47TfQ/Qo/Me1XQymkhyAawsfr13cE
X4SRAMQYciKMmw7GunntWmrRrIj5mKeahYiG6qo/74yGBXTbkfbkM44HDDs9SFa2qk52
bK0SrtbRgu8Yxw3CgTAldwmzPH3q0RuOfhPTXPCF3wDwJZuqz2/8ZlCwLI6CWGAmVtGe
jeyHUaTTAMOQ+hTH3M6qXdm5yxL0oNpJ+P3b9Fkfydl7N2Ee4GgmXBcUlxee8OyTCsaO
OdiA==
X-Gm-Message-State: ALoCoQmXfb1Hmm1stBlFhPnpBBdqFAb25+AyiUe/TL1kG6/gnZf2ZEjIQnTDkrmOH4VHnFeDoHm4
MIME-Version: 1.0
X-Received: by 10.194.123.227 with SMTP id md3mr9349776wjb.17.1376929621504;
Mon, 19 Aug 2013 09:27:01 -0700 (PDT)
Received: by 10.194.23.1 with HTTP; Mon, 19 Aug 2013 09:27:01 -0700 (PDT)
Date: Mon, 19 Aug 2013 12:27:01 -0400
Message-ID: <CAJHLa0MnnWw=qiYC0nJcY=BdTDcAjGtraJ+kazoG7_bHW-HBtw@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.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 SPF_PASS SPF: sender matches SPF record
-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: 1VBSIN-0007sG-QJ
Subject: [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 16:27:09 -0000
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/
|
