From: Jeff Garzik <jgarzik@exmulti.com>
To: Luke-Jr <luke@dashjr.org>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Upcoming network event: block v2 lock-in
Date: Sat, 23 Mar 2013 13:47:46 -0400 [thread overview]
Message-ID: <CA+8xBpfzNYqFm-zCD8L7KDiL9x+ez-pUM3B3T981D1n69t8gQQ@mail.gmail.com> (raw)
In-Reply-To: <201303231743.59510.luke@dashjr.org>
On Sat, Mar 23, 2013 at 1:43 PM, Luke-Jr <luke@dashjr.org> wrote:
> On Saturday, March 23, 2013 5:28:55 PM Jeff Garzik wrote:
>> On Sat, Mar 23, 2013 at 1:09 PM, Luke-Jr <luke@dashjr.org> wrote:
>> > I don't think anyone is mining using bitcoind 0.7 or later?
>>
>> slush, BTC Guild, ozcoin too I think, several others.
>
> Not for producing coinbases (where BIP 34 is implemented).
Sure, that is largely the pool server layer. But it is misleading to
imply that bitcoind is nowhere in the stack.
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com
next prev parent reply other threads:[~2013-03-23 17:47 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
2013-03-23 17:28 ` Jeff Garzik
2013-03-23 17:43 ` Luke-Jr
2013-03-23 17:47 ` Jeff Garzik [this message]
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=CA+8xBpfzNYqFm-zCD8L7KDiL9x+ez-pUM3B3T981D1n69t8gQQ@mail.gmail.com \
--to=jgarzik@exmulti.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=luke@dashjr.org \
/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