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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1VCWq7-0002ma-Vi
for bitcoin-development@lists.sourceforge.net;
Thu, 22 Aug 2013 15:30:24 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.54 as permitted sender)
client-ip=209.85.214.54; envelope-from=laanwj@gmail.com;
helo=mail-bk0-f54.google.com;
Received: from mail-bk0-f54.google.com ([209.85.214.54])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VCWq4-0007Xc-2z
for bitcoin-development@lists.sourceforge.net;
Thu, 22 Aug 2013 15:30:23 +0000
Received: by mail-bk0-f54.google.com with SMTP id mz12so758886bkb.13
for <bitcoin-development@lists.sourceforge.net>;
Thu, 22 Aug 2013 08:30:13 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.205.22.71 with SMTP id qv7mr10857523bkb.20.1377185413668;
Thu, 22 Aug 2013 08:30:13 -0700 (PDT)
Received: by 10.204.69.141 with HTTP; Thu, 22 Aug 2013 08:30:13 -0700 (PDT)
In-Reply-To: <CANEZrP22PaduRgfNv6Cj=wV_3eCt42VTLhLmMWU9PQv_d4g0nA@mail.gmail.com>
References: <mailman.167053.1376954386.4583.bitcoin-development@lists.sourceforge.net>
<1377120278.34996.YahooMailNeo@web124501.mail.ne1.yahoo.com>
<6e1e64615be421f47a74bcc427a13485@astutium.com>
<CAD=_8RRU8UAqOUZeawe=XVfT91YtWmVGwDzW+KfkWYj649aZbw@mail.gmail.com>
<CAJHLa0OF8bnrBhETbfMcL8gYTqHqP5zbVT8vZN1gbkGbymOQFQ@mail.gmail.com>
<CANEZrP22PaduRgfNv6Cj=wV_3eCt42VTLhLmMWU9PQv_d4g0nA@mail.gmail.com>
Date: Thu, 22 Aug 2013 17:30:13 +0200
Message-ID: <CA+s+GJC4o5V5p+FY+bgWVUt5umebn4_37bTihfX2q1GF05S=VA@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: multipart/alternative; boundary=20cf30223bf55f5f7704e48af78c
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
(laanwj[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: 1VCWq4-0007Xc-2z
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: Thu, 22 Aug 2013 15:30:24 -0000
--20cf30223bf55f5f7704e48af78c
Content-Type: text/plain; charset=UTF-8
On Thu, Aug 22, 2013 at 3:33 PM, Mike Hearn <mike@plan99.net> wrote:
> That would be annoying for testing. Regtest mode allows you to create a
> new block by just running "setgenerate true" (it switches itself off after
> creating a block). If you had to set up a complicated set of separate
> programs just to do regtest mode that'd be a step backwards, IMO.
>
There is some consensus that when the internal miner is to be removed, a
simple miner should be packaged with the main repository as separate
program (the "reference miner"?). The only change is that it does no longer
need to burden the core code
(see also the discussion here: https://github.com/bitcoin/bitcoin/pull/2917).
Wladimir
--20cf30223bf55f5f7704e48af78c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><div class=3D"gmail_quote">=
On Thu, Aug 22, 2013 at 3:33 PM, Mike Hearn <span dir=3D"ltr"><<a href=
=3D"mailto:mike@plan99.net" target=3D"_blank">mike@plan99.net</a>></span=
> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">That wou=
ld be annoying for testing. Regtest mode allows you to create a new block b=
y just running "setgenerate true" (it switches itself off after c=
reating a block). If you had to set up a complicated set of separate progra=
ms just to do regtest mode that'd be a step backwards, IMO.</div>
</blockquote><div><br></div><div>There is some consensus that when the inte=
rnal miner is to be removed, a simple miner should be packaged with the mai=
n repository as separate program (the "reference miner"?). The on=
ly change is that it does no longer need to burden the core code<br>
</div><div>(see also the discussion here: <a href=3D"https://github.com/bit=
coin/bitcoin/pull/2917">https://github.com/bitcoin/bitcoin/pull/2917</a>). =
<br></div><br><div>Wladimir<br><br></div></div></div></div>
--20cf30223bf55f5f7704e48af78c--
|
