summaryrefslogtreecommitdiff
path: root/fe/c170022b4ac1e6cdf0513884c27177604b12db
blob: 6893a3eb85e3cccbdd1cc90d31603c8f3adff3d1 (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
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 <luke@dashjr.org>) id 1UJRwa-0006wu-8W
	for bitcoin-development@lists.sourceforge.net;
	Sat, 23 Mar 2013 17:09:24 +0000
X-ACL-Warn: 
Received: from zinan.dashjr.org ([173.242.112.54])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1UJRwW-0000uK-O4 for bitcoin-development@lists.sourceforge.net;
	Sat, 23 Mar 2013 17:09:24 +0000
Received: from ishibashi.localnet (unknown [173.170.142.26])
	(Authenticated sender: luke-jr)
	by zinan.dashjr.org (Postfix) with ESMTPSA id 85A9627A2965;
	Sat, 23 Mar 2013 17:09:14 +0000 (UTC)
From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Date: Sat, 23 Mar 2013 17:09:05 +0000
User-Agent: KMail/1.13.7 (Linux/3.7.3-gentoo; KDE/4.9.5; x86_64; ; )
References: <CA+8xBpcwLUt=RBYynbQDwY2Bv1keCPy0pdXP4+8CG-wqvrxOCA@mail.gmail.com>
In-Reply-To: <CA+8xBpcwLUt=RBYynbQDwY2Bv1keCPy0pdXP4+8CG-wqvrxOCA@mail.gmail.com>
X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F
X-PGP-Key-ID: BD02942421F4889F
X-PGP-Keyserver: hkp://pgp.mit.edu
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201303231709.07059.luke@dashjr.org>
X-Spam-Score: -2.5 (--)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-2.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay
	domain
X-Headers-End: 1UJRwW-0000uK-O4
Subject: Re: [Bitcoin-development] Upcoming network event: block v2 lock-in
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, 23 Mar 2013 17:09:24 -0000

On Saturday, March 23, 2013 4:16:19 PM Jeff Garzik wrote:
> Users should not be impacted.  Some ancient miners will produce
> newly-invalid blocks (v1), that will get ignored.  The easy solution
> is to mine using a recent bitcoind (0.7 or later).  If you are a miner
> and need help upgrading to v2, ping us on #bitcoin-dev or
> bitcoin-development@lists.sourceforge.net.

I don't think anyone is mining using bitcoind 0.7 or later? Deepbit is the 
only pool I know of using bitcoind at all, and it's based on 0.3.21 (or about 
that)...

p2pool has supported v2 blocks since 2012 Aug 8.
Eloipool has supported v2 blocks since 2012 Sep 1.
slush's stratum server has supported v2 blocks since it was written.

I'm not aware of any other maintained open source poolservers.
At least PoolServerJ and ecoinpool are known to break when v2 blocks become 
mandatory.