From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Upcoming network event: block v2 lock-in
Date: Sat, 23 Mar 2013 17:09:05 +0000 [thread overview]
Message-ID: <201303231709.07059.luke@dashjr.org> (raw)
In-Reply-To: <CA+8xBpcwLUt=RBYynbQDwY2Bv1keCPy0pdXP4+8CG-wqvrxOCA@mail.gmail.com>
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.
next prev parent reply other threads:[~2013-03-23 17:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-23 16:16 [Bitcoin-development] Upcoming network event: block v2 lock-in Jeff Garzik
2013-03-23 17:09 ` Luke-Jr [this message]
2013-03-23 17:28 ` Jeff Garzik
2013-03-23 17:43 ` Luke-Jr
2013-03-23 17:47 ` Jeff Garzik
2013-03-23 17:51 ` Luke-Jr
2013-03-23 18:21 ` Jeff Garzik
2013-03-23 18:27 ` Luke-Jr
2013-03-23 19:18 ` Gregory Maxwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201303231709.07059.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox