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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <maciej@bitalo.com>) id 1VCSM2-0002qs-FQ
for bitcoin-development@lists.sourceforge.net;
Thu, 22 Aug 2013 10:43:02 +0000
Received-SPF: fail (sog-mx-1.v43.ch3.sourceforge.com: domain of bitalo.com
does not designate 74.125.82.193 as permitted sender)
client-ip=74.125.82.193; envelope-from=maciej@bitalo.com;
helo=mail-we0-f193.google.com;
Received: from mail-we0-f193.google.com ([74.125.82.193])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VCSM1-0005sJ-30
for bitcoin-development@lists.sourceforge.net;
Thu, 22 Aug 2013 10:43:02 +0000
Received: by mail-we0-f193.google.com with SMTP id x50so285767wes.8
for <bitcoin-development@lists.sourceforge.net>;
Thu, 22 Aug 2013 03:42:53 -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:in-reply-to:references:date
:message-id:subject:from:to:content-type;
bh=qEv9JKpRJiG7Hdlcdl/N3FEiB85kelnnuB9LEt4MLRo=;
b=VkMCwmVtzcVkrjsGL7el2bRgbYyUe5rDP2zzgPE0LP2Gunuq1sEWiwEVVZyo/F5MCY
xzE6O1mYg73u8t/OuKLFOw+na/woK+FOxN3LD0hTO3BmzGc0oOe+9nrUwpzYTCcFA0d4
W7U9XFirLfr23em0Flb7mRPGPxo8EtRYLL1TxPEMwEz8L3/4xmo+FkT67OpRpMQySdv8
2xrvROUSFnaTxVsjiie74zdzSCVMnFvtYuDYtYaYvke2jyqcq1WP8PjGFzA7PLUV82TZ
hdmWg20zJqiIP2YvKOoHaoGC2j1ogWbfhfPTgPccw4qop2SI13v5j/cHxpmJogS8/cyH
37BQ==
X-Gm-Message-State: ALoCoQmQbKLk34gXbT2B7/4ABOVCcePJw644pponz44v48d8p7ucAIPEQwMpZCRB1oc0XGlm9uVY
MIME-Version: 1.0
X-Received: by 10.180.188.102 with SMTP id fz6mr19809379wic.6.1377164211321;
Thu, 22 Aug 2013 02:36:51 -0700 (PDT)
Received: by 10.217.2.17 with HTTP; Thu, 22 Aug 2013 02:36:51 -0700 (PDT)
X-Originating-IP: [83.5.255.244]
In-Reply-To: <6e1e64615be421f47a74bcc427a13485@astutium.com>
References: <mailman.167053.1376954386.4583.bitcoin-development@lists.sourceforge.net>
<1377120278.34996.YahooMailNeo@web124501.mail.ne1.yahoo.com>
<6e1e64615be421f47a74bcc427a13485@astutium.com>
Date: Thu, 22 Aug 2013 11:36:51 +0200
Message-ID: <CAD=_8RRU8UAqOUZeawe=XVfT91YtWmVGwDzW+KfkWYj649aZbw@mail.gmail.com>
From: Maciej Trebacz <maciej@bitalo.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=001a11c37b9a9d121504e48607d5
X-Spam-Score: 5.9 (+++++)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
4.0 SPF_CHECK_FAIL SPF reports sender host as NOT permitted to send
mails from
0.9 SPF_FAIL SPF: sender does not match SPF record (fail)
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1VCSM1-0005sJ-30
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 10:43:02 -0000
--001a11c37b9a9d121504e48607d5
Content-Type: text/plain; charset=ISO-8859-1
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 :).
On Wed, Aug 21, 2013 at 11:39 PM, <rob.golding@astutium.com> wrote:
> > It appears that we will soon be at a hashrate where all the desktop
> > CPUs in the world couldn't really make a dent in it... certainly not
> > desktop cpus using the slow integrated cpu miner,
>
> I thought the integrated miner was retired a version or so ago - I
> dontrecall seeing it for some time in bitcoin-qt
>
> Now you can buy a USB stick for $20 which can be pushed to around
> 500MH/s, and there's no reason the manufacturers couldn't ship those
> with a miner-program onboard !
>
> Rob
>
>
> ------------------------------------------------------------------------------
> 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
>
--001a11c37b9a9d121504e48607d5
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><span style=3D"font-family:arial,sans-serif;font-size:13px=
">Will removing "getwork" from the client impact the "setgen=
erate" RPC call? I.e. would you still be able to generate coins on tes=
tnet-in-a-box this way, or would you need a dedicated miner for that? testn=
et-in-a-box is very useful for testing and easy to setup, it would be great=
if it stays that way :).</span><br>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Wed,=
Aug 21, 2013 at 11:39 PM, <span dir=3D"ltr"><<a href=3D"mailto:rob.gol=
ding@astutium.com" target=3D"_blank">rob.golding@astutium.com</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">> It appears that we wi=
ll soon be at a hashrate where all the desktop<br>
> CPUs in the world couldn't really make a dent in it... certainly n=
ot<br>
> desktop cpus using the slow integrated cpu miner,<br>
<br>
</div>I thought the integrated miner was retired a version or so ago - I<br=
>
dontrecall seeing it for some time in bitcoin-qt<br>
<br>
Now you can buy a USB stick for $20 which can be pushed to around<br>
500MH/s, and =A0there's no reason the manufacturers couldn't ship t=
hose<br>
with a miner-program onboard !<br>
<br>
Rob<br>
<div class=3D"HOEnZb"><div class=3D"h5"><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>
--001a11c37b9a9d121504e48607d5--
|
