summaryrefslogtreecommitdiff
path: root/5e/206166526188bf4b7be7355d8238988d27c84d
blob: 99ccddfe3a2469fd663ac15fbdfd04f18c247895 (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
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 <pete@petertodd.org>) id 1UGzPq-0003UV-SQ
	for bitcoin-development@lists.sourceforge.net;
	Sat, 16 Mar 2013 22:17:26 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of petertodd.org
	designates 62.13.149.58 as permitted sender)
	client-ip=62.13.149.58; envelope-from=pete@petertodd.org;
	helo=outmail149058.authsmtp.co.uk; 
Received: from outmail149058.authsmtp.co.uk ([62.13.149.58])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1UGzPn-0005UO-6j for bitcoin-development@lists.sourceforge.net;
	Sat, 16 Mar 2013 22:17:26 +0000
Received: from mail-c232.authsmtp.com (mail-c232.authsmtp.com [62.13.128.232])
	by punt14.authsmtp.com (8.14.2/8.14.2/) with ESMTP id r2GMHGOM017693;
	Sat, 16 Mar 2013 22:17:16 GMT
Received: from [25.13.89.202] (wireless-device.rogers.com [74.198.9.202] (may
	be forged)) (authenticated bits=0)
	by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id r2GMHBlo090459
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Sat, 16 Mar 2013 22:17:14 GMT
References: <CAD2Ti28XnZFDLMm+B1cxb5b+adjwk5M-DrFRs7C+VE=SLZ0hNQ@mail.gmail.com>
	<CABsx9T0VMuCwtw=LR_N4PyVPKGzAJfE3K7NzzLK719w87aqQ5g@mail.gmail.com>
	<17182C57-07C5-4E35-9F04-DC2B8C96A8EB@ceptacle.com>
	<CAD2Ti28baaYbbYvNxUgb2PNz0UjURkE5ROtmdSJ8nxvp4+fFKA@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CAD2Ti28baaYbbYvNxUgb2PNz0UjURkE5ROtmdSJ8nxvp4+fFKA@mail.gmail.com>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <403A5D3D-9CB1-4E35-A017-A5E0F42BFF39@petertodd.org>
X-Mailer: iPhone Mail (10B146)
From: Peter Todd <pete@petertodd.org>
Date: Sat, 16 Mar 2013 18:17:09 -0400
To: grarpamp <grarpamp@gmail.com>
X-Server-Quench: 41c7cf26-8e87-11e2-b10b-0025903375e2
X-AuthReport-Spam: If SPAM / abuse - report it at:
	http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
	aAdMdwQUFVQGAgsB AmUbWVZeUVp7WGc7 bA5PbAxVfENQXQVo
	T01BRU1TWkdqdmF5 dEJBUhBycwBPNnh2 Y08sWnEIWxcsd0Bg
	ShtcEnAHZDJidTIe UBJFdwNWdQpKfRxC bwV9GhFYa3VsFCMk
	FAgyOXU9MCtSLCNN RwwLMWdaZkVDAjl0 WgsPVW1pTQsVEE0A 
X-Authentic-SMTP: 61633532353630.1019:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 74.198.9.202/587
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
	anti-virus system.
X-Spam-Score: -1.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 SPF_PASS               SPF: sender matches SPF record
X-Headers-End: 1UGzPn-0005UO-6j
Cc: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Ok to use 0.8.x?
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, 16 Mar 2013 22:17:27 -0000

Hardware mining rigs do not need updating - they all are designed to connect=
 directly to a pool and it is the pool that makes all block related decision=
s. All the miner, or as I prefer to call them hasher, sees is an 80 byte blo=
ck header and possibly with stratum and getblocktemplate enough other inform=
ation like a partial merkle tree to roll the extranonce.

On 2013-03-16, at 18:04, grarpamp <grarpamp@gmail.com> wrote:

>>> Bitcoin version 0.8.0 is safe to use for everything EXCEPT creating bloc=
ks.
>>>=20
>>> So: safe for everybody except solo miners / pool operators.
>>=20
>> And even solo miners / pool operators can use it if connected to the netw=
ork only through a 0.7 node.
>=20
> I'll go ahead and use 0.8.x since it will be just transactions and queries=
.
>=20
> I'm guessing this will all be fixed in a couple weeks and that ASIC and FP=
GA
> miners will have their softcode updated, as will the pure softminers (GPU)=
.
>=20
> --------------------------------------------------------------------------=
----
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_mar
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>=20