summaryrefslogtreecommitdiff
path: root/6e/712535f23b38c5a7e5c8d70512791d969ceb1e
blob: 10dc319f393e1680ca2051e69d08d74073a3b79a (plain)
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
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mh.in.england@gmail.com>) id 1VCV0v-0004h5-Q0
	for bitcoin-development@lists.sourceforge.net;
	Thu, 22 Aug 2013 13:33:25 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.219.42 as permitted sender)
	client-ip=209.85.219.42; envelope-from=mh.in.england@gmail.com;
	helo=mail-oa0-f42.google.com; 
Received: from mail-oa0-f42.google.com ([209.85.219.42])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1VCV0s-0007RG-Hp
	for bitcoin-development@lists.sourceforge.net;
	Thu, 22 Aug 2013 13:33:25 +0000
Received: by mail-oa0-f42.google.com with SMTP id i18so3485171oag.29
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 22 Aug 2013 06:33:17 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.230.163 with SMTP id sz3mr2400055obc.81.1377178397124;
	Thu, 22 Aug 2013 06:33:17 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.80.165 with HTTP; Thu, 22 Aug 2013 06:33:16 -0700 (PDT)
In-Reply-To: <CAJHLa0OF8bnrBhETbfMcL8gYTqHqP5zbVT8vZN1gbkGbymOQFQ@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>
Date: Thu, 22 Aug 2013 15:33:16 +0200
X-Google-Sender-Auth: opbzQ_aeYzkShnhtmS6Ak5auYeU
Message-ID: <CANEZrP22PaduRgfNv6Cj=wV_3eCt42VTLhLmMWU9PQv_d4g0nA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Jeff Garzik <jgarzik@bitpay.com>
Content-Type: multipart/alternative; boundary=001a11c2f63a272d4e04e48955ce
X-Spam-Score: -0.5 (/)
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
	(mh.in.england[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	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: 1VCV0s-0007RG-Hp
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 13:33:26 -0000

--001a11c2f63a272d4e04e48955ce
Content-Type: text/plain; charset=UTF-8

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.


On Thu, Aug 22, 2013 at 3:18 PM, Jeff Garzik <jgarzik@bitpay.com> wrote:

> On Thu, Aug 22, 2013 at 5:36 AM, Maciej Trebacz <maciej@bitalo.com> wrote:
> > Will removing "getwork" from the client impact the "setgenerate" RPC
> call?
> > I.e. would you still be able to generate coins on testnet-in-a-box this
> way,
> > or would you need a dedicated miner for that? testnet-in-a-box is very
> > useful for testing and easy to setup, it would be great if it stays that
> way
>
> Yes, that is currently being discussed in a separate pull request.  My
> pull request does not impact setgenerate, but an added proposal does
> remove the internal miner completely.
>
> --
> Jeff Garzik
> Senior Software Engineer and open source evangelist
> BitPay, Inc.      https://bitpay.com/
>
>
> ------------------------------------------------------------------------------
> 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
>

--001a11c2f63a272d4e04e48955ce
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">That would be annoying for testing. Regtest mode allows yo=
u to create a new block by just running &quot;setgenerate true&quot; (it sw=
itches itself off after creating a block). If you had to set up a complicat=
ed set of separate programs just to do regtest mode that&#39;d be a step ba=
ckwards, IMO.</div>
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu, Aug 2=
2, 2013 at 3:18 PM, Jeff Garzik <span dir=3D"ltr">&lt;<a href=3D"mailto:jga=
rzik@bitpay.com" target=3D"_blank">jgarzik@bitpay.com</a>&gt;</span> wrote:=
<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">
<div class=3D"im">On Thu, Aug 22, 2013 at 5:36 AM, Maciej Trebacz &lt;<a hr=
ef=3D"mailto:maciej@bitalo.com">maciej@bitalo.com</a>&gt; wrote:<br>
&gt; Will removing &quot;getwork&quot; from the client impact the &quot;set=
generate&quot; RPC call?<br>
&gt; I.e. would you still be able to generate coins on testnet-in-a-box thi=
s way,<br>
&gt; or would you need a dedicated miner for that? testnet-in-a-box is very=
<br>
&gt; useful for testing and easy to setup, it would be great if it stays th=
at way<br>
<br>
</div>Yes, that is currently being discussed in a separate pull request. =
=C2=A0My<br>
pull request does not impact setgenerate, but an added proposal does<br>
remove the internal miner completely.<br>
<div class=3D"im HOEnZb"><br>
--<br>
Jeff Garzik<br>
Senior Software Engineer and open source evangelist<br>
BitPay, Inc. =C2=A0 =C2=A0 =C2=A0<a href=3D"https://bitpay.com/" target=3D"=
_blank">https://bitpay.com/</a><br>
<br>
</div><div class=3D"HOEnZb"><div class=3D"h5">-----------------------------=
-------------------------------------------------<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&amp;iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D48897511&amp;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>

--001a11c2f63a272d4e04e48955ce--