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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1WtC0E-00046a-6l
for bitcoin-development@lists.sourceforge.net;
Sat, 07 Jun 2014 08:29:26 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.173 as permitted sender)
client-ip=209.85.213.173; envelope-from=laanwj@gmail.com;
helo=mail-ig0-f173.google.com;
Received: from mail-ig0-f173.google.com ([209.85.213.173])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WtC0D-0005j4-71
for bitcoin-development@lists.sourceforge.net;
Sat, 07 Jun 2014 08:29:26 +0000
Received: by mail-ig0-f173.google.com with SMTP id hn18so1707864igb.12
for <bitcoin-development@lists.sourceforge.net>;
Sat, 07 Jun 2014 01:29:19 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.43.155.16 with SMTP id lg16mr12591198icc.65.1402129758864;
Sat, 07 Jun 2014 01:29:18 -0700 (PDT)
Received: by 10.64.60.195 with HTTP; Sat, 7 Jun 2014 01:29:18 -0700 (PDT)
In-Reply-To: <CAJHLa0OW9TeJrh6J8mAnx8Zy0i+AoF_1Mrp0Wn+5kZGex3_uJg@mail.gmail.com>
References: <CAJHLa0OW9TeJrh6J8mAnx8Zy0i+AoF_1Mrp0Wn+5kZGex3_uJg@mail.gmail.com>
Date: Sat, 7 Jun 2014 10:29:18 +0200
Message-ID: <CA+s+GJDQJk_37EruYkc41YfAgA__ntubwKVGM=15K03LRE+6tQ@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Jeff Garzik <jgarzik@bitpay.com>
Content-Type: text/plain; charset=UTF-8
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(laanwj[at]gmail.com)
-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: 1WtC0D-0005j4-71
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin miner heads-up: "getwork" RPC
going away
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: Sat, 07 Jun 2014 08:29:26 -0000
On Sat, Jun 7, 2014 at 3:55 AM, Jeff Garzik <jgarzik@bitpay.com> wrote:
> As such, it is planned to remove "getwork" in the next release. Most
> if not all pool servers have switched away from "getwork" years ago.
To be clear, they switched to "getblocktemplate" and "submitblock"
which provides a much more flexible and scalable way to do mining.
This is explained in https://en.bitcoin.it/wiki/Getblocktemplate .
Wladimir
|
